From b73b8eb297d91cb78ed4c88b8d8efd0e2019d5c5 Mon Sep 17 00:00:00 2001 From: myersg86 Date: Sat, 29 Jan 2022 09:52:14 -0700 Subject: [PATCH] Fix typos in markdown docs README.md: meesages -> messages CONTRIBUTING.md invokable -> invocable --- CONTRIBUTING.md | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 797d0dc..4923069 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -62,8 +62,8 @@ As always, if you're modifying the software, you'll need to have your development environment set up. You need: * make -* python2 (invokable as "python2") -* python3 (invokable as "python3") +* python2 (invocable as "python2") +* python3 (invocable as "python3") * pylint (see below) An easy way to install pylint is to use pip. diff --git a/README.md b/README.md index d8f0fbf..0afb0b3 100644 --- a/README.md +++ b/README.md @@ -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 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` Unfortunately, Python3 fails to provide useful built-ins to deal with this.