TR-4678 Update guides on setting up HTTPS ET with AWS CloudFront and …

…Azure Front Door

content/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost.md

@@ -171,9 +171,9 @@ For up to date information on creating a distribution via CloudFront, please ref
 
    * Origin Path: leave blank.
 
-   * Protocol: choose "Match viewer". This provides backwards compatibility with HTTP as well as HTTPS.
+   * Protocol: choose "HTTPS only". This requires HTTPS for communication between CloudFront and SparkPost.
 
-   * Leave the port numbers at default.
+   * Leave the port number at default.
 
    * Choose minimum version of TLSv1.2. Note this sets what AWS CloudFront uses to communicate with SparkPost, it does not limit what your distribution offers to clients.
 
@@ -619,7 +619,7 @@ The steps below are based on [this guide](https://docs.microsoft.com/en-us/azure
 
     Leave "Accepted protocol" as the default "HTTP and HTTPS". Ensure your "Frontends/domains" setting is your previously configured subdomain name.
 
-    Set the Path to `/*` to match all incoming requests. Leave Route type set to the default "Forward", and set Forwarding Protocol to "Match request". Select "Add".
+    Set the Path to `/*` to match all incoming requests. Leave Route type set to the default of "Forward" and Forwarding Protocol set to the default of "HTTPS Only". Select "Add".
 
     ![](media/enabling-https-engagement-tracking-on-sparkpost/azure-front-door7.png)