diff --git a/Week10/elasticsearch.md b/Week10/elasticsearch.md
index 497c32f..8ac69a9 100644
--- a/Week10/elasticsearch.md
+++ b/Week10/elasticsearch.md
@@ -329,7 +329,7 @@ Let's assume the data is in the following format when it gets posted to elastic
 }
 ```
 
-The next thing we want to do is to make sure that our the propertie key will not be stored as ```second.py``` and ```cool_function``` but as a single piece ```second.py-cool_function```.
+The next thing we want to do is to make sure that our the property key will not be stored as ```second.py``` and ```cool_function``` but as a single piece ```second.py-cool_function```.
 
 In order to do that we could execute the following script.
 ```bash
@@ -372,4 +372,4 @@ The following code takes all executions in and looks at the properties key and t
 
 We take both the key and token properties and tell elastic search to store these single fields as two properties. First as the original string which we say is not analyzed, which means that if we now query the propertie key by key.original_key then we are asking elastic to filter out where each key is exactly as it was when it got saved (ex. ```second.py-cool_function```).
 
-On the other hand if we still want to be able to look it up in a clever way elastic has also saved the properties like it wants to. So if we query by key as before we'll get the key split up on dashes like the default mapping behavior wants to. You can read more about mapping [here](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)
\ No newline at end of file
+On the other hand if we still want to be able to look it up in a clever way elastic has also saved the properties like it wants to. So if we query by key as before we'll get the key split up on dashes like the default mapping behavior wants to. You can read more about mapping [here](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)