Merge pull request #102283 from tchristiani/minor-fixes-24JAN20

spelling and grammar

Author: PRMerger15

articles/search/cognitive-search-working-with-skillsets.md

@@ -52,7 +52,7 @@ For the rest of this document, we will assume we are working with [hotel reviews
 Each skill requires a context. A context determines:
 +	The number of times the skill executes, based on the nodes selected. For context values of type collection, adding an ```/*``` at the end will result in the skill being invoked once for each instance in the collection. 
 +	Where in the enrichment tree the skill outputs are added. Outputs are always added to the tree as children of the context node. 
-+	Shape of the inputs. For multi level collections, setting the context to the parent collection will affect the shape of the input the skill. For example if you have an enrichment tree with a list of countries, each enriched with a list of states containing a list of zipcodes.
++	Shape of the inputs. For multi level collections, setting the context to the parent collection will affect the shape of the input for the skill. For example if you have an enrichment tree with a list of countries, each enriched with a list of states containing a list of zipcodes.
 
 |Context|Input|Shape of Input|Skill Invocation|
 |---|---|---|---|
@@ -61,7 +61,7 @@ Each skill requires a context. A context determines:
 
 ### SourceContext
 
-The `sourceContext` is only used in skill inputs and [projections](knowledge-store-projection-overview.md). It is used to construct multi-level, nested objects. You may need to create a new oject to either pass it as an input to a skill or project into the knowledge store. As enrichment nodes may not be a valid JSON object in the enrichment tree and refrencing an node in the tree only returns that state of the node when it was created, using the enrichments as skill inputs or projections requires you to create a well formed JSON object. The `sourceContext` enables you to construct a hierarchical, anonymous type object, which would require multiple skills if you were only using the context. Using `sourceContext` is shown in the next section. Look at the skill output that generated an enrichment to determine if it is a valid JSON object and not a primitive type.
+The `sourceContext` is only used in skill inputs and [projections](knowledge-store-projection-overview.md). It is used to construct multi-level, nested objects. You may need to create a new object to either pass it as an input to a skill or project into the knowledge store. As enrichment nodes may not be a valid JSON object in the enrichment tree and referencing a node in the tree only returns that state of the node when it was created, using the enrichments as skill inputs or projections requires you to create a well formed JSON object. The `sourceContext` enables you to construct a hierarchical, anonymous type object, which would require multiple skills if you were only using the context. Using `sourceContext` is shown in the next section. Look at the skill output that generated an enrichment to determine if it is a valid JSON object and not a primitive type.
 
 ### Projections
 
@@ -111,7 +111,7 @@ The colors of the connectors in the tree above indicate that the enrichments wer
 
 ## Save enrichments in a knowledge store 
 
-Skillsets also define a knowledge store where your enriched documents can be projected as tables or objects. To save your enriched data in the knowledge store, you define a set of projections of your enriched document. To learn more about the knowledge store see [knowledge store overview](knowledge-store-concept-intro.md)
+Skillsets also define a knowledge store where your enriched documents can be projected as tables or objects. To save your enriched data in the knowledge store, you define a set of projections for your enriched document. To learn more about the knowledge store see [knowledge store overview](knowledge-store-concept-intro.md)
 
 ### Slicing projections