[cog svcs] Update CT info

Author: Jann-Skotdal

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

@@ -14,7 +14,10 @@ ms.author: v-jansko
 
 # Translator Text API V2 to V3 Migration
 
-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. V2 will be deprecated on April 30, 2018 and will be discontinued on April 30, 2019.
+> [!NOTE]
+> V2 will be 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. 
 
 The end of this document contains helpful links for you to learn more.
 

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

@@ -131,6 +131,7 @@ The error code is a 6-digit number combining the 3-digit HTTP status code follow
 | 403000| The operation is not allowed.|
 | 403001| The operation is not allowed because the subscription has exceeded its free quota.|
 | 405000| The request method is not supported for the requested resource.|
+| 408001| The custom translation system requested is not yet available. Please retry in a few minutes.|
 | 415000| The Content-Type header is missing or invalid.|
 | 429000, 429001, 429002| The server rejected the request because the client is sending too many requests. Reduce the frequency of requests to avoid throttling.|
 | 500000| An unexpected error occurred. If the error persists, report it with date/time of error, request identifier from response header X-RequestId, and client identifier from request header X-ClientTraceId.|

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

@@ -80,6 +80,11 @@ Request parameters passed on the query string are:
     <td>toScript</td>
     <td>*Optional parameter*.<br/>Specifies the script of the translated text.</td>
   </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>
+  </tr>
 </table> 
 
 Request headers include:
@@ -103,6 +108,13 @@ Request headers include:
     <td>X-ClientTraceId</td>
     <td>*Optional*.<br/>A client-generated GUID to uniquely identify the request. You can omit this header if you include the trace ID in the query string using a query parameter named `ClientTraceId`.</td>
   </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>
+  </tr>
 </table> 
 
 ## Request body
@@ -183,6 +195,10 @@ The following are the possible HTTP status codes that a request returns.
     <td>403</td>
     <td>The request is not authorized. Check the details error message. This often indicates that all free translations provided with a trial subscription have been used up.</td>
   </tr>
+  <tr>
+    <td>408</td>
+    <td>The request could not be fulfilled because a resource is missing. Check the details error message. When using a custom `category`, this often indicates that the custom translation system is not yet available to serve requests. The request should be retried after a waiting period (e.g. 10 minutes).</td>
+  </tr>
   <tr>
     <td>429</td>
     <td>The caller is sending too many requests.</td>