review of Executor's documentation
# Elasticsearch Executor
-The Elasticsearch Executor is an executor that extracts data from a Tornado Action and sends
+The Elasticsearch Executor is a functionality that extracts data from a Tornado Action and sends
it to [Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-apis.html).
-
-
## How It Works
-This executor expects a Tornado Action that includes the following elements in its payload:
+The executor expects a Tornado Action that includes the following elements in its payload:
1. An __endpoint__ : The Elasticsearch endpoint which Tornado will call to create the Elasticsearch document.
1. An __index__ : The name of the Elasticsearch index in which the document will be created.
1. An __data__: The content of the document that will be sent to Elasticsearch.
+1. (**optional**) An __auth__: a method of authentication, see next section.
-An example of a valid Tornado Action is:
+An example of a valid Tornado Action is a json document like this:
```json
{
"id": "elasticsearch",
@@ -30,20 +29,22 @@ An example of a valid Tornado Action is:
```
The Elasticsearch Executor will create a new document in the specified Elasticsearch index for each action
-executed. The specified index will be created if it does not already exist in Elasticsearch.
+executed; also the specified index will be created if it does not already exist.
-
-With this json the default authentication method created during the executor creation is used.
-An action can define a specific authentication method as described in the next section.
+In the above json document, no authentication is specified, therefore the default authentication method
+created during the executor creation is used. This method is saved in a tornado configuration file
+(`elasticsearch_executor.toml`) and can be overridden for each Tornado Action, as described in the next
+section.
## Elasticsearch authentication
-When the Elasticsearch executor is created, a default authentication method can be specified.
-In this case, if not differently specified by the action, this method will be used to authenticate to
-Elasticsearch. On the contrary, if a default method is not defined at creation time, then each action
-that does not specify an authentication method will fail.
-To use a specific authentication method the action should include the `auth` field with one of the following
-authentication types:
+When the Elasticsearch executor is created, a default authentication method can be specified and will be used
+to authenticate to Elasticsearch, if not differently specified by the action. On the contrary, if a default
+method is **not** defined at creation time, then each action that does not specify an authentication method
+**will fail**.
+
+To use a specific authentication method the action should include the `auth` field with either of the
+following authentication types: **None** or **PemCertificatePath**, like shown in the following examples.
* **None**: the client connects to Elasticsearch without authentication
