diff --git a/README.md b/README.md
index cae34df07f..b9af2d1332 100644
--- a/README.md
+++ b/README.md
@@ -41,7 +41,7 @@ in your Script Build Phases.
 This is the recommended way to install a specific version of SwiftLint since it supports
 installing a pinned version rather than simply the latest (which is the case with Homebrew).
 
-Note that this will add the SwiftLint binaries, its dependencies' binaries and the Swift binary
+Note that this will add the SwiftLint binaries, its dependencies' binaries, and the Swift binary
 library distribution to the `Pods/` directory, so checking in this directory to SCM such as
 git is discouraged.
 
@@ -113,7 +113,7 @@ results.
 
 If you wish to fix violations as well, your script could run
 `swiftlint --fix && swiftlint` instead of just `swiftlint`. This will mean
-that all correctable violations are fixed, while ensuring warnings show up in
+that all correctable violations are fixed while ensuring warnings show up in
 your project for remaining violations.
 
 If you've installed SwiftLint via CocoaPods the script should look like this:
@@ -374,7 +374,7 @@ run SwiftLint from. The following parameters can be configured:
 Rule inclusion:
 
 * `disabled_rules`: Disable rules from the default enabled set.
-* `opt_in_rules`: Enable rules not from the default set.
+* `opt_in_rules`: Enable rules that are not part of the default set.
 * `only_rules`: Only the rules specified in this list will be enabled.
    Cannot be specified alongside `disabled_rules` or `opt_in_rules`.
 * `analyzer_rules`: This is an entirely separate list of rules that are only
@@ -634,7 +634,7 @@ specifications of nested configurations are getting ignored because there's no s
 If one (or more) SwiftLint file(s) are explicitly specified via the `--config` parameter,
 that configuration will be treated as an override, no matter whether there exist
 other `.swiftlint.yml` files somewhere within the directory. **So if you want to use
-use nested configurations, you can't use the `-- config` parameter.**
+ nested configurations, you can't use the `--config` parameter.**
 
 ## License