diff --git a/WPScan-User-Documentation.md b/WPScan-User-Documentation.md
index 991899f..467f8e7 100644
--- a/WPScan-User-Documentation.md
+++ b/WPScan-User-Documentation.md
@@ -130,11 +130,11 @@ Here we have put together a bunch of common commands that will help you get star
 
 _NOTE: Get your API token from [wpscan.com](https://wpscan.com/) if you also want the vulnerabilities associated with the detected plugin displaying._
 
-#### Enumerate all plugins with known vulnerabilities:
+#### Enumerate all plugins with known vulnerabilities
 
 `wpscan --url example.com -e vp --plugins-detection mixed --api-token YOUR_TOKEN`
 
-#### Enumerate all plugins in our database (could take a very long time):
+#### Enumerate all plugins in our database (could take a very long time)
 
 `wpscan --url example.com -e ap --plugins-detection mixed --api-token YOUR_TOKEN`
 
@@ -142,7 +142,7 @@ _NOTE: Get your API token from [wpscan.com](https://wpscan.com/) if you also wan
 
 `wpscan --url example.com -e u --passwords /path/to/password_file.txt`
 
-#### The remote website is up, but does not seem to be running WordPress.
+#### The remote website is up, but does not seem to be running WordPress
 
 If you get the `Scan Aborted: The remote website is up, but does not seem to be running WordPress.` error, it means that for some reason WPScan did not think that the site you are trying to scan is actually WordPress. If you think WPScan is wrong, you can supply the `--force` option to force WPScan to scan the site regardless. You may also need to set other options in this case, such as `--wp-content-dir` and `--wp-plugins-dir`.