Update README [skip ci] (#253)

Author: algoliareadmebot

README.md

@@ -424,16 +424,16 @@ Parameters that can also be used in a setSettings also have the `indexing` [scop
 
 **Advanced**
 
-- [analyticsTags](#analyticstags) `search`
-- [synonyms](#synonyms) `search`
-- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 - [minProximity](#minproximity) `settings`, `search`
 - [responseFields](#responsefields) `settings`, `search`
 - [distinct](#distinct) `settings`, `search`
 - [getRankingInfo](#getrankinginfo) `search`
 - [numericFilters](#numericfilters) `search`
 - [tagFilters (deprecated)](#tagfilters-deprecated) `search`
 - [analytics](#analytics) `search`
+- [analyticsTags](#analyticstags) `search`
+- [synonyms](#synonyms) `search`
+- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 
 ## Search in indices - `multipleQueriesAsync` 
 
@@ -842,7 +842,7 @@ index.getSettingsAsync(new CompletionHandler() {
 index.setSettingsAsync(new JSONObject().append("customRanking", "desc(followers)"), null);
 ```
 
-You can find the list of parameters you can set in the [Settings Parameters](#settings-parameters) section
+You can find the list of parameters you can set in the [Settings Parameters](#index-settings-parameters) section
 
 **Warning**
 
@@ -918,19 +918,18 @@ Parameters that can be overridden at search time also have the `search` [scope](
 
 **performance**
 
-- [numericAttributesToIndex](#numericattributestoindex) `settings`
+- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
 - [allowCompressionOfIntegerArray](#allowcompressionofintegerarray) `settings`
 
 **Advanced**
 
 - [attributeForDistinct](#attributefordistinct) `settings`
-- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 - [placeholders](#placeholders) `settings`
 - [altCorrections](#altcorrections) `settings`
 - [minProximity](#minproximity) `settings`, `search`
 - [responseFields](#responsefields) `settings`, `search`
 - [distinct](#distinct) `settings`, `search`
-- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
+- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 
 
 # Parameters
@@ -1029,25 +1028,24 @@ They are three scopes:
 
 **performance**
 
-- [numericAttributesToIndex](#numericattributestoindex) `settings`
+- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
 - [allowCompressionOfIntegerArray](#allowcompressionofintegerarray) `settings`
 
 **Advanced**
 
 - [attributeForDistinct](#attributefordistinct) `settings`
-- [analyticsTags](#analyticstags) `search`
-- [synonyms](#synonyms) `search`
-- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 - [placeholders](#placeholders) `settings`
 - [altCorrections](#altcorrections) `settings`
 - [minProximity](#minproximity) `settings`, `search`
 - [responseFields](#responsefields) `settings`, `search`
 - [distinct](#distinct) `settings`, `search`
 - [getRankingInfo](#getrankinginfo) `search`
-- [numericAttributesForFiltering](#numericattributesforfiltering) `settings`
 - [numericFilters](#numericfilters) `search`
 - [tagFilters (deprecated)](#tagfilters-deprecated) `search`
 - [analytics](#analytics) `search`
+- [analyticsTags](#analyticstags) `search`
+- [synonyms](#synonyms) `search`
+- [replaceSynonymsInHighlight](#replacesynonymsinhighlight) `settings`, `search`
 
 ## Search
 
@@ -1066,7 +1064,7 @@ If no query parameter is set, the textual search will match with all the objects
 
 - scope: `settings`
 - type: `array of strings`
-- default: *
+- default: * (all string attributes)
 - formerly known as: `attributesToIndex`
 
 The list of attributes you want index (i.e. to make searchable).
@@ -1090,7 +1088,7 @@ This parameter has two important uses:
     will consider all positions inside the `text` attribute as equal, but positions inside the `title` attribute will still matter.
 
     You can decide to have the same priority for several attributes by passing them in the same string using comma as separator.
-    For example: \n`title` and `alternative_title` have the same priority in this example: `attributesToIndex:["title,alternative_title", "text"]`
+    For example: \n`title` and `alternative_title` have the same priority in this example: `searchableAttributes:["title,alternative_title", "text"]`
 
 To get a full description of how the ranking works, you can have a look at our [Ranking guide](https://www.algolia.com/doc/guides/relevance/ranking).
 
@@ -1236,7 +1234,7 @@ Like for the other filter for performance reason, it's not possible to have FILT
 
 It's not possible to mix different category of filter inside a OR like num=3 OR tag1 OR facet:value
 
-It's not possible to negate an group, it's only possible to negate a filters:  NOT(FILTER1 OR (FILTER2) is not allowed.
+It's not possible to negate an group, it's only possible to negate a filter:  NOT(FILTER1 OR FILTER2) is not allowed.
 
 #### facets
 
@@ -1799,16 +1797,20 @@ Specify the list of approximation that should be considered as an exact match in
 
 ## performance
 
-#### numericAttributesToIndex
+#### numericAttributesForFiltering
 
 - scope: `settings`
 - type: `array of strings`
 - default: []
+- formerly known as: `numericAttributesToIndex`
 
-All numerical attributes are automatically indexed as numerical filters.
-If you don't need filtering on some of your numerical attributes, please consider sending them as strings to speed up the indexing.
+All numerical attributes are automatically indexed as numerical filters
+(allowing filtering operations like `<` and `<=`).
+If you don't need filtering on some of your numerical attributes,
+you can specify this list to speed up the indexing.
 
-If you only need to filter on a numeric value with the operator `=` or `!=`, you can speed up the indexing by specifying the attribute with `equalOnly(AttributeName)`.
+If you only need to filter on a numeric value with the operator `=` or `!=`,
+you can speed up the indexing by specifying the attribute with `equalOnly(AttributeName)`.
 The other operators will be disabled.
 
 #### allowCompressionOfIntegerArray
@@ -1842,29 +1844,6 @@ then only the first one is kept and the others are removed from the results.
 To get a full understanding of how `Distinct` works,
 you can have a look at our [guide on distinct](https://www.algolia.com/doc/search/distinct).
 
-#### analyticsTags
-
-- scope: `search`
-- type: `array of strings`
-
-If set, tag your query with the specified identifiers. Tags can then be used in the Analytics to analyze a subset of searches only.
-
-#### synonyms
-
-- scope: `search`
-- type: `boolean`
-- default: true
-
-If set to `false`, the search will not use the synonyms defined for the targeted index.
-
-#### replaceSynonymsInHighlight
-
-- scope: `settings` `search`
-- type: `boolean`
-- default: true
-
-If set to `false`, words matched via synonyms expansion will not be replaced by the matched synonym in the highlighted result.
-
 #### placeholders
 
 - scope: `settings`
@@ -2000,21 +1979,6 @@ you can have a look at our [guide on distinct](https://www.algolia.com/doc/searc
 If set to YES,
 the result hits will contain ranking information in the **_rankingInfo** attribute.
 
-#### numericAttributesForFiltering
-
-- scope: `settings`
-- type: `array of strings`
-- default: []
-
-All numerical attributes are automatically indexed as numerical filters
-(allowing filtering operations like `<` and `<=`).
-If you don't need filtering on some of your numerical attributes,
-you can specify this list to speed up the indexing.
-
-If you only need to filter on a numeric value with the `=` operator,
-you can speed up the indexing by specifying the attribute with `equalOnly(AttributeName)`.
-The other operators will be disabled.
-
 #### numericFilters
 
 - scope: `search`
@@ -2067,6 +2031,29 @@ For example `{"_tags":["tag1","tag2"]}`.
 
 If set to false, this query will not be taken into account in the analytics.
 
+#### analyticsTags
+
+- scope: `search`
+- type: `array of strings`
+
+If set, tag your query with the specified identifiers. Tags can then be used in the Analytics to analyze a subset of searches only.
+
+#### synonyms
+
+- scope: `search`
+- type: `boolean`
+- default: true
+
+If set to `false`, the search will not use the synonyms defined for the targeted index.
+
+#### replaceSynonymsInHighlight
+
+- scope: `settings` `search`
+- type: `boolean`
+- default: true
+
+If set to `false`, words matched via synonyms expansion will not be replaced by the matched synonym in the highlighted result.
+
 
 # Manage Indices