Updated Auth README to fix broken link

Authentication/External_Token_Auth/README.md

@@ -4,11 +4,11 @@ Sometimes authentication is not performed with just a `username` and `password`.
 
 To support this type of authentication, HawkScan supports externally supplying an authorization token with the authentication.external configuration.
 
-The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programatic fashion.
+The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programmatic fashion.
 
-For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/configuration/authenticated-scanning.html#external-token-authentication--custom-token-authorization)
+For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/authenticated-scanning/inject-multiple-cookies-and-tokens.html)
 
-#### Running the scanner with multiiple config files
+#### Running the scanner with multiple config files
 To better support advanced configurations you can provide multiple configuration files as an overlay to the base scan configuration `stackhawk.yml`. Subsequent configuration files will be merged on top of the prior, effectively replacing any duplicate setting values form the previous scan configuration file.
 
 ```