Fix: move scope to appendix

Author: lwasser

scope.md renamed to appendices/scope.md

@@ -20,7 +20,6 @@ To be in technical scope for a pyOpenSci review, your package:
 * Should be structured in a way that someone else could contribute to it
 * Should vendor dependencies using standard approaches rather than including code from other packages within your repository. 
 
-
 ### Notes on scope categories
 - pyOpenSci is still developing as a community. If your scientific Python 
 package does not fit into one of the categories or if you have any other 
@@ -46,10 +45,8 @@ pyOpenSci has a goal of supporting long term maintenance of open source
 Python tools. It is thus important for us to know that if you need to step down as a maintainer, the package infrastructure and documentation is 
 in place to support us finding a new maintainer who can take over you 
 package's maintenance. 
-```
 
-A few examples of technically complex package structures that may 
-make it difficult for us to review are below:
+## Examples of technically complex package structures that may be difficult for us to review
 
 ### Example 1: Your package is an out of sync fork of another package repository that is being actively maintained. 
 
@@ -66,9 +63,10 @@ However, if there is a case where a forked repository is warranted, please
 consider submitting a pre-submission inquiry first and explain why the package is a 
 fork rather than an independent parent repository.
 
-### Example 2 Vendored dependencies
+### Example 2: Vendored dependencies
 
 If your package is a wrapper that wraps around another tool, we prefer that 
 the dependency be added as a dependency to your package. This allows 
 maintenance of the original code base to be independent from your package's 
 maintenance. 
+```

software-peer-review-guide/author-guide.md

@@ -55,7 +55,6 @@ emphasis on long term software maintenance and focuses more on
 publication quality and citation / credit.  
 ```
 
-
 ## 2. Does Your Package Meet Packaging Requirements?
 Before submitting your project for review with pyOpenSci, make sure that it
 follows the standards and guidelines outlined in the 
@@ -84,7 +83,7 @@ up to a week.
 
 Our current categories for determining package scope are below:
 
-```{include} ../scope.md
+```{include} ../appendices/scope.md
 ```
 
 ## 4. Submit Your Package for Peer Review
@@ -98,6 +97,12 @@ Once the issue is opened, our editor-in-chief and an editor from our editorial b
 to your package to meet minimal criteria before review. They also may reject your 
 package if it does not fall within our scope. 
 
+```{button-link} https://www.pyopensci.org/software-peer-review-guide/editor-in-chief-guide.html#editor-checklist-template
+:color: secondary
+:class: sd-rounded-pill
+Click here to view the editor checks that will be used to evaluate your package. 
+```
+
 ## 6. The Review Begins
 If your package meets minimal criteria for being 
 reviewed it may then be given to an editor with appropriate domain experience