Skip to content

Commit 951f210

Browse files
committed
Some grammar fixes for writing/structure.
1 parent fb41621 commit 951f210

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

docs/writing/structure.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -99,12 +99,12 @@ which is not the case. There is an
9999
`example <http://docs.python.org/tutorial/modules.html#packages>`_ of how the
100100
dot notation should be used in the Python docs.
101101

102-
If you'd like you could name it as :file:`my_spam.py` but even our friend the
103-
underscore should not be seen often in module names.
102+
If you'd like you could name your module :file:`my_spam.py`, but even our
103+
friend the underscore should not be seen often in module names.
104104

105-
Aside for some naming restrictions, nothing special is required for a Python file
106-
to be a module, but the import mechanism needs to be understood in order to use
107-
this concept properly and avoid some issues.
105+
Aside from some naming restrictions, nothing special is required for a Python
106+
file to be a module, but you need to understand the import mechanism in order
107+
to use this concept properly and avoid some issues.
108108

109109
Concretely, the ``import modu`` statement will look for the proper file, which is
110110
:file:`modu.py` in the same directory as the caller if it exists. If it is not
@@ -134,7 +134,7 @@ compartmentalized**.
134134
Using ``from modu import func`` is a way to pinpoint the function you want to
135135
import and put it in the global namespace. While much less harmful than ``import
136136
*`` because it shows explicitly what is imported in the global namespace, its
137-
advantage over a simpler ``import modu`` is only that it will save some typing.
137+
only advantage over a simpler ``import modu`` is that it will save a little typing.
138138

139139
**Very bad**
140140

0 commit comments

Comments
 (0)