Merge branch 'master' of https://github.com/Jann-Skotdal/azure-docs-pr

Author: Jann-Skotdal

articles/cognitive-services/Translator/migrate-to-v3.md

@@ -15,7 +15,7 @@ ms.author: v-jansko
 # Translator Text API V2 to V3 Migration
 
 > [!NOTE]
-> V2 will be deprecated on April 30, 2018 and will be discontinued on April 30, 2019.
+> V2 was deprecated on April 30, 2018 and will be discontinued on April 30, 2019.
 
 The Microsoft Translator team has released Version 3 (V3) of the Translator Text API. This release includes new features, deprecated methods and a new format for sending to, and receiving data from the Microsoft Translator Service. This document provides information for changing applications to use V3. 
 

articles/cognitive-services/Translator/reference/v3-0-translate.md

@@ -82,7 +82,7 @@ Request parameters passed on the query string are:
   </tr>
   <tr>
     <td>AllowFallback</td>
-    <td>*Optional parameter*.<br/>Specifies that the service is allowed to fallback to a general system when a custom system does not exist. Possible values are: `true` (default) or `false`.<br/>‘AllowFallback=false’ specifies that the translation should only use systems trained for the ‘category’ specified by the request. If a translation for language X to language Y requires chaining through a pivot language E, then all the systems in the chain (X->E and E->Y) will need to be custom and have the same category. If no system is found with the specific category, the request will return a 400 status code. ‘AllowFallback=true’ specifies that the service is allowed to fallback to a general system when a custom system does not exist.
+    <td>*Optional parameter*.<br/>Specifies that the service is allowed to fallback to a general system when a custom system does not exist. Possible values are: `true` (default) or `false`.<br/><br/>`AllowFallback=false` specifies that the translation should only use systems trained for the `category` specified by the request. If a translation for language X to language Y requires chaining through a pivot language E, then all the systems in the chain (X->E and E->Y) will need to be custom and have the same category. If no system is found with the specific category, the request will return a 400 status code. `AllowFallback=true` specifies that the service is allowed to fallback to a general system when a custom system does not exist.
 </td>
   </tr>
 </table> 
@@ -110,9 +110,7 @@ Request headers include:
   </tr>
   <tr>
     <td>X-MT-System</td>
-    <td>*Optional*.<br/>Specifies the system type that was used for translation for each ‘to’ language requested for translation. The value is a comma-separated list of strings. Each string indicates a type:<br/>
-* Custom -  Request includes a custom system and at least one custom system was used during translation.
-* Team - All other requests
+    <td>*Optional*.<br/>Specifies the system type that was used for translation for each ‘to’ language requested for translation. The value is a comma-separated list of strings. Each string indicates a type:<br/><ul><li>Custom -  Request includes a custom system and at least one custom system was used during translation.</li><li>Team - All other requests</li></ul>
 </td>
   </tr>
 </table>