Fix: edits from @pllim

Co-authored-by: P. L. Lim <[email protected]>

Author: lwasser

partners/astropy.md

@@ -8,13 +8,9 @@
 .
 :::
 
-pyOpenSci has a collaboration with the [Astropy scientific community](https://www.astropy.org/). Through this collaboration we add an additional layer of peer review checks to Astropy-related packages that go through our [open peer review process](https://www.pyopensci.org/software-peer-review/about/intro.html). If the package meets both the Astropy criteria and our pyOpenSci peer review criteria, it can then become both an astropy affiliated package and a pyOpenSci ecosystem package.
+pyOpenSci has a collaboration with the [Astropy scientific community](https://www.astropy.org/). Through this collaboration we add an additional layer of peer review checks to Astropy-related packages that go through our [open peer review process](https://www.pyopensci.org/software-peer-review/about/intro.html). If the package meets both the Astropy criteria and our pyOpenSci peer review criteria, it can then become both an Astropy Affiliated package and a pyOpenSci ecosystem package.
 
-If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
-Reviewed against current pyOpenSci guidelines and checks.
-Also reviewed against the Astropy-specific guidelines listed below.
-
-If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
+If you are submitting a package for review and wish to also apply for Astropy affiliation, your package will be:
 
 - Reviewed against current pyOpenSci guidelines and checks.
 - Also reviewed against the Astropy-specific guidelines listed below.
@@ -23,18 +19,18 @@ If you are submitting a package for review and wish to also apply for astropy af
 
 ### Astropy Specific Software Peer Review Guidelines
 
-To be an affiliated astropy package, your package should:
+To be an Astropy Affiliated package, your package should:
 
 - Be useful to astronomers. This can mean useful to a specific sub-domain of astronomy, or more broadly useful to a large fraction of astronomy (or beyond, as long as it is also useful for astronomy).
-- Specifically use, interface with, or provide complementary capabilities to other Astropy packages.
-- Use classes and functions from the astropy core package wherever possible and appropriate, and (as much as possible) avoid duplication with other packages in the Astropy ecosystem. This facilitates re-use of code and sharing of resources.
+- Specifically use, interface with, or provide complementary capabilities to `astropy` or other Astropy Affiliated packages.
+- Use classes and functions from the `astropy` core package wherever possible and appropriate, and (as much as possible) avoid duplication with other packages in the Astropy ecosystem. This facilitates re-use of code and sharing of resources.
 
 ### Ecointegration - Integration with the Astropy Ecosystem
 
 Your package should clearly integrate into the broader Astropy ecosystem. It should:
 
-- Use Astropy or other affiliated packages wherever possible
-- Use / depend upon Astropy or other affiliated packages functionality wherever possible to avoid duplication of functionality across the ecosystem.
+- Use `astropy` or other Astropy Affiliated packages wherever possible
+- Use / depend upon `astropy` or other Astropy Affiliated packages functionality wherever possible to avoid duplication of functionality across the ecosystem.
 
 ## Long-term maintenance & affiliate status over time