Skip to content

Commit f07db08

Browse files
authored
Fix typos in porting.rst (#939)
1 parent 43ec282 commit f07db08

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

developer-workflow/porting.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,12 @@ Next, learn how to compile and run the Python interpreter on a platform to
1212
which it has already been ported; preferably Unix, but Windows will
1313
do, too. The build process for Python, in particular the ``Makefile`` in the
1414
source distribution, will give you a hint on which files to compile
15-
for Python. Not all source files are relevant: some are platform
16-
specific, others are only used in emergencies (e.g. ``getopt.c``).
15+
for Python. Not all source files are relevant: some are platform-specific,
16+
and others are only used in emergencies (e.g. ``getopt.c``).
1717

18-
It is not recommended to start porting Python without at least medium-level
18+
It is not recommended to start porting Python without at least a medium-level
1919
understanding of your target platform; i.e. how it is generally used, how to
20-
write platform specific apps, etc. Also, some Python knowledge is required, or
20+
write platform-specific apps, etc. Also, some Python knowledge is required, or
2121
you will be unable to verify that your port is working correctly.
2222

2323
You will need a ``pyconfig.h`` file tailored for your platform. You can

0 commit comments

Comments
 (0)