Add references to documentation for Solution customisation

Author: ConnorKirk

docs/step-2.md

@@ -1,10 +1,10 @@
 # Step 2 - Customising and extending AWS WAF Security Automations Solution
 
-In this step, you will configure the WAF Security Automation Solution. Once you have configured the HTTP Flood Protection and Probe/Scanner Log Parser, you will test the new rules.
+In this step, you will configure the WAF Security Automation Solution. Once you have configured the HTTP Flood Protection and Probe/Scanner Log Parser, you will test this new configuration.
 
 ## 2.1.1 Customise HTTP Flood Protection (AWS Lambda Log Parser)
 
-The HTTP Flood protection provided by the Security Automation Solution can be configured. In this step, you will explore the possible configuration options.
+The HTTP Flood protection provided by the Security Automation Solution can be configured. In this step, you will explore the possible configuration options. [See the documentation](https://docs.aws.amazon.com/solutions/latest/aws-waf-security-automations/appendix-c.html) for a complete list
 
 
 The HTTP Flood log parser comes with some extensions points, they are:
@@ -77,7 +77,7 @@ curl -s -o /dev/null -w "Return Code: %{http_code}\n" <your-endpoint>
 Now you will customise our Scanner and Probe rules. These use Amazon Athena to query the logs generated by an application.
 The solutions refer to Athena by a saved query ID. As Athena doesn't allow you to change saved queries, you need to create a new query and update the Athena log parser event to use the new query ID.
 
-By customising the query performed by Athena, you can specify the rules for blocking scanners and probes.
+By customising the query performed by Athena, you can specify the rules for blocking scanners and probes. For further details, [see the documentation](https://docs.aws.amazon.com/solutions/latest/aws-waf-security-automations/appendix-d.html)
 
 ### 2.2.1
 * Navigate to the Amazon Athena console, select the Saved Queries tab;