update documentation

tgrall · tgrall · commit 2fe60dd5c7fd · 2020-09-16T12:34:59.000+02:00
diff --git a/docs/003-create-index.md b/docs/003-create-index.md
@@ -85,7 +85,7 @@ This is where RediSearch module is helping, and why it as been created.
 
 RediSearch simplifies a lot this by offering a simple and automatic way to create secondary indices on Redis Hashes. (more datastructure will eventually come)
 
-![Secondary Index](https://github.com/Redis-Developer/getting-started-redisearch/blob/master/docs/images/secondary-index.png)
+![Secondary Index](https://raw.githubusercontent.com/RediSearch/redisearch-getting-started/blob/master/docs/images/secondary-index.png)
 
 Using RediSearch if you want to query on a field, you must index the fields. Let's start by indexing the following fields in of our movies:
 
@@ -117,7 +117,7 @@ Before running some queries let's look at the command in detail:
 * `idx:movie` : the name of the index
 * `ON hash` : the type of structure to be indexed. *Note that in RediSearch 2.0 only hash structure are supported, this is parameter will allow RediSearch to index other structure in the future* 
 * `PREFIX 1 "movie:"` : the prefix of the keys that should be indexed. This is a list, so since we want to only index movie:* keys the number is 1. Suppose you want to index movies and tv_show that have the same fields, you can use: `PREFIX 2 "movie:" "tv_show:"` 
-* `SCHEMA ...`: define the schema, the fields and their type, to index, as you can see in the command, we are using TEXT, NUMERIC and TAG, and SORTABLE parameters.
+* `SCHEMA ...`: define the schema, the fields and their type, to index, as you can see in the command, we are using [TEXT](https://oss.redislabs.com/redisearch/Query_Syntax/#a_few_query_examples), [NUMERIC](https://oss.redislabs.com/redisearch/Query_Syntax/#numeric_filters_in_query) and [TAG](https://oss.redislabs.com/redisearch/Query_Syntax/#tag_filters), and [SORTABLE](https://oss.redislabs.com/redisearch/Sorting/) parameters.
 
 You can find information about the [FT.CREATE](https://oss.redislabs.com/redisearch/Commands/#ftcreate) command in the [documentation](https://oss.redislabs.com/redisearch/Commands/#ftcreate).
 
diff --git a/docs/004-query-data.md b/docs/004-query-data.md
@@ -4,10 +4,10 @@ The database contains few movies, and an index, it is not possible to execute so
 
 ## Queries
 
-**Example : *All the movies that contains the string "`star`"***
+**Example : *All the movies that contains the string "`war`"***
 
 ```
-> FT.SEARCH idx:movie "star"
+> FT.SEARCH idx:movie "war"
 
 1) (integer) 2
 2) "movie:11005"
@@ -26,14 +26,14 @@ The database contains few movies, and an index, it is not possible to execute so
 
 The FT.SEARCH commands returns the list of result starting with the number of results, then the list of elements (keys & fields).
 
-This example uses a simple query string `"star"`, this will return all the movies that *contain* the word star in a text field of the index.
+As you can see the movie *Star Wars: Episode V - The Empire Strikes Back* is found, even though you used only the word “war” to match “Wars” in the title. This is because the title has been indexed as text, so the field is [tokenized](https://oss.redislabs.com/redisearch/Escaping/) and [stemmed](https://oss.redislabs.com/redisearch/Stemming/).
 
 Later when looking in more details on the query syntax you will learn more the search capabilities.
 
 It is also possible to limit the list of fields returned by the query using the `RETURN` parameter, let's run the same query, and return only the title and release_year:
 
 ```
-> FT.SEARCH idx:movie "star" RETURN 2 title release_year
+> FT.SEARCH idx:movie "war" RETURN 2 title release_year
 
 1) (integer) 2
 2) "movie:11005"
@@ -53,17 +53,16 @@ This query does not specific any "field" and still return some movie, this is be
 If you need to do a query on a specific field you can specify it using the `@field:` syntax, for example:
 
 ```
-> FT.SEARCH idx:movie "@title:star" RETURN 2 title release_year
+> FT.SEARCH idx:movie "@title:war" RETURN 2 title release_year
 ```
 
-
 ---
-**Example : *All the movies that contains the string "`star` but NOT the `jedi` one"***
+**Example : *All the movies that contains the string "`war` but NOT the `jedi` one"***
 
 Adding the string `-jedi` (minus) will ask the query engine to not return the values that contain `jedi`.
 
 ```
-> FT.SEARCH idx:movie "star -jedi" RETURN 2 title release_year
+> FT.SEARCH idx:movie "war -jedi" RETURN 2 title release_year
 
 1) (integer) 1
 2) "movie:11002"
@@ -73,6 +72,21 @@ Adding the string `-jedi` (minus) will ask the query engine to not return the va
    4) "1980"
 ```
 
+---
+**Example : *All the movies that contains the string "`gdfather` using fuzzy search"***
+
+As you can see the word godfather is wrongly spelled, it is possible using a [fuzzy matching](https://oss.redislabs.com/redisearch/Query_Syntax/#fuzzy_matching). Fuzzy matches are performed based on [Levenshtein distance](https://en.wikipedia.org/wiki/Levenshtein_distance) (LD).
+
+```
+> FT.SEARCH idx:movie " %gdfather% " RETURN 2 title release_year
+
+1) (integer) 1
+2) "movie:11003"
+3) 1) "title"
+   2) "The Godfather"
+   3) "release_year"
+   4) "1972"
+```
 
 ---
 **Example  : *All `Thriller` movies"***
@@ -93,7 +107,6 @@ The syntax to query a TAG field is  @field_name:{value}
 
 ```
 
-
 ---
 **Example : *All `Thriller` or `Action` movies"***
 
@@ -153,7 +166,9 @@ or
 
 ```
 > FT.SEARCH idx:movie * FILTER release_year 1970 1980 RETURN 2 title release_year
+```
 
+```
 > FT.SEARCH idx:movie "@release_year:[1970 1980]" RETURN 2 title release_year
 
 1) (integer) 2
@@ -176,7 +191,6 @@ To exclude a value prepend it with `(` in the FILTER or query string, for exampl
 > FT.SEARCH idx:movie "@release_year:[1970 (1980]" RETURN 2 title release_year
 ```
 
-
 ---
 ## Insert, Update, Delete and Expire Documents
 
@@ -188,25 +202,25 @@ As part of this tutorial you have:
 
 When creating the index, using  the `idx:movie ON hash PREFIX 1 "movie:"` parameter you are asking the indexing engine to look at all existing keys and index them.
 
-Also any new information that match this pattern/type, will be indexed.
+Also new information that match this pattern/type, will be indexed.
 
-Let's count the number of movie and then add a new one, and count again:
+Let's count the number of movies, add a new one, and count again:
 
 ```
 > FT.SEARCH idx:movie "*" LIMIT 0 0
+
 1) (integer) 4
 
 
 > HSET movie:11033 title "Tomorrow Never Dies" plot "James Bond sets out to stop a media mogul's plan to induce war between China and the U.K in order to obtain exclusive global media coverage." release_year 1997 genre "Action" rating 6.5 votes 177732 imdb_id tt0120347
 
 > FT.SEARCH idx:movie "*" LIMIT 0 0
+
 1) (integer) 5
 
 ```
 
-The new movie has been indexed.
-
-You can also search on any of the indexed fields:
+The new movie has been indexed. You can also search on any of the indexed fields:
 
 ```
 > FT.SEARCH idx:movie "never" RETURN 2 title release_year
@@ -219,7 +233,7 @@ You can also search on any of the indexed fields:
    4) "1997"
 ```
 
-Let **update** one of the field, and search for `007`
+Now you **update** one of the field, and search for `007`
 
 ```
 > HSET movie:11033 title "Tomorrow Never Dies - 007"
@@ -235,7 +249,7 @@ Let **update** one of the field, and search for `007`
    4) "1997"
 ```
 
-When you *delete* the has the index is also updated, and the same happends when you are using expiration (TTL-Time To Live). 
+When you *delete* the hash, the index is also updated, and the same happens the the key is expired (TTL-Time To Live). 
 
 For example put a 20 sedonds expiration time to the James Bond movie:
 
@@ -253,7 +267,7 @@ You can run the following query, and you will see after 20 seconds the document
 
 ```
 
-> Note: When you are using Redis as your primary database you are not necessary using the TTL to delet record. However, if the data your are storing and indexing are transient, for example a caching layer at the top of another datastore or Web service, query user sessions content, ... This is often qualified as a "Ephemeral Search" use case: lighweight, fast and expiration.
+> Note: When you are using Redis as your primary database you are not necessary using the TTL to delet record. However, if the data your are storing and indexing are transient, for example a caching layer at the top of another datastore or Web service, query user sessions content, ... This is often qualified as a "[Ephemeral Search](https://redislabs.com/blog/the-case-for-ephemeral-search/)" use case: lighweight, fast and expiration.
 
 ---
 ##  More
diff --git a/docs/006-import-dataset.md b/docs/006-import-dataset.md
@@ -156,7 +156,7 @@ The theater hashes contain the following fields.
 
 ## Importing the Movies & Theaters
 
-Before importing the data, you can start by flushing your project database:
+Before importing the data, flush the database:
 
 ```
 > FLUSHALL
diff --git a/docs/007-query-movies.md b/docs/007-query-movies.md
@@ -211,7 +211,7 @@ TAG is the structure to use when you want to do exact match condition on string/
   </b></i>
   </summary>
 
-This is very similar to the previous query, you can pass a list of value with the `|` to represent the OR.
+This is  similar to the previous query, you can pass a list of value with the `|` to represent the OR.
 
 
 ```
@@ -289,9 +289,9 @@ In this query it will be twao condition with a OR (`|`).
 
 Summary
 
-* A fieldless query will apply to all TEXT fields and will use the words and their base form (stemming)
+* Fieldless queries apply to all TEXT fields and use the words and their base form (stemming)
 * To apply a condition to a specific field you must use the `@field:` notation
-* Multiple conditions are "intersection" (AND condition)
+* Multiple conditions are "intersection" (AND condition), to do an "union" (OR condition), you have to use the "`|`" character.
 
 ----
 ### Sort
@@ -319,18 +319,19 @@ A very common use case when querying data is to sort the data on a specific fiel
     4) "Mechanic: Resurrection"
 ```
 
-The first line contains the number of documents (`186`) that matche the query condition, the the list of movies.
+The first line contains the number of documents (`186`) that match the query condition.
 
-The FT.SEARCH command by default returns the first 10 documents, you will see in the next query how to paginate.
+The FT.SEARCH command, by default, returns the first ten documents. You will see in the next query how to paginate.
 
+You can only use one SORTBY in an FT.SEARCH query, if you want to sort on multiple fields, for example sorting movies by `genre` ascending and `release_year` descending, you have to use an FT.AGGREGATE, this is covered in the [next section](008-aggregation.md).
 
+Note: The field used in the [SORTBY](https://oss.redislabs.com/redisearch/Sorting/#specifying_sortby) should be part of the index schema and defined as SORTABLE.
 ---
 </details>
 
 ----
 ### Paginate
 
-
 <details> 
   <summary>
   <i><b>Query all the `Action` movies, sorted by release year from the oldest to the most recent one, returning the record by batch of 100 movies</b></i>
diff --git a/docs/009-application-development.md b/docs/009-application-development.md
@@ -12,7 +12,7 @@ You can find the same REST Service that uses RediSearch developed with different
 
 The frontend is created using a Vue.js application that let you run search queries using each of the REST backend.
 
-![Application Architecture](https://github.com/Redis-Developer/getting-started-redisearch/blob/master/docs/images/sample-app-archi.png)
+![Application Architecture](https://raw.githubusercontent.com/RediSearch/redisearch-getting-started/master/docs/images/sample-app-archi.png)
 
 
 ## Run the Sample Application
