Fix: Typo for both, initialization, variety (#705)

## Which problem is this PR solving?
- Part of #701 


## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits

Signed-off-by: JeevaRamanathan <jeevaramanathan.m@infosys.com>

content/docs/1.15/operator.md

@@ -415,7 +415,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.16/operator.md

@@ -477,7 +477,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.17/deployment.md

@@ -300,7 +300,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.17/operator.md

@@ -598,7 +598,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.18/deployment.md

@@ -301,7 +301,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.18/operator.md

@@ -615,7 +615,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.19/deployment.md

@@ -301,7 +301,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.19/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.20/deployment.md

@@ -301,7 +301,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.20/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.21/deployment.md

@@ -301,7 +301,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.21/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.22/deployment.md

@@ -299,7 +299,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.22/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.23/deployment.md

@@ -299,7 +299,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.23/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.24/deployment.md

@@ -410,7 +410,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.24/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.25/deployment.md

@@ -410,7 +410,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.25/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.26/deployment.md

@@ -410,7 +410,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.26/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.27/deployment.md

@@ -410,7 +410,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.27/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.
 

content/docs/1.28/deployment.md

@@ -412,7 +412,7 @@ Rollover lets you configure when to roll over to a new index based on one or mor
 * `max_docs` - the maximum documents in the index.
 * `max_size` - the maximum estimated size of primary shards (since Elasticsearch 6.x). It uses [byte size units](https://www.elastic.co/guide/en/elasticsearch/reference/master/common-options.html#byte-units) `tb`, `gb`, `mb`.
 
-Rollover index management strategy is more complex than using the default daily indices and it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+Rollover index management strategy is more complex than using the default daily indices and it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 
 To learn more about rollover index management in Jaeger refer to this
 [article](https://medium.com/jaegertracing/using-elasticsearch-rollover-to-manage-indices-8b3d0c77915d).

content/docs/1.28/operator.md

@@ -619,7 +619,7 @@ The connection configuration to storage is derived from storage options.
 #### Elasticsearch rollover
 
 This index management strategy is more complicated than using the default daily indices and
-it requires an initialisation job to prepare the storage and two cron jobs to manage indices.
+it requires an initialization job to prepare the storage and two cron jobs to manage indices.
 The first cron job is used for rolling-over to a new index and the second for removing
 indices from read alias. The rollover feature is used when storage option `es.use-aliases` is enabled.