v0.2.47..v0.2.48 changeset FeatureFiltering.asciidoc

diff --git a/docs/user/FeatureFiltering.asciidoc b/docs/user/FeatureFiltering.asciidoc
index ca4a45f..e884d0c 100644
--- a/docs/user/FeatureFiltering.asciidoc
+++ b/docs/user/FeatureFiltering.asciidoc
@@ -2,21 +2,21 @@
 [[FeatureFiltering]]
 == Feature Filtering
 
-Feature filtering is supported during conflation in order to conflate a subset of the input features.  Feature filtering happens in 
+Feature filtering is supported during conflation in order to conflate a subset of the input features.  Feature filtering happens in
 two ways: 1) at the geometry/base feature type level and 2) more granularly at the tag/schema level.
 
 === Geometry and Base Fature Type Conflation Feature Filtering
 
-Conflation at the geometry/base feature type level is controlled with matchers.  An example of this type of conflation would be 
-Road Conflation or POI Conflation.  Hootenanny has a specific geometric and attribute related definition of what makes up a road or POI.  
-For an overview of the different types of conflation available in Hootenanny see the corresponding conflation related sections in this 
-document, as well as the documentation for the `match.creators` configuration option.  By default, Hootenanny enables all types of 
-conflation that it supports.  This ensures that a conflation job results in as much data conflated as possible.  If you desire to perform 
+Conflation at the geometry/base feature type level is controlled with matchers.  An example of this type of conflation would be
+Road Conflation or POI Conflation.  Hootenanny has a specific geometric and attribute related definition of what makes up a road or POI.
+For an overview of the different types of conflation available in Hootenanny see the corresponding conflation related sections in this
+document, as well as the documentation for the `match.creators` configuration option.  By default, Hootenanny enables all types of
+conflation that it supports.  This ensures that a conflation job results in as much data conflated as possible.  If you desire to perform
 certain types of conflation only, you can adjust the `match.creators` and `merger.creators` configuration options accordingly.
 
 === Tag and Schema Conflation Feature Filtering
 
-At a more granular level, Hootenanny allows for filtering out features during conflation via tag/schema relationships.  Hootenanny supports 
+At a more granular level, Hootenanny allows for filtering out features during conflation via tag/schema relationships.  Hootenanny supports
 specifying a JSON string or path to a file containing multiple logical AND/OR/NOT tag filters and allows for multiple filtering concepts:
 
 * Tag key/value string wildcard - basic tag string matching between features
@@ -24,7 +24,7 @@ specifying a JSON string or path to a file containing multiple logical AND/OR/NO
 * Aliases - include features that have tags that are aliases for other tags
 * Children/ancestors - include features that are either children or ancestors of the features they are being compared to
 * Associations - include features that have associations with other features in ways that do not fall into one of the other matching types (catch all similarity capability)
-* Categories - include features that fall into a user defined category 
+* Categories - include features that fall into a user defined category
 
 ==== Conflation Command Example
 
@@ -48,7 +48,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "amenity=restaurant"
@@ -61,7 +61,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "tourism=*"
@@ -74,7 +74,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "should": 
+  "should":
   [
     {
       "tag": "amenity=restaurant"
@@ -96,7 +96,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "amenity=hospital",
@@ -110,7 +110,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "amenity=restaurant",
@@ -124,7 +124,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "shop=mall"
@@ -143,7 +143,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "*address*=*"
@@ -156,7 +156,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "address*=*"
@@ -169,7 +169,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "*address=*"
@@ -182,7 +182,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "*=*address*"
@@ -195,7 +195,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "*=address*"
@@ -208,7 +208,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "*=*address"
@@ -221,7 +221,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "surface=gravel",
@@ -235,7 +235,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "highway=secondary",
@@ -249,7 +249,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "category": "transportation"
@@ -262,7 +262,7 @@ The tag/schema filtering capability is best explained through specific filter ex
 +
 -----
 {
-  "must": 
+  "must":
   [
     {
       "tag": "building:part=yes",