Some phrasing and spelling updates.

Author: simonprickett

docs/003-create-index.md

@@ -4,26 +4,26 @@ Before creating the index let's describe the dataset and insert entries.
 
 ## Sample Dataset
 
-In this project you will use a simple dataset describging movies, for now, all record are in English. You will learn more about other languages in another tutorial.
+In this project you will use a simple dataset describing movies, for now, all records are in English. You will learn more about other languages in another tutorial.
 
 A movie is represented by the following attributes:
 
 * **`movie_id`** : The unique ID of the movie, internal to this database
 * **`title`** : The title of the movie.
 * **`plot`** : A summary of the movie.
-* **`genre`** : The genre of the movie, for now a movie will only h ave one single genre.
-* **`release_year`** : The year the movie has been released as a numerical value.
-* **`rating`** : The ratings from the public numerical value.
+* **`genre`** : The genre of the movie, for now a movie will only have a single genre.
+* **`release_year`** : The year the movie was released as a numerical value.
+* **`rating`** : A numeric value representing the public's rating for this movie.
 * **`votes`** : Number of votes.
 * **`poster`** : Link to the movie poster.
 * **`imdb_id`** : id of the movie in the [IMDB](https://imdb.com) database.
 
 
 ### Key and Data structure
 
-As a Redis developer, one of the first thing to look when building your application is to define the structure of the key and data (data design/data modeling).
+As a Redis developer, one of the first things to look when building your application is to define the structure of the key and data (data design/data modeling).
 
-A common way of defining the keys in Redis is to use specific pattern in them for example in this application when the database will probably deal with various business objects: movies, actors, theaters, users, ... we can use the following pattern:
+A common way of defining the keys in Redis is to use specific patterns in them. For example in this application where the database will probably deal with various business objects: movies, actors, theaters, users, ... we can use the following pattern:
 
 * `business_object:key`
 
@@ -32,14 +32,14 @@ For example:
 * `user:001` the user with the id 001
 
 
-and for the movies information you should use a Rediss [Hashes](https://redis.io/topics/data-types#hashes). 
+and for the movies information you should use a Redis [Hash](https://redis.io/topics/data-types#hashes). 
 
-A Redis Hash will allow the application to structure all the movie attributes in individual field; also RediSearch will index the fields based on the index definition.
+A Redis Hash allows the application to structure all the movie attributes in individual fields; also RediSearch will index the fields based on the index definition.
 
 ## Insert Movies
 
 
-It is time now to add some data into your database, let's insert few movies, using `redis-cli` or [Redis Insight](https://redislabs.com/redisinsight/).
+It is time now to add some data into your database, let's insert a few movies, using `redis-cli` or [Redis Insight](https://redislabs.com/redisinsight/).
 
 Once you are connected to your Redis instance run the following commands:
 
@@ -55,7 +55,7 @@ Once you are connected to your Redis instance run the following commands:
 
 ```
 
-Now it is possible to get information from the hash using the movie ID for example if you want to get the title, and rating execute the following command:
+Now it is possible to get information from the hash using the movie ID. For example if you want to get the title, and rating execute the following command:
 
 ```
 > HMGET movie:11002 title rating
@@ -71,23 +71,23 @@ And you can increment the rating of this movie using:
 "8.8"
 ```
 
-But how do you get a movie or list of movies from the release year, rating value or title?
+But how do you get a movie or list of movies by year of release, rating or title?
 
-One option, would be to read all the movies, check all fields and then return the movies; no need to say that it is a really bad idea.
+One option, would be to read all the movies, check all fields and then return only matching movies; no need to say that this is a really bad idea.
 
-Nevertheless this is where Redis developer are creating custom secondary index using SET/SORTED SET structures that point back to the movie hash. This needs some heavy design and implementation.
+Nevertheless this is where Redis developers often create custom secondary indexes using SET/SORTED SET structures that point back to the movie hash. This needs some heavy design and implementation.
 
-This is where RediSearch module is helping, and why it as been created.
+This is where the RediSearch module can help, and why it was created.
 
 
 ## RediSearch & Indexing
 
 
-RediSearch simplifies a lot this by offering a simple and automatic way to create secondary indices on Redis Hashes. (more datastructure will eventually come)
+RediSearch greatly simplifies 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/RediSearch/redisearch-getting-started/blob/master/docs/images/secondary-index.png?raw=true)
 
-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:
+Using RediSearch if you want to query on a field, you must first index that field. Let's start by indexing the following fields for our movies:
 
 * Title
 * Release Year
@@ -101,7 +101,7 @@ When creating a index you define:
 
 > ***Warning: Do not index all fields***
 >
-> Indexes take space in memory, and must be updated when the primary data is updated. So create the index carefully and keep the definition up to date with your need.
+> Indexes take space in memory, and must be updated when the primary data is updated. So create the index carefully and keep the definition up to date with your needs.
 
 ### Create the Index
 
@@ -115,9 +115,9 @@ Before running some queries let's look at the command in detail:
 
 * [`FT.CREATE`](https://oss.redislabs.com/redisearch/master/Commands/#ftcreate) : creates an index with the given spec. The index name will be used in all the key names so keep it short.
 * `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* 
+* `ON hash` : the type of structure to be indexed. *Note that in RediSearch 2.0 only hash structures are supported, this parameter will accept other Redis data types in future as RediSearch is updated to index them* 
 * `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](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.
+* `SCHEMA ...`: defines 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).