CONTENT: find and destroy broken links

Author: lwasser

_pages/home.md

@@ -11,8 +11,8 @@ header:
     actions:
         - label: "Submit a Package"
           url: "https://github.com/pyOpenSci/software-review/issues"
-        - label: "Read our Handbook"
-          url: "/contributing-guide/intro"
+        - label: "Read our Peer Review Guide"
+          url: "/peer-review-guide/intro"
 mission:
   - excerpt: 'We build diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. Join our global community.'
 programs:
@@ -26,8 +26,8 @@ programs:
     alt: "placeholder image 2"
     title: "Open Peer Review"
     excerpt: "Our open peer review process of Python tools supports standardized software quality and usability. It also provides needed credit and visibility to tool maintainers. Finally it removes redundancy of packages with similar functionaly across the scientific Python ecosystem."
-    url: https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/intro.html
-    btn_label: "Read More About Our Peer Review"
+    url: /python-packages/
+    btn_label: "Learn More About Package Peer Review"
     btn_class: "btn--primary"
   - image_path: images/brooke-cagle-unsplash.png
     title: "Skills for Open Source and Open Science"

_pages/python-packages.md

@@ -27,7 +27,7 @@ classes: wide
             <p>You're in the right place! Learn about the steps to submit a package
             for open peer review in our guidebook. </p>
           </div>  
-          <p><a href="https://www.pyopensci.org/contributing-guide/open-source-software-submissions/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
+          <p><a href="https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
       </div>
     </div>
   </div>

_pages/resources.md

@@ -13,10 +13,10 @@ Here are some links to our resources and related sites:
 
 * [**pyOpenSci Discourse Forum**](https://pyopensci.discourse.group/): Our community forum for discussing all things pyOpenSci. Have feedback or ideas about the review process? Need help finishing or maintaining your Python package? Have a question about how to use one of pyOpenSci’s packages? Our forum is the best place for these types of discussion.
 
-* [**pyOpenSci Guidebook**](https://www.pyopensci.org/contributing-guide/intro): Contains information for package authors and reviewers, including our [package guide](https://www.pyopensci.org/contributing-guide/authoring/index.html#packaging-guide), our [peer review process](https://www.pyopensci.org/contributing-guide/intro.html), and tips for [package maintenance](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/policies-and-guidelines.html#after-acceptance-package-ownership-and-maintenance). If you are interested in submitting a package to pyOpenSci, start with our [author guide](https://www.pyopensci.org/contributing-guide/authoring/index.html) and the links within it.
+* [**pyOpenSci Guidebook**](https://www.pyopensci.org/peer-review-guide/intro): Contains information for package authors and reviewers, including our [package guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html#packaging-guide), our [peer review process](https://www.pyopensci.org/peer-review-guide/intro.html), and tips for [package maintenance](https://www.pyopensci.org/peer-review-guide/open-source-software-peer-review/policies-and-guidelines.html#after-acceptance-package-ownership-and-maintenance). If you are interested in submitting a package to pyOpenSci, start with our [author guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html) and the links within it.
 
 * [**pyOpenSci's Governance Repo**](https://github.com/pyOpenSci/governance): Where we discuss the direction and scope of pyOpenSci. We're a community organization, so please feel free to create an [issue](https://github.com/pyOpenSci/governance/issues) if you have any questions or concerns!
 
-* [**pyOpenSci cookiecutter**](https://cookiecutter-pyopensci.readthedocs.io/en/latest/): We created a cookiecutter template to make packaging your python code easier. The cookiecutter follows all our guidelines from our [packaging guide](https://www.pyopensci.org/contributing-guide/authoring/index.html#packaging-guide).
+* [**pyOpenSci cookiecutter**](https://cookiecutter-pyopensci.readthedocs.io/en/latest/): We created a cookiecutter template to make packaging your python code easier. The cookiecutter follows all our guidelines from our [packaging guide](https://www.pyopensci.org/peer-review-guide/authoring/index.html#packaging-guide).
 
 * [**rOpenSci**](https://ropensci.org/): We draw inspiration from rOpenSci, a community to help promote, teach, and grow best-practices in software development for the Scientific R stack. They have a wonderful array of resources for R, such as their [collection of scientific R packages](https://ropensci.org/packages/). If you use R, we encourage you to get involved with them.

_posts/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md

@@ -101,7 +101,7 @@ There are a few ways to get involved with us now.
 1. [You can sign up to be a reviewer by filling out our reviewer form](https://forms.gle/B6zAukLCvJot5nws6). If you do this, we will reach out to you if a package is submitted that suits your background and interests!
   * We will also be growing our editorial board in the upcoming months. Once you have reviewed for us you are eligible to be considered as an editor. We will be posting more about this process in the upcoming months.
 1. Our open peer review process is running! If you have a package that you are working on, [you can submit it to our peer review process](https://github.com/pyOpenSci/software-review/issues). 
-  * You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/aims-and-scope.html).
+  * You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/peer-review-guide/open-source-software-peer-review/aims-and-scope.html).
   * If you have a package that you wish to submit but need some guidance, you can also submit a presubmission inquiry or a request for help here.
 2. You can [follow us on twitter](https://www.twitter.com/pyopensci) to keep tabs on our progress. 
 

_posts/2022-09-27-call-for-python-software-review-editors.md

@@ -17,7 +17,7 @@ categories:
 ## An update on pyOpenSci's review process 
 
 Hey there! I just wanted to update everyone about where pyOpenSci is with 
-its peer review process. We are currently hard at work updating [our guides](https://www.pyopensci.org/contributing-guide/intro.html) to 
+its peer review process. We are currently hard at work updating [our guides](https://www.pyopensci.org/peer-review-guide/intro.html) to 
 streamline the peer review process. For the next 2 months (October & November 2022) 
 we will prioritize setting up an editorial board to support new reviews as they 
 come in. 
@@ -28,7 +28,7 @@ With that below you will find a few updates.
 
 [David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as 
 an editor will take on the Editor in Chief role! [You can learn more about that 
-role here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
+role here](https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
 
 As Editor in Chief, David will:
 
@@ -57,7 +57,7 @@ longer given mutual consent. You will be responsible for handling 3-4 package
 reviews during that year. We may also bring on guest editors in other 
 instances, e.g., because of their familiarity with a specific domain.
 
-You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editors-guide.html). 
+You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/peer-review-guide/open-source-software-submissions/editors-guide.html). 
 
 We currently have a package in the queue that is spatial / remote sensing related
 that we'd love to have an editor onboard to review. But we are in need of editors