Merge pull request #5 from opendistro/master

merging

Author: ashwinkumar12345

docs/alerting/api.md

@@ -836,7 +836,7 @@ PUT _opendistro/_alerting/destinations/<destination-id>
 #### Request
 
 ```
-_opendistro/_alerting/destinations/<destination-id>
+DELETE _opendistro/_alerting/destinations/<destination-id>
 ```
 
 #### Sample response

docs/alerting/cron.md

@@ -16,7 +16,7 @@ Minute | 0-59
 Hour | 0-23
 Day of month | 1-31
 Month | 1-12
-Day of week | 0-7 (0 and 7 are both Sunday)
+Day of week | 0-7 (0 and 7 are both Sunday) or SUN, MON, TUE, WED, THU, FRI, SAT
 
 For example, the following expression translates to "every Monday through Friday at 11:30 AM":
 

docs/elasticsearch/cluster.md

@@ -327,7 +327,7 @@ In this case, all primary shards are allocated to `odfe-d2`. Again, all replica
 
 A popular approach is to configure your [index templates](../index-templates/) to set the `index.routing.allocation.require.temp` value to `hot`. This way, Elasticsearch stores your most recent data on your hot nodes.
 
-{% comment %}You can then use the [Index State Management (ISM)](../../ism/index/) plugin to periodically check the age of an index and specify actions to take on it. For example, when the index reaches a specific age, change the `index.routing.allocation.require.temp` setting to `warm` to automatically move your data from hot nodes to warm nodes.{% endcomment %}
+You can then use the [Index State Management (ISM)](../../ism/index/) plugin to periodically check the age of an index and specify actions to take on it. For example, when the index reaches a specific age, change the `index.routing.allocation.require.temp` setting to `warm` to automatically move your data from hot nodes to warm nodes.
 
 
 ## Next steps

docs/elasticsearch/index-templates.md

@@ -23,13 +23,13 @@ Index templates let you initialize new indices with predefined mappings and sett
 To create an index template, use a POST request:
 
 ```json
-POST _template
+POST _index_template
 ```
 
 This command creates a template named `daily_logs` and applies it to any new index whose name matches the regular expression `logs-2020-01-*` and also adds it to the `my_logs` alias:
 
 ```json
-PUT _template/daily_logs
+PUT _index_template/daily_logs
 {
   "aliases": {
     "my_logs": {}
@@ -116,25 +116,25 @@ GET _cat/templates
 To find a template by its name:
 
 ```json
-GET _template/daily_logs
+GET _index_template/daily_logs
 ```
 
 To get a list of all your templates:
 
 ```json
-GET _template/daily_logs
+GET _index_template/daily_logs
 ```
 
 To get a list of all templates that match a pattern:
 
 ```json
-GET _template/daily*
+GET _index_template/daily*
 ```
 
 To check if a specific template exists:
 
 ```json
-HEAD _template/<name>
+HEAD _index_template/<name>
 ```
 
 ## Configure multiple templates
@@ -150,7 +150,7 @@ For example, say you have the following two templates that both match the `logs-
 #### Template 1
 
 ```json
-PUT _template/template-01
+PUT _index_template/template-01
 {
   "index_patterns": [
     "logs*"
@@ -165,7 +165,7 @@ PUT _template/template-01
 #### Template 2
 
 ```json
-PUT _template/template-02
+PUT _index_template/template-02
 {
   "index_patterns": [
     "logs-2020-01-*"
@@ -184,7 +184,7 @@ Because `template-02` has a higher `order` value, it takes precedence over `temp
 You can delete an index template using its name, as shown in the following command:
 
 ```json
-DELETE _template/daily_logs
+DELETE _index_template/daily_logs
 ```
 
 ## Index template options

docs/elasticsearch/search-template.md

@@ -47,8 +47,7 @@ To run this search on a specific index, add the index name to the request:
 GET shakespeare/_search/template
 ```
 
-You can implement pagination using the `from` and `size` parameters.
-The `from` parameter indicates the document number that you want to start showing the results from. The `size` parameter refers to the number of results that you want to show. For example, if the value of `size` is 10 and the value of `from` is 0, you see the first 10 results. If you change the value of `from` to 10, you will see the next 10 results (because the results are zero-indexed). Each time the user clicks the next page for search results, your application must make the same search query with an incremented `from` value.
+Specify the `from` and `size` parameters:
 
 ```json
 GET _search/template