docs(README): automatic update

  Update README Python
  [This list might not be relevant]
  refactor: Renaming attributes (#132)

* refactor: Renaming attributes

Specifically, this commit replaces:
 - attributesToIndex with searchableAttributes
 - numericAttributesToIndex with numericAttributesForFiltering

* refactor: Renaming `forwardToSlaves` into `forwardToReplicas`

* Display legacy names in parameter descriptions

Settings: Fix `indexing` scope instead of `settings` (#139) [ci skip]

Author: algoliareadmebot

README.md

@@ -192,7 +192,7 @@ index.set_settings({"customRanking": ["desc(followers)"]})
 You can also configure the list of attributes you want to index by order of importance (first = most important):
 
 ```python
-index.set_settings({"attributesToIndex": ["lastname", "firstname", "company", 
+index.set_settings({"searchableAttributes": ["lastname", "firstname", "company", 
                                          "email", "city", "address"]})
 ```
 
@@ -760,9 +760,9 @@ index.set_settings({"customRanking": ["desc(followers)"]})
 
 Performance wise, it's better to do a `` before pushing the data
 
-#### Slave settings
+#### Replica settings
 
-You can forward all settings updates to the slaves of an index by using the `forwardToSlaves` option:
+You can forward all settings updates to the replicas of an index by using the `forwardToReplicas` option:
 
 ```python
 index.set_settings({"customRanking": ["desc(followers)"]}, True)
@@ -774,14 +774,14 @@ index.set_settings({"customRanking": ["desc(followers)"]}, True)
 
 <!--PARAMETERS_LINK-->
 
-Here is the list of parameters you can use with the set settings method (`indexing` [scope](#scope))
+Here is the list of parameters you can use with the set settings method (`settings` [scope](#scope)).
 
 
-Parameters that can be overridden at search time also have the `search` [scope](#scope)
+Parameters that can be overridden at search time also have the `search` [scope](#scope).
 
 **Attributes**
 
-- [attributesToIndex](#attributestoindex) `settings`
+- [searchableAttributes](#searchableattributes) `settings`
 - [attributesForFaceting](#attributesforfaceting) `settings`
 - [attributesToRetrieve](#attributestoretrieve) `settings`, `search`
 - [unretrievableAttributes](#unretrievableattributes) `settings`
@@ -790,7 +790,7 @@ Parameters that can be overridden at search time also have the `search` [scope](
 
 - [ranking](#ranking) `settings`
 - [customRanking](#customranking) `settings`
-- [slaves](#slaves) `settings`
+- [replicas](#replicas) `settings`
 
 **Filtering / Faceting**
 
@@ -834,7 +834,7 @@ Parameters that can be overridden at search time also have the `search` [scope](
 
 - [attributeForDistinct](#attributefordistinct) `settings`
 - [distinct](#distinct) `settings`, `search`
-- [numericAttributesToIndex](#numericattributestoindex) `settings`
+- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
 - [allowCompressionOfIntegerArray](#allowcompressionofintegerarray) `settings`
 - [altCorrections](#altcorrections) `settings`
 - [placeholders](#placeholders) `settings`
@@ -866,7 +866,7 @@ They are three scopes:
 
 **Attributes**
 
-- [attributesToIndex](#attributestoindex) `settings`
+- [searchableAttributes](#searchableattributes) `settings`
 - [attributesForFaceting](#attributesforfaceting) `settings`
 - [unretrievableAttributes](#unretrievableattributes) `settings`
 - [attributesToRetrieve](#attributestoretrieve) `settings`, `search`
@@ -876,7 +876,7 @@ They are three scopes:
 
 - [ranking](#ranking) `settings`
 - [customRanking](#customranking) `settings`
-- [slaves](#slaves) `settings`
+- [replicas](#replicas) `settings`
 
 **Filtering / Faceting**
 
@@ -937,7 +937,7 @@ They are three scopes:
 - [attributeForDistinct](#attributefordistinct) `settings`
 - [distinct](#distinct) `settings`, `search`
 - [getRankingInfo](#getrankinginfo) `search`
-- [numericAttributesToIndex](#numericattributestoindex) `settings`
+- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
 - [allowCompressionOfIntegerArray](#allowcompressionofintegerarray) `settings`
 - [numericFilters (deprecated)](#numericfilters-deprecated) `search`
 - [tagFilters (deprecated)](#tagfilters-deprecated) `search`
@@ -963,11 +963,12 @@ The instant search query string, used to set the string you want to search in yo
 
 ### Attributes
 
-#### attributesToIndex
+#### searchableAttributes
 
 - scope: `settings`
 - type: `array of strings`
 - default: `*`
+- formerly known as: `attributesToIndex`
 
 
 The list of attributes you want index (i.e. to make searchable).
@@ -979,7 +980,7 @@ This parameter has two important uses:
 
 1. **Limit the attributes to index.** For example, if you store the URL of a picture, you want to store it and be able to retrieve it, but you probably don't want to search in the URL.
 
-2. **Control part of the ranking.** The contents of the `attributesToIndex` parameter impacts ranking in two complementary ways:
+2. **Control part of the ranking.** The contents of the `searchableAttributes` parameter impacts ranking in two complementary ways:
 
     First, the order in which attributes are listed defines their ranking priority: matches in attributes at the beginning of the list will be considered more important than matches in attributes further down the list. To assign the same priority to several attributes, pass them within the same string, separated by commas. For example, by specifying `["title,"alternative_title", "text"]`, `title` and `alternative_title` will have the same priority, but a higher priority than `text`.
 
@@ -1034,13 +1035,13 @@ You can also use `*` to retrieve all values when an **attributesToRetrieve** set
 
 - scope: `search`
 - type: `array of strings`
-- default: `attributesToIndex`
+- default: `searchableAttributes`
 
 
-List of attributes you want to use for textual search (must be a subset of the `attributesToIndex` index setting).
+List of attributes you want to use for textual search (must be a subset of the `searchableAttributes` index setting).
 Attributes are separated with a comma such as `"name,address"`.
 You can also use JSON string array encoding such as `encodeURIComponent("[\"name\",\"address\"]")`.
-By default, all attributes specified in the `attributesToIndex` settings are used to search.
+By default, all attributes specified in the `searchableAttributes` settings are used to search.
 
 
 ### Ranking
@@ -1060,7 +1061,7 @@ We have nine available criterion:
 * `geo`: Sort according to decreasing distance when performing a geo location based search.
 * `words`: Sort according to the number of query words matched by decreasing order. This parameter is useful when you use the `optionalWords` query parameter to have results with the most matched words first.
 * `proximity`: Sort according to the proximity of the query words in hits.
-* `attribute`: Sort according to the order of attributes defined by attributesToIndex.
+* `attribute`: Sort according to the order of attributes defined by searchableAttributes.
 * `exact`:
   * If the user query contains one word: sort objects having an attribute that is exactly the query word before others. For example, if you search for the TV show "V", you want to find it with the "V" query and avoid getting all popular TV shows starting by the letter V before it.
   * If the user query contains multiple words: sort according to the number of words that matched exactly (not as a prefix).
@@ -1088,11 +1089,12 @@ For example, `"customRanking" => ["desc(population)", "asc(name)"]`.
 To get a full description of how the Custom Ranking works,
 you can have a look at our [Ranking guide](https://www.algolia.com/doc/guides/relevance/ranking).
 
-#### slaves
+#### replicas
 
 - scope: `settings`
 - type: `array of strings`
 - default: `[]`
+- formerly known as: `slaves`
 
 
 The list of indices on which you want to replicate all write operations.
@@ -1103,7 +1105,7 @@ If you want to use different ranking configurations depending of the use case,
 you need to create one index per ranking configuration.
 
 This option enables you to perform write operations only on this index and automatically
-update slave indices with the same operations.
+update replica indices with the same operations.
 
 ### Filtering / Faceting
 
@@ -1375,7 +1377,7 @@ If set to true, plural won't be considered as a typo. For example, car and cars,
 
 
 List of attributes on which you want to disable typo tolerance
-(must be a subset of the `attributesToIndex` index setting).
+(must be a subset of the `searchableAttributes` index setting).
 
 Attributes are separated with a comma such as `"name,address"`.
 You can also use JSON string array encoding such as `encodeURIComponent("[\"name\",\"address\"]")`.
@@ -1633,7 +1635,7 @@ For most use cases, it is better to not use this feature as people search by key
 
 
 List of attributes on which you want to disable prefix matching
-(must be a subset of the `attributesToIndex` index setting).
+(must be a subset of the `searchableAttributes` index setting).
 
 This setting is useful on attributes that contain string that should not be matched as a prefix
 (for example a product SKU).
@@ -1647,7 +1649,7 @@ This setting is useful on attributes that contain string that should not be matc
 
 
 List of attributes on which you want to disable the computation of `exact` criteria
-(must be a subset of the `attributesToIndex` index setting).
+(must be a subset of the `searchableAttributes` index setting).
 
 #### exactOnSingleWordQuery
 
@@ -1727,11 +1729,12 @@ you can have a look at our [guide on distinct](https://www.algolia.com/doc/searc
 If set to true,
 the result hits will contain ranking information in the **_rankingInfo** attribute.
 
-#### numericAttributesToIndex
+#### numericAttributesForFiltering
 
 - scope: `settings`
 - type: `array of strings`
 - default: ``
+- formerly known as: `numericAttributesToIndex`
 
 
 All numerical attributes are automatically indexed as numerical filters
@@ -1994,21 +1997,21 @@ The move_index method will overwrite the destination index, and delete the tempo
 **Warning**
 
 The move_index operation will override all settings of the destination,
-There is one exception for the [slaves](#slaves) parameter which is not impacted.
+There is one exception for the [replicas](#replicas) parameter which is not impacted.
 
 For example, if you want to fully update your index `MyIndex` every night, we recommend the following process:
 
  1. Get settings and synonyms from the old index using [Get settings](#get-settings---get_settings)
   and [Get synonym](#get-synonym---get_synonym).
  1. Apply settings and synonyms to the temporary index `MyTmpIndex`, (this will create the `MyTmpIndex` index)
   using [Set settings](#set-settings) and [Batch synonyms](#batch-synonyms---batch_synonyms)
-  (make sure to remove the [slaves](#slaves) parameter from the settings if it exists).
+  (make sure to remove the [replicas](#replicas) parameter from the settings if it exists).
  1. Import your records into a new index using [Add objects](#add-objects---add_objects).
  1. Atomically replace the index `MyIndex` with the content and settings of the index `MyTmpIndex`
  using the [Move index](#move-index---move_index) method.
  This will automatically override the old index without any downtime on the search.
  1. You'll end up with only one index called `MyIndex`, that contains the records and settings pushed to `MyTmpIndex`
- and the slave-indices that were initially attached to `MyIndex` will be in sync with the new data.
+ and the replica-indices that were initially attached to `MyIndex` will be in sync with the new data.
 
 
 
@@ -2174,7 +2177,7 @@ public_key = client.generate_secured_api_key('YourSearchOnlyApiKey', {'restrictS
 
 This method saves a single synonym record into the index.
 
-In this example, we specify true to forward the creation to slave indices.
+In this example, we specify true to forward the creation to replica indices.
 By default the behavior is to save only on the specified index.
 
 ```python
@@ -2188,7 +2191,7 @@ index.save_synonym({
 ### Batch synonyms - `batch_synonyms`
 
 Use the batch method to create a large number of synonyms at once,
-forward them to slave indices if desired,
+forward them to replica indices if desired,
 and optionally replace all existing synonyms
 on the index with the content of the batch using the replaceExistingSynonyms parameter.
 
@@ -2197,7 +2200,7 @@ on a production index. This is the only way to ensure the index always
 has a full list of synonyms to use during the indexing of the new list.
 
 ```python
-# Batch synonyms, with slave forwarding and atomic replacement of existing synonyms
+# Batch synonyms, with replica forwarding and atomic replacement of existing synonyms
 index.batch_synonyms([{
   'objectID': 'a-unique-identifier',
   'type': 'synonym',
@@ -2224,10 +2227,10 @@ in the batch update.
 
 Use the normal index delete method to delete synonyms,
 specifying the objectID of the synonym record you want to delete.
-Forward the deletion to slave indices by setting the forwardToSlaves parameter to true.
+Forward the deletion to replica indices by setting the forwardToReplicas parameter to true.
 
 ```python
-# Delete and forward to slaves
+# Delete and forward to replicas
 index.delete_synonym('a-unique-identifier', True)
 ```
 
@@ -2242,7 +2245,7 @@ To atomically replace all synonyms of an index,
 use the batch method with the replaceExistingSynonyms parameter set to true.
 
 ```python
-# Clear synonyms and forward to slaves
+# Clear synonyms and forward to replicas
 index.clear_synonyms(True)
 ```