Fix: a few minor edits

Author: lwasser

index.md

@@ -1,7 +1,6 @@
 # pyOpenSci Python Open Source Package Development Guide
 
 
-
 ```{toctree}
 :hidden:
 :caption: Documentation
@@ -30,7 +29,8 @@ https://github.com/pyOpenSci/python-package-guide/community -->
 ## Welcome, Python open source enthusiast!
 
 Here you will find guidelines for what we look for in your scientific
-Python package when reviewing. You will also find best practice recommendations and curated lists of community resources surrounding packaging and documentation.
+Python package when reviewing. You will also find best practice recommendations and curated lists of community resources surrounding packaging and documentation. Our goal is to help the
+community make decisions around how to create scientific Python packages. We are working towards a shared vision of packaging that helps users better understand where to start.
 
 ::::{grid} 2
 :reverse:
@@ -82,6 +82,16 @@ documentation that are
 commonly used in the scientific Python community.
 :::
 
+:::{grid-item-card}
+:link: package-structure-code/intro
+:link-type: doc
+:class-header: bg-light
+
+✨ Python packaging tools & structure ✨
+^^^
+All of the modern tools discussed in this guide will help you build an efficient packaging workflow. This section helps you select the one that will work best for your workflow.
+:::
+
 
 :::{grid-item-card}
 :link: CONTRIBUTING
@@ -98,9 +108,9 @@ contribute.
 ## Who this guidebook is for
 We assume that you are here because you are:
 
+1. Looking for guidance on creating a Python package.
+1. Looking for resources associated with Python packaging.
 1. Considering submitting a package to pyOpenSci and want to understand what we are looking for when we review your package
-2. Looking for guidance on creating a Python package.
-3. Looking for resources associated with Python packaging.
 
 Well, friend, you've come to the right place!
 

package-structure-code/intro.md

@@ -3,6 +3,12 @@
 This section provides guidance on your Python package's structure, code formats and style. It also reviews the various packaging tools that you can use to
 support building and publishing your package.
 
+If you are confused by Python packaging, you are not alone!
+The good news is there are some great modern packaging
+tools that ensure that you're following best practices. Here, we
+review tool features and suggest tools that might be best fitted for your workflow.
+
+
 ```{note}
 If you are considering submitting a package for peer review, have a look at the
 bare-minimum [editor checks](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/editor-in-chief-guide.html#editor-checklist-template) that pyOpenSci
@@ -55,7 +61,7 @@ The suggestions for package layout in this section are made with the
 intent of being helpful; they are not specific requirements for your
 package to be reviewed and accepted into our pyOpenSci open source ecosystem.
 
-Please check out our [package scope page](https://www.pyopensci.org/software-peer-review/about/package-scope.html) and [review requirements in our author guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#) if you are looking for Python package review requirements!
+Please check out our [package scope page](https://www.pyopensci.org/software-peer-review/about/package-scope.html) and [review requirements in our author guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#) if you are looking for pyOpenSci's Python package review requirements!
 ```
 
 <!--

package-structure-code/python-package-structure.md

@@ -8,7 +8,6 @@ There are several core directories that should be included in all Python package
 * **tests/** this directory contains the tests for your project code
 * **package-name/**: this is the directory that contains the code for your Python project. It is normally named using your project's name.
 
-Every Python package should have all 3 of the above directories within it.
 
 ## Src vs flat layouts
 There are two different layouts that you will commonly see
@@ -25,9 +24,8 @@ at the root of your package's repository.
 
 On this page we:
 
-1. Suggest the **src/package-name** layout structure for new packages. This layout prevents some commonly found issues with the flat layout (discussed below)
-2. Introduce the flat layout as it is used in the scientific ecosystem. Currently this layout is the most common. As such it's good to be familiar with it in case you contribute to a package using a flat layout in the future! Or, perhaps
-you maintain one now!
+1. Suggest the **src/package-name** layout structure for new packages. This layout prevents some commonly found issues with the flat layout (discussed below).
+2. Introduce the flat layout as it is used in the scientific ecosystem. Currently this layout is the most common. As such it's good to be familiar with it in case you contribute to a package using a flat layout in the future!
 
 ```{admonition} pyOpenSci will never require a specific package structure for peer review
 :class: important