diff --git a/guide/reference/mapping/conf-mappings.textile b/guide/reference/mapping/conf-mappings.textile
index 5d9d32767..3c8625b9b 100644
--- a/guide/reference/mapping/conf-mappings.textile
+++ b/guide/reference/mapping/conf-mappings.textile
@@ -5,7 +5,7 @@ cat: guide
 sidebar: reference_mapping
 ---
 
-p. Creating new mappings can be done using the @put_mapping@ API. When a document is indexed with no mapping associated with it in the specific index, the "dynamic / default mapping":dynamic-mapping.html feature will kick in an automatically create mapping definition for it.
+p. Creating new mappings can be done using the @put_mapping@ API. When a document is indexed with no mapping associated with it in the specific index, the "dynamic / default mapping":dynamic-mapping.html feature will kick in and automatically create mapping definition for it.
 
 p. Mappings can also be provided on the node level, meaning that each index created will automatically be started with all the mappings defined within a certain location.
 
diff --git a/guide/reference/mapping/index.textile b/guide/reference/mapping/index.textile
index 06ed0b225..f4f900ea8 100644
--- a/guide/reference/mapping/index.textile
+++ b/guide/reference/mapping/index.textile
@@ -11,7 +11,7 @@ p. Explicit mapping is defined on an index/type level. By default, there isn't a
 
 h2. Mapping Types
 
-p. Mapping types are a way to try and divide the documents indexed into the same index into logical groups. Think of it as tables in a database. Though there is separation between types, its not a full separation (all end up as a document within the same Lucene index).
+p. Mapping types are a way to try and divide the documents indexed into the same index into logical groups. Think of it as tables in a database. Though there is separation between types, it's not a full separation (all end up as a document within the same Lucene index).
 
 p. Field names with the same name across types are highly recommended to have the same type and same mapping characteristics (analysis settings for example). There is an effort to allow to explicitly "choose" which field to use by using type prefix (@my_type.my_field@), but its not complete, and there are places where it will never work (like faceting on the field).
 
diff --git a/guide/reference/query-dsl/query-string-query.textile b/guide/reference/query-dsl/query-string-query.textile
index c3e07dd47..c44b95842 100644
--- a/guide/reference/query-dsl/query-string-query.textile
+++ b/guide/reference/query-dsl/query-string-query.textile
@@ -20,7 +20,7 @@ p. The @query_string@ top level parameters include:
 
 |_. Parameter |_. Description |
 | @query@ | The actual query to be parsed. |
-| @default_field@ | The default field for query terms if no prefix field is specified. Defaults to the @index.query.default_field@ index settings, which in turn defaults to @_all@ |
+| @default_field@ | The default field for query terms if no prefix field is specified. Defaults to the @index.query.default_field@ index settings, which in turn defaults to @_all@. |
 | @default_operator@ | The default operator used if no explicit operator is specified. For example, with a default operator of @OR@, the query @capital of Hungary@ is translated to @capital OR of OR Hungary@, and with default operator of @AND@, the same query is translated to @capital AND of AND Hungary@. The default value is @OR@. |
 | @analyzer@ | The analyzer name used to analyze the query string. |
 | @allow_leading_wildcard@ | When set, @*@ or @?@ are allowed as the first character. Defaults to @true@. |