Merge pull request #51310 from kyle-hoyer/patch-4

Fixing formatting. Adding service endpoint link

Author: ktoliver

articles/azure-government/documentation-government-ase-disa-cap.md

@@ -36,11 +36,11 @@ However, since DISA advertises a default route out the ExpressRoute circuit, the
 You will need to create new routes in the UDR for the management addresses in order to keep the ASE healthy. For Azure Government ranges see [App Service Environment management addresses](https://docs.microsoft.com/azure/app-service/environment/management-addresses
 )
 
-Rule 1: 23.97.29.209 --> Internet
-Rule 2: 23.97.0.17 --> Internet 
-Rule 3: 23.97.16.184 --> Internet 
-Rule 4: 13.72.180.105 --> Internet
-Rule 5: 13.72.53.37 --> Internet
+* Rule 1: 23.97.29.209 --> Internet
+* Rule 2: 23.97.0.17 --> Internet 
+* Rule 3: 23.97.16.184 --> Internet 
+* Rule 4: 13.72.180.105 --> Internet
+* Rule 5: 13.72.53.37 --> Internet
 
 Make sure the UDR is applied to the subnet your ASE is deployed to. 
 
@@ -56,16 +56,16 @@ The images below describe the default NSG rules created during the ASE creation.
 
 ### Service Endpoints 
 
-Depending what storage you are using you will be required to enable Service Endpoints for SQL and Azure Storage to access them without going back down to the DISA BCAP. You also need to enable EventHub Service Endpoint for ASE logs. 
+Depending on the storage you use, you will be required to enable Service Endpoints for SQL and Azure Storage to access them without going back down to the DISA BCAP. You also need to enable EventHub Service Endpoint for ASE logs. [Learn more](https://docs.microsoft.com/azure/app-service/environment/network-info#service-endpoints).
 
 ## FAQs
 
-* Some configuration changes may take some time to take effect.  Allow for several hours for changes to routing, NSGs, ASE Health, etc. to propagate and take effect, or optionally you can reboot the ASE. 
+Some configuration changes may take some time to take effect.  Allow for several hours for changes to routing, NSGs, ASE Health, etc. to propagate and take effect, or optionally you can reboot the ASE. 
 
 ## Resource manager template sample
 
 > [!NOTE]
-   >In order to deploy non-RFC 1918 IP addresses in the portal you must pre-stage the VNet and Subnet for the ASE. You can use a Resource Manager Template to deploy the ASE with non-RFC1918 IPs as well.
+> In order to deploy non-RFC 1918 IP addresses in the portal you must pre-stage the VNet and Subnet for the ASE. You can use a Resource Manager Template to deploy the ASE with non-RFC1918 IPs as well.
    
 <a href="https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2FApp-Service-Environment-AzFirewall%2Fazuredeploy.json" target="_blank">