Fixed blocking issue

Author: HeidiSteen

articles/search/search-how-to-create-search-index.md

@@ -24,9 +24,9 @@ Write permissions on the search service are required for creating and loading in
 
 Index creation is largely a schema definition exercise. Before creating one, you should have:
 
-+ A clear idea of which fields you want to make searchable, retrievable, filterable, and sortable in your index.
++ A clear idea of which fields you want to make searchable, retrievable, filterable, facetable, and sortable in your index.
 
-  The attributes you assign to fields will determine its physical storage structure on the search service. During design and development, start with sample data so that you can drop and rebuild the index easily as you finalize field attribution.
+  The [field attribute assignments](search-what-is-an-index.md#index-attributes) will determine its physical storage structure on the search service. During design and development, start with sample data so that you can drop and rebuild the index easily as you finalize field attribution.
 
 + A source field that uniquely identifies each row, record, or item in the source data. If you're indexing from Blob Storage, the storage path is often used as the document key. 
 
@@ -38,7 +38,7 @@ Finally, all service tiers have [index limits](search-limits-quotas-capacity.md#
 
 ## Allowed updates
 
-[Create Index](/rest/api/searchservice/create-index) is an operation that creates physical data structures (files and inverted indexes) on your search service. Your ability to update an index is contingent upon whether the modification invalidates those physical structures. Most field attributes can't be changed once the field is created in your index.
+[Create Index](/rest/api/searchservice/create-index) is an operation that creates physical data structures (files and inverted indexes) on your search service. Your ability to effect changes using [Update Index](/rest/api/searchservice/update-index) is contingent upon whether the modification invalidates those physical structures. Most field attributes can't be changed once the field is created in your index.
 
 To minimize churn in the design process, the following table describes which elements are fixed and flexible in the schema. Changing a fixed element requires an index rebuild, whereas flexible elements can be changed at any time without impacting the physical implementation. 
 
@@ -60,20 +60,21 @@ To minimize churn in the design process, the following table describes which ele
 
 ## Schema checklist
 
-Use this checklist to help drive design decisions for your search index.
+Use this checklist to help drive the design decisions for your search index.
 
 1. Review [naming conventions](/rest/api/searchservice/naming-rules) so that index and field names conform to the naming rules.
 
-1. Review [supported data types](/rest/api/searchservice/supported-data-types). Data type will impact how the field is used. For example, numeric content is filterable but not full text searchable.
+1. Review [supported data types](/rest/api/searchservice/supported-data-types). The data type will impact how the field is used. For example, numeric content is filterable but not full text searchable.
 
-1. Identify one field in the data source that will be used as the key field in your index.
+1. Identify one field in the data source that contains unique values, allowing it to function as the key field in your index.
 
-1. Identify which source fields have searchable content. If the content is text and verbose (phrases or longer), experiment with different analyzers to see how the text is tokenized.
+1. Identify the fields in your data source that can contribute searchable content in the index. Searchable content are short or long strings that are queried using the full text search engine. If the content is verbose (small phrases or bigger chunks), experiment with different analyzers to see how the text is tokenized.
 
 1. Identify which source fields can be used as filters. Numeric content and short text fields, particularly those with repeating values, are good choices. When working with filters, remember:
 
-  + Filterable fields can optionally be used in faceted navigation. 
-  + Filterable fields are returned in arbitrary order, so consider making them sortable as well.
+   + Filterable fields can optionally be used in faceted navigation.
+
+   + Filterable fields are returned in arbitrary order, so consider making them sortable as well.
 
 ## Formulate a request