Skip to content

Commit ef475bf

Browse files
committed
Minor edits
1 parent 597dbbf commit ef475bf

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

package-structure-code/code-style-linting-format.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
# Python Package Code Style, Format and Linters
22

33
```{important}
4+
45
## Take Aways
56
67
* pyOpenSci requires authors to follow PEP 8 code format guidelines
@@ -27,7 +28,7 @@ pyOpenSci peer review process requires that you to follow standard
2728
you can.
2829

2930
pyOpenSci doesn't require you to use a specific code format tool. However,
30-
we do look for consistency and readbility in code style. Below you will find
31+
we do look for consistency and readability in code style. Below you will find
3132
a discussion of:
3233

3334
1. The benefits of using linters and code format tools in your workflow
@@ -73,7 +74,7 @@ Python focused code formatters often follow PEP 8 standards. However, they also
7374
make stylistic decisions about code consistency. Code formatters will
7475
reformat your code for you.
7576

76-
Black is anexample of a commonly-used code formatter. Black both applies PEP 8
77+
Black is an example of a commonly-used code formatter. Black both applies PEP 8
7778
standards while also making decisions about things like consistent use of double
7879
quotes for strings, and spacing of items in lists.
7980

0 commit comments

Comments
 (0)