Improved spelling and wording

J12934 · J12934 · commit fe2807b1c9f1 · 2018-08-10T15:20:19.000+02:00
diff --git a/docs/user-guide/usage-examples/arachni-bodgeit-example.md b/docs/user-guide/usage-examples/arachni-bodgeit-example.md
@@ -1,24 +1,24 @@
-# Scanning modern Server Side Rendered Apps using arachni
+# Scanning Server Side Rendered Apps using arachni
 
-Scanning for Vulnerabilities in BodgeIt using arachni and the secureCodeBox API.
+Scanning for Vulnerabilities in BodgeIt using Arachni and the secureCodeBox.
 
 ## Introduction
 
 BodgeIt is a intentionally vulnarable web application written in JSPs with only very few usages of JavaScript.
 This makes the app relativly straight forward to scan using pretty much any tool.
 
-In this example we'll be using arachni controlled by the secureCodeBox to scan for vulnarabilties in the BodgeIt Store.
+In this example we'll be using Arachni controlled by the secureCodeBox to scan for vulnarabilties in the BodgeIt Store.
 
 ## Testing the setup
 
 This is a straight forward configuration.
 This configuration could be improved by configuring a login method for the scanner.
 
-### Start scan via HTTP API
+### Start the scan via HTTP API
 
 `PUT http://localhost:8080/box/processes/arachni_webapplicationscan`
 
-### Start scan via CLI
+### Start the scan via CLI
 
 `run_scanner.sh --payload payloadFile.json`
 
@@ -28,7 +28,7 @@ This configuration could be improved by configuring a login method for the scann
 [
     {
         "name": "Arachni BodgeIt Scan",
-        "location": "http://bodgeit:8080/",
+        "location": "http://bodgeit:8080/bodgeit/",
         "attributes": {
             "ARACHNI_DOM_DEPTH_LIMIT": 15,
             "ARACHNI_DIR_DEPTH_LIMIT": 5,
diff --git a/docs/user-guide/usage-examples/arachni-juice-shop-example.md b/docs/user-guide/usage-examples/arachni-juice-shop-example.md
@@ -1,22 +1,22 @@
-# Scanning modern Single Page Application like OWASP JuiceShop using arachni
+# Scanning modern Single Page Application like OWASP JuiceShop using Arachni
 
-Scanning for Vulnerabilities in OWASP JuiceShop using arachni and the secureCodeBox API.
+Scanning for Vulnerabilities in OWASP JuiceShop using Arachni and the secureCodeBox.
 
 ## Introduction
 
 JuiceShop poses some problems for many scanners, as it is written as a single page application. This means that the scanner needs to be able to execute JavaScript to spider the application.
 
-Luckily arachni is intended for exactly this case!
+Luckily Arachni is intended for exactly this case!
 
 ## Testing the setup
 
-To start of we should test weather the secureCodeBox and JuiceShop is properly set up. To do this we can start a minimal scan which will finish relatively quickly. This is done by setting the Page Limit to `1` so that arachni will only test the first page of the application.
+To start of we should test weather the secureCodeBox and JuiceShop is properly set up. To do this we can start a minimal scan which will finish relatively quickly. This is done by setting the Page Limit to `1` so that Arachni will only test the first page of the application.
 
-### Start test scan via HTTP API
+### Start the test scan via HTTP API
 
 `PUT http://localhost:8080/box/processes/arachni_webapplicationscan`
 
-### Start test scan via CLI
+### Start the test scan via CLI
 
 `run_scanner.sh --payload payloadFile.json`
 
@@ -42,20 +42,20 @@ This scan should finish in about a minute and should return a couple of findings
 
 ## Full JuiceShop Arachni Config
 
-A full arachni scan config for JuiceShop includes optimisations to maximise the amount of vulnerabilities discovered and optimise the scan time.
+A full Arachni scan config for JuiceShop includes optimisations to maximise the amount of vulnerabilities discovered and optimise the scan time.
 
 This is done by configuring the following parameters:
 
 1.  Increase Scan Depth (DOM_DEPTH, DIR_DEPTH and PAGE_LIMIT) to more sensible values for the application.
-2.  Exclude non relevant endpoints. This greatly decreases the scan time as arachni doesn't have to waste time scanning non relevant resources like static css/js files or socket.io endpoints.
-3.  Extending the spider by routes we know about but arachni wont be able to find via its spider because the are not linked anywhere in the application.
-4.  Provide arachni with the ability to log into the application. This is often the hardest part of the scan config. Without it the scanner will not be able access restricted pages, so that the scanner will only scan a subset of the application. In this case the login is performed using the `login-script` plugin of arachni which lets us script how to to the login. This script is included in the default `docker-compose` setup of the secureCodeBox. This script is located in `plugins/arachni-login-scripts/login_juice_shop.rb`. You can add custom login scripts for your application into the same directory, the will get mounted into the arachni container.
+2.  Exclude non relevant endpoints. This greatly decreases the scan time as Arachni doesn't have to waste time scanning non relevant resources like static css/js files or socket.io endpoints.
+3.  Extending the spider by routes we know about but Arachni wont be able to find via its spider because the are not linked anywhere in the application.
+4.  Provide Arachni with the ability to log into the application. This is often the hardest part of the scan config. Without it the scanner will not be able access restricted pages, so that the scanner will only scan a subset of the application. In this case the login is performed using the `login-script` plugin of Arachni which lets us script how to to the login. This script is included in the default `docker-compose` setup of the secureCodeBox. This script is located in `plugins/Arachni-login-scripts/login_juice_shop.rb`. You can add custom login scripts for your application into the same directory, the will get mounted into the Arachni container.
 
-### Start full scan via HTTP API
+### Start the full scan via HTTP API
 
 `PUT http://localhost:8080/box/processes/arachni_webapplicationscan`
 
-### Start full scan via CLI
+### Start the full scan via CLI
 
 `run_scanner.sh --payload payloadFile.json`
 
