Update documentation

google_translate3_cli/projects_translate-text/index.html

@@ -5,7 +5,7 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   
-  <title>Translate Text - Translate v2.0.4+20210312</title>
+  <title>Translate Text - Translate v3.0.0+20220121</title>
   
 
   
@@ -34,7 +34,7 @@
     
     <nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
       <div class="wy-side-nav-search">
-        <a href=".." class="icon icon-home"> Translate v2.0.4+20210312</a>
+        <a href=".." class="icon icon-home"> Translate v3.0.0+20220121</a>
         
       </div>
 
@@ -54,6 +54,11 @@
                     
                 </li>
             
+                <li class="toctree-l1 ">
+                    <a class="" href="../projects_locations-batch-translate-document">Locations Batch Translate Document</a>
+                    
+                </li>
+            
                 <li class="toctree-l1 ">
                     <a class="" href="../projects_locations-batch-translate-text">Locations Batch Translate Text</a>
                     
@@ -124,6 +129,11 @@
                     
                 </li>
             
+                <li class="toctree-l1 ">
+                    <a class="" href="../projects_locations-translate-document">Locations Translate Document</a>
+                    
+                </li>
+            
                 <li class="toctree-l1 ">
                     <a class="" href="../projects_locations-translate-text">Locations Translate Text</a>
                     
@@ -226,41 +236,41 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 
 <p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
 <ul>
-<li><code>-r .    contents=ipsum</code><ul>
+<li><code>-r .    contents=et</code><ul>
 <li>Required. The content of the input in string format. We recommend the total content be less than 30k codepoints. The max length of this field is 1024. Use BatchTranslateText for larger text.</li>
 <li>Each invocation of this argument appends the given value to the array.</li>
 </ul>
 </li>
-<li><code>glossary-config    glossary=est</code><ul>
+<li><code>glossary-config    glossary=vero</code><ul>
 <li>Required. The <code>glossary</code> to be applied for this translation. The format depends on glossary: - User provided custom glossary: <code>projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}</code></li>
 </ul>
 </li>
 <li>
-<p><code>ignore-case=true</code></p>
+<p><code>ignore-case=false</code></p>
 <ul>
 <li>Optional. Indicates match is case-insensitive. Default value is false if missing.</li>
 </ul>
 </li>
 <li>
-<p><code>..    labels=key=ea</code></p>
+<p><code>..    labels=key=duo</code></p>
 <ul>
 <li>Optional. The labels with user-defined metadata for the request. Label keys and values can be no longer than 63 characters (Unicode codepoints), can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter. See https://cloud.google.com/translate/docs/advanced/labels for more information.</li>
 <li>the value will be associated with the given <code>key</code></li>
 </ul>
 </li>
-<li><code>mime-type=dolor</code><ul>
+<li><code>mime-type=dolore</code><ul>
 <li>Optional. The format of the source text, for example, &#34;text/html&#34;, &#34;text/plain&#34;. If left blank, the MIME type defaults to &#34;text/html&#34;.</li>
 </ul>
 </li>
-<li><code>model=lorem</code><ul>
-<li>Optional. The <code>model</code> type requested for this translation. The format depends on model type: - AutoML Translation models: <code>projects/{project-number-or-id}/locations/{location-id}/models/{model-id}</code> - General (built-in) models: <code>projects/{project-number-or-id}/locations/{location-id}/models/general/nmt</code>, <code>projects/{project-number-or-id}/locations/{location-id}/models/general/base</code> For global (non-regionalized) requests, use <code>location-id</code> <code>global</code>. For example, <code>projects/{project-number-or-id}/locations/global/models/general/nmt</code>. If missing, the system decides which google base model to use.</li>
+<li><code>model=et</code><ul>
+<li>Optional. The <code>model</code> type requested for this translation. The format depends on model type: - AutoML Translation models: <code>projects/{project-number-or-id}/locations/{location-id}/models/{model-id}</code> - General (built-in) models: <code>projects/{project-number-or-id}/locations/{location-id}/models/general/nmt</code>, For global (non-regionalized) requests, use <code>location-id</code> <code>global</code>. For example, <code>projects/{project-number-or-id}/locations/global/models/general/nmt</code>. If not provided, the default Google model (NMT) will be used</li>
 </ul>
 </li>
-<li><code>source-language-code=eos</code><ul>
+<li><code>source-language-code=voluptua.</code><ul>
 <li>Optional. The BCP-47 language code of the input text if known, for example, &#34;en-US&#34; or &#34;sr-Latn&#34;. Supported language codes are listed in Language Support. If the source language isn&#39;t specified, the API attempts to identify the source language automatically and returns the source language within the response.</li>
 </ul>
 </li>
-<li><code>target-language-code=labore</code><ul>
+<li><code>target-language-code=amet.</code><ul>
 <li>Required. The BCP-47 language code to use for translation of the input text, set to one of the language codes listed in Language Support.</li>
 </ul>
 </li>