Apply suggestions from code review

Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>

Author: lwasser

package-structure-code/python-package-distribution-files-sdist-wheel.md

@@ -8,7 +8,7 @@
 Once you have published both package distributions (the source distribution and the wheel) to PyPI, you can then publish to conda-forge. conda-forge requires an source distribution on PyPI in order to build your package on conda-forge. You do not need to rebuild your package to publish to conda-forge.
 :::
 
-You need to build your Python package in order to publish it to PyPI (or Conda). The build process organizes your code and metadata into a distribution format that can be uploaded to PyPI and subsequently downloaded and installed by users. NOTE: you need to publish a sdist to PyPI in order for conda-forge to properly build your package automatically.
+You need to build your Python package in order to publish it to PyPI (or a conda channel). The build process organizes your code and metadata into a distribution format that can be uploaded to PyPI and subsequently downloaded and installed by users. NOTE: you need to publish a sdist to PyPI in order for conda-forge to properly build your package automatically.
 :::
 
 (build-package)=

tutorials/publish-conda-forge.md

@@ -371,7 +371,7 @@ Below we break down each element of that list.
 > -[x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
 
 **Translation:** Make sure that your pull request title is specific. We suggest something like:
-`Add: conda-forge recipe for <your package name>`
+`Add recipe for <your package name>`
 
 > -[x] License file is packaged (see [here](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73) for an example).