updated as per dlepow feedback comments

Author: bengimblett

articles/api-management/api-management-faq.yml

@@ -15,8 +15,7 @@ metadata:
   ms.topic: article
   ms.date: 11/19/2017
   ms.author: danlep 
-  ms.custom: devx-track-azurepowershell
-  ms.custom: fasttrack-edit
+  ms.custom: devx-track-azurepowershell, fasttrack-edit
 
 title: Azure API Management FAQs
 summary: |
@@ -151,5 +150,5 @@ sections:
       - question: |
           How does API Management handle trailing slashes when calling backend services?
         answer: |
-          Historically and by convention a URL ending with a trailing slash is treated as a Directory, for example "https://contoso.com/sample/" whereas the same URL without the trailing slash "https://contoso.com/sample" would be indicative of a file. This is not mandated, so some systems will consider those two URLs unique, whilst others will consider them the same URL. API Management doesn’t make a distinction thus a single operation "resource" will accept "resource" and "resource/". It does not make sense therefore to create an operation for each. However, whilst the distinction doesn’t matter to API Management it may matter to the backend host. Some web servers will automatically redirect a URL not ending with a trailing slash, to the same URL ending in a trailing slash. As API Management is the client to the backend (server) an automatic redirect is not always desirable. The issue can be fixed by using the [Rewrite URL policy](api-management-transformation-policies.md#RewriteURL) to ensure a trailing slash is always added to the outbound backend call.
+          Historically and by convention a URL ending with a trailing slash is treated as a Directory, for example "https://contoso.com/sample/" whereas the same URL without the trailing slash "https://contoso.com/sample" would be indicative of a file. This is not mandated, so some systems will consider those two URLs unique, whilst others will consider them the same URL. API Management doesn’t make a distinction thus a single operation "resource" will accept "resource" and "resource/". However, whilst the distinction doesn’t matter to API Management it may matter to the backend host. Some web servers will automatically redirect a URL not ending with a trailing slash, to the same URL ending in a trailing slash. As API Management is the client to the backend (server) an automatic redirect is not always desirable. if needed create a [Rewrite URL policy](api-management-transformation-policies.md#RewriteURL) to ensure a trailing slash is always added to the outbound backend call.