Merge remote-tracking branch 'origin/docs_cn' into docs_cn

_data/footer.yml

@@ -1,29 +1,35 @@
 columns:
   -
-    title: 'Get Involved'
+    title: '参与项目（Get Involved）'
     links:
       -
         title: Code of Conduct
-        url: '/codeofconduct.html'
+        url: 'https://opensearch.org/codeofconduct.html'
       -
-        title: 'Forums'
+        title: 'OpenSearch 中文论坛'
+        url: 'https://www.ossez.com/tag/opensearch'
+      -
+        title: '官方论坛'
         url: 'https://discuss.opendistrocommunity.dev/'
       -
-        title: 'Github'
+        title: '中文文档代码仓库 中文论坛'
+        url: 'https://github.com/cwiki-us-docs/opensearch-docs-cn'
+      -
+        title: '官方 Github'
         url: 'https://github.com/opensearch-project'
       -
-        title: 'Partners'
+        title: '合作方'
         url: '/partners/'
       -
-        title: 'Community Projects'
+        title: '社区项目'
         url: '/community_projects'
   -
-    title: 'Resources'
+    title: '资源（Resources）'
     links:
       #- 
       #  title: 'Documentation'
       #  url: 'https://github.com/opensearch/documentation'
-      - 
+      -
         title: FAQ
         url: '/faq/'
       -
@@ -32,11 +38,11 @@ columns:
       -
         title: 'Trademark Usage Policy'
         url: '/trademark-usage.html'
-      - 
+      -
         title: OpenSearch Disambiguation
         url: '/disambiguation.html'
   -
-    title: 'Connect'
+    title: '联系我们（Connect）'
     links:
       # -
       #  title: 'Twitter'

_im-plugin/ism/index.md

@@ -39,7 +39,7 @@ You can use the visual editor or JSON editor to create policies. Compared to the
 2. Choose **Create policy**.
 3. Choose **Visual editor**.
 4. In the **Policy info** section, enter a policy ID and an optional description.
-5. In the **Error notification** section, set up an optional error notification that gets sent whenever a policy execution fails. For more information, see [Error notifications]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#error-notifications).
+5. In the **Error notification** section, set up an optional error notification that gets sent whenever a policy execution fails. For more information, see [Error notifications]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#error-notifications). If you're using auto rollovers in your policy, we recommend setting up error notifications, which notify you of unexpectedly large indices if rollovers fail. 
 6. In **ISM templates**, enter any ISM template patterns to automatically apply this policy to existing and future indices. For example, if you specify a template of `sample-index*`, the ISM plugin automatically applies this policy to any indices whose names start with `sample-index`.
 7. In **States**, add any states you want to include in the policy. Each state has [actions]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies/#actions) the plugin executes when the index enters a certain state, and [transitions]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies/#transitions), which have conditions that, when met, transition the index into a destination state. The first state you create in a policy is automatically set as the initial state. Each policy must have at least one state, but actions and transitions are optional.
 8. Choose **Create**.
@@ -76,7 +76,7 @@ PUT _plugins/_ism/policies/policy_id
 
 If you have more than one template that matches an index pattern, ISM uses the priority value to determine which template to apply.
 
-For an example ISM template policy, see [Sample policy with ISM template]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#sample-policy-with-ism-template).
+For an example ISM template policy, see [Sample policy with ISM template for auto rollover]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies#sample-policy-with-ism-template-for-auto-rollover).
 
 Older versions of the plugin include the `policy_id` in an index template, so when an index is created that matches the index template pattern, the index will have the policy attached to it:
 

_im-plugin/ism/policies.md

@@ -517,10 +517,12 @@ The destination system **must** return a response otherwise the `error_notificat
 
 You can use the same options for `ctx` variables as the [notification](#notification) operation.
 
-## Sample policy with ISM template
+## Sample policy with ISM template for auto rollover
 
 The following sample template policy is for a rollover use case.
 
+If you want to skip rollovers for an index, use the [update cluster settings API]({{site.url}}{{site.baseurl}}/opensearch/configuration/#update-cluster-settings-using-the-api) to set `index.plugins.index_state_management.rollover_skip` to true.
+
 1. Create a policy with an `ism_template` field:
 
    ```json

_opensearch/rest-api/index-apis/delete-index.md

@@ -3,7 +3,7 @@ layout: default
 title: Delete index
 parent: Index APIs
 grand_parent: REST API reference
-nav_order: 5
+nav_order: 10
 ---
 
 # Delete index

_opensearch/rest-api/index-apis/get-index.md

@@ -3,7 +3,7 @@ layout: default
 title: Get index
 parent: Index APIs
 grand_parent: REST API reference
-nav_order: 10
+nav_order: 20
 ---
 
 # Get index