Fix typos in documentation (#698)

heysachin · web-flow · commit ed4dad2b4c7e · 2020-05-15T14:50:24.000+08:00
* Clean up documentation

* Update feature-retrieval.md
diff --git a/docs/user-guide/feature-retrieval.md b/docs/user-guide/feature-retrieval.md
@@ -55,7 +55,7 @@ Historical feature retrieval can be done through either the Feast SDK or directl
 features = self._features + [self._target]
 
 # Retrieve training dataset from Feast. The "entity_df" is a dataframe that contains
-# timestamps and entity keys. In this case it is a dataframe with two columns.
+# timestamps and entity keys. In this case, it is a dataframe with two columns.
 # One timestamp column, and one customer id column
 dataset = client.get_batch_features(
     feature_refs=features,
@@ -71,7 +71,7 @@ In the above example, Feast does a point in time correct query from a single fea
 
 This is called a point in time correct join.
 
-Feast allows users to retrieve features from any feature sets and join them to gether in a single response dataset. The only requirement is that the user provide the correct entities in order to look up the features.
+Feast allows users to retrieve features from any feature sets and join them together in a single response dataset. The only requirement is that the user provides the correct entities in order to look up the features.
 
 ### **Point-in-time-correct Join**
 
@@ -81,14 +81,15 @@ Below is another example of how a point-in-time-correct join works. We have two
 
 ![Input 2: Driver DataFrame](https://lh3.googleusercontent.com/LRtCOzmcfhLWzpyndbRKZSVPanLLzfULoHx2YxY6N3i1gQd2Eh6MS1igahOe8ydA7zQulIFJEaQ0IXFXOsdkKRobOC6ThSOnT4hACbCl1jeM4O2JDVC_kvw8lwTCezVUD3d6ZUYj31Q)
 
-Typically the `input 1` DataFrame would be provided by the user, and the `input 2` DataFrame would already be ingested into Feast. In order to join these two, the user would call Feast as follows:
+Typically the `input 1` DataFrame would be provided by the user, and the `input 2` DataFrame would already be ingested into Feast. To join these two, the user would call Feast as follows:
 
 ```python
 # Feature references
 features = [
  'conv_rate',
  'acc_rate',
  'avg_daily_trips',
+ 'trip_completed'
  ]
 
 
@@ -124,5 +125,5 @@ data = client.get_online_features(
     )
 ```
 
-Online serving with Feast is built to be very low latency. Feast Serving provides a [gRPC API](https://api.docs.feast.dev/grpc/feast.serving.pb.html) that is backed by [Redis](https://redis.io/). We also provide support for [Python](https://api.docs.feast.dev/python/), [Go](https://godoc.org/github.com/gojek/feast/sdk/go), and Java clients.
+Online serving with Feast is built to be very low latency. Feast Serving provides a [gRPC API](https://api.docs.feast.dev/grpc/feast.serving.pb.html) that is backed by [Redis](https://redis.io/). We also provide support for [Python](https://api.docs.feast.dev/python/), [Go](https://godoc.org/github.com/gojek/feast/sdk/go), and Java clients. 
 
