Fix typos in markdown docs (#64)
README.md: meesages -> messages CONTRIBUTING.md invokable -> invocable
This commit is contained in:
parent
c099c27d63
commit
6168884f4a
|
@ -62,8 +62,8 @@ As always, if you're modifying the software, you'll need to have
|
||||||
your development environment set up. You need:
|
your development environment set up. You need:
|
||||||
|
|
||||||
* make
|
* make
|
||||||
* python2 (invokable as "python2")
|
* python2 (invocable as "python2")
|
||||||
* python3 (invokable as "python3")
|
* python3 (invocable as "python3")
|
||||||
* pylint (see below)
|
* pylint (see below)
|
||||||
|
|
||||||
An easy way to install pylint is to use pip.
|
An easy way to install pylint is to use pip.
|
||||||
|
|
|
@ -65,7 +65,7 @@ is configured to use UTF-8 (the most common situation by far).
|
||||||
|
|
||||||
However, it's possible for flawfinder to halt if there is a
|
However, it's possible for flawfinder to halt if there is a
|
||||||
character encoding problem and you're running Python3.
|
character encoding problem and you're running Python3.
|
||||||
The usual symptom is error meesages like this:
|
The usual symptom is error messages like this:
|
||||||
`Error: encoding error in FILENAME 'ENCODING' codec can't decode byte ... in position ...: invalid start byte`
|
`Error: encoding error in FILENAME 'ENCODING' codec can't decode byte ... in position ...: invalid start byte`
|
||||||
|
|
||||||
Unfortunately, Python3 fails to provide useful built-ins to deal with this.
|
Unfortunately, Python3 fails to provide useful built-ins to deal with this.
|
||||||
|
|
Loading…
Reference in New Issue