Fix: minor edits after review

Author: lwasser

.github/workflows/build-site.yml

@@ -28,18 +28,11 @@ jobs:
           build_only: true
           build_dir: _site
 
-      - name: Run HTMLProofer with Ruby script that skips new links
-        run: |
-          merge_base = `git merge-base origin/main HEAD`.chomp
-          diffable_files = `git diff --name-only --diff-filter=AC #{merge_base}`.split("\n")
-          diffable_files = diffable_files.select { |filename| filename.end_with?('.md') }.map { |f| File.basename(f, File.extname(f)) }
-          HTMLProofer.check_directory('./_site', { ignore_urls: diffable_files }).run
-
-        # - name: Check HTML using htmlproofer
-        #   uses: chabad360/htmlproofer@master
-        #   with:
-        #     directory: "_site"
-        #     arguments: |
-        #       --ignore-urls "https://fonts.googleapis.com,https://fonts.gstatic.com,_site/_posts/README/index.html"
-        #       --ignore-files "/.+\/_posts\/README.md"
-        #       --ignore-status-codes "0,403, 429, 503, 999"
+      - name: Check HTML using htmlproofer
+        uses: chabad360/htmlproofer@master
+        with:
+          directory: "_site"
+          arguments: |
+            --ignore-urls "https://fonts.googleapis.com,https://fonts.gstatic.com,_site/_posts/README/index.html"
+            --ignore-files "/.+\/_posts\/README.md"
+            --ignore-status-codes "0,403, 429, 503, 999"

_posts/2023-12-29-czi-funds-pyopensci-2024.md

@@ -1,7 +1,7 @@
 ---
 layout: single
 title: "CZI Funds pyOpenSci"
-excerpt: "CZI has received funding from the Chan Zuckerberg Foundation"
+excerpt: "CZI has received funding from the Chan Zuckerberg Foundation. Learn more about how this funding will support pyOpenSci over the next 2 years."
 author: "Leah Wasser"
 permalink: /blog/czi-funds-pyOpenSci-2024.html
 header:
@@ -18,25 +18,25 @@ comments: true
 
 We are thrilled to announce that pyOpenSci has received 2 years of funding to cover core operations from the [Chan Zuckerberg Initiative (CZI)](https://chanzuckerberg.com/). These CZI funds will be used to continue critical pyOpenSci work that:
 
-* supports Python open source maintainers in developing the usable and maintainable scientific software the enables open science
-* helps scientists navigate a complex Python packaging ecosystem
-* diversifies the scientific Python open source community
+* supports Python open source maintainers in developing the usable and maintainable scientific software the enables open science;
+* helps scientists navigate a complex Python packaging ecosystem;
+* diversifies the scientific Python open source community.
 
 
 ## Open science builds trust and enables more people to participate
 
 Open and reproducible science builds trust and accelerates research and
 discovery. Open science supports scientific research that is both transparent and
 reusable. Free and open source software is critical to open science as it ensures that
-the analyses of research data are broadly accessible. To build truly open research workflows, scientists need to use free and open source software (FOSS). FOSS removes the barriers that licenses and other fees may create, particularly for undeserved communities.
+the analyses of research data are broadly accessible. To build truly open research workflows, scientists need to use free and open source software (FOSS). FOSS removes the barriers that licenses and other fees may create making diverse participation more accessible.
 
 ### Broad inclusion is critical for both open source and open science
 
-Broad inclusion of underrepresented and historically excluded individuals is critical to pyOpenSci's mission. The open source ecosystem has been found to be [even less diverse then the broader tech community], (https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/) and to help remedy this, pyOpenSci empowers everyone to participate in both the development and use of open source software. This
+Broad inclusion of underrepresented and historically excluded individuals is critical to pyOpenSci's mission. The open source ecosystem has been found to be [even less diverse then the broader tech community](https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/). To help remedy this, pyOpenSci empowers everyone to participate in both the development and use of open source software. This
 empowerment enables open science to reach its full potential.
 
 ### Open source maintainers need support
-Despite the importance of open source software and inclusion to fundamental
+Despite the importance of open source software to fundamental
 open science principles, open source maintainers do not get the support they
 need. Maintainers need both institutional and community support in learning
 and engaging in open source software development, maintaining tools and engaging
@@ -46,25 +46,25 @@ with the broad user base that may begin to use their tools in support of open sc
 
 We envision a world where:
 
-* The scientific Python open source ecosystem is diverse and inclusive.
-* Individuals developing open software are supported.
+* The scientific Python open source ecosystem is diverse and inclusive;
+* Individuals developing open software are supported;
 * Scientists have the skills needed to both contribute to open source and also develop collaborative open science workflows; these skills have significant overlap.
 
 ## pyOpenSci builds a supportive and inclusive world through three programs
 
 <figure>
     <a href="/images/pyopensci-pillars-flower.png">
-    <img src="/images/pyopensci-pillars-flower.png" style="max-width:100%" alt="A flower petal image with 3 flower petals and a flower center. In each petal there is text. The first says software peer review, the second community partnerships and the third packaging resources and standards. The center circle of the flower says diverse inclusive community.">
+    <img src="/images/pyopensci-pillars-flower.png" style="max-width:100%" alt="A flower petal image with 3 flower petals and a flower center. In each petal there is text. The first says software peer review, the second community partnerships and the third packaging resources and recommendations. The center circle of the flower says diverse inclusive community.">
     </a>
-    <figcaption> pyOpenSci supports scientists developing open source software through three programs: 1) peer review of scientific software, 2) community partnerships and 3) packaging resources and standards. These three programs are supported by a diverse and inclusive community that cares about the open source software that is needed for open science.
+    <figcaption> pyOpenSci supports scientists developing open source software through three programs: 1) peer review of scientific software, 2) community partnerships and 3) packaging resources and recommendations. These three programs are supported by a diverse and inclusive community that cares about the open source software that is needed for open science.
     </figcaption>
 </figure>
 
 The three programs pyOpenSci runs are:
 
 * [Peer review of scientific Python software](https://www.pyopensci.org/about-peer-review/index.html) - The pyOpenSci software peer review process helps scientists find the vetted and trusted tools they need to build reproducible open science workflows. We also empower our community with critical open science skills that support contributing to open source software.
 
-* [Community partnerships with domain-specific scientific Python communities](https://www.pyopensci.org/partners.html). Domain-specific communities partner with PyOpenSci to leverage pyOpenSci's peer review process as a way to track vetted, high quality tools. Communities also support the development of Python packaging packaging guidelines in an effort to streamline the development of packaging standards across the scientific Python ecosystem.
+* [Community partnerships with domain-specific scientific Python communities](https://www.pyopensci.org/partners.html). Domain-specific communities partner with PyOpenSci to leverage pyOpenSci's peer review process as a way to track vetted, high quality tools. Communities also support the development of Python packaging packaging guidelines in an effort to streamline the development of packaging recommendations across the scientific Python ecosystem.
 
 * Training and resources to help scientists develop and maintain high-quality, accessible, open source software. Our community developed the [Python packaging guide](https://www.pyopensci.org/python-package-guide/), which provides resources and tutorials that help scientists navigate a complex Python packaging ecosystem. The Python packaging guide also makes recommendations for community accepted best practices.