Review updates

irushchyshyn · irushchyshyn · commit cebb62309762 · 2017-04-27T15:58:43.000+02:00
- rename the section name to be a question
- sentences rewording and fixes
diff --git a/index.rst b/index.rst
@@ -86,8 +86,8 @@ If your package is being imported by third-party projects, but does not have any
 
 *See:* :doc:`tools`
 
-Make sure to follow the new naming scheme
------------------------------------------
+Are you following the new Python package naming scheme?
+-------------------------------------------------------
 
 .. include:: snippets/naming_scheme.inc
 
diff --git a/naming-scheme.rst b/naming-scheme.rst
@@ -1,5 +1,5 @@
-Following the new naming scheme
-===============================
+New Python package naming scheme
+================================
 
 .. include:: snippets/naming_scheme.inc
 
@@ -16,7 +16,7 @@ Using the outdated naming scheme in your subpackage names or run-time/build-time
 What needs to be changed?
 -------------------------
 
-Check the names of binary packages you are building from your SRPM, and if you use one of the following naming schemes, you'll find instructions on how to fix it in the `section below <required_changes_>`_.
+Check the names of binary RPM packages you are building from your SRPM, and if you use one of the following naming schemes, you'll find instructions on how to fix it in the `section below <required_changes_>`_.
 
 Common naming scheme violations
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/snippets/naming_scheme.inc b/snippets/naming_scheme.inc
@@ -1,3 +1,3 @@
-If you have ported your package in accordance with the guidance in the above sections, then it most certainly complies with the `Python package naming guidelines`_. However, you might have done it before this guide came to life or even before the naming guidelines changed, which might mean that some name changes are required. This section is here to walk you through them.
+If you have ported your package according to the guidance in previous sections, then it most certainly complies with the `Python package naming guidelines`_. However, you might have done it before this guide came to life or even before the naming guidelines changed, which might mean that some name changes are required. This section is here to walk you through them.
 
 .. _Python package naming guidelines: https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines#Python_source_package_naming

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`		-If you have ported your package in accordance with the guidance in the above sections, then it most certainly complies with the `Python package naming guidelines`_. However, you might have done it before this guide came to life or even before the naming guidelines changed, which might mean that some name changes are required. This section is here to walk you through them.
	`1`	+If you have ported your package according to the guidance in previous sections, then it most certainly complies with the `Python package naming guidelines`_. However, you might have done it before this guide came to life or even before the naming guidelines changed, which might mean that some name changes are required. This section is here to walk you through them.
`2`	`2`
`3`	`3`	`.. _Python package naming guidelines: https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines#Python_source_package_naming`