Fix snippets

One bad path and one missing file. This fixes the bad path and replaces
the missing file with `// AUTOSENSE` rather than overriding the file.

Author: nik9000

054_Query_DSL/75_Combining_queries_together.asciidoc

@@ -145,7 +145,7 @@ will be identical, but it may aid in query simplicity/clarity.
     }
 }
 --------------------------------------------------
-// SENSE: 054_Query_DSL/70_bool_query.json
+// SENSE: 054_Query_DSL/70_Bool_query.json
 
 <1> A `term` query is placed inside the `constant_score`, converting it to a
 non-scoring filter.  This method can be used in place of a `bool` query which only

300_Aggregations/65_percentiles.asciidoc

@@ -76,7 +76,7 @@ POST /website/logs/_bulk
 { "index": {}}
 { "latency" : 319, "zone" : "EU", "timestamp" : "2014-10-29" }
 ----
-// SENSE: 300_Aggregations/65_percentiles.json
+// AUTOSENSE
 
 This data contains three values: a latency, a data center zone, and a date
 timestamp.  Let's run +percentiles+ over the whole dataset to get a feel for
@@ -101,7 +101,7 @@ GET /website/logs/_search
     }
 }
 ----
-// SENSE: 300_Aggregations/65_percentiles.json
+// AUTOSENSE
 <1> The `percentiles` metric is applied to the +latency+ field.
 <2> For comparison, we also execute an `avg` metric on the same field.
 
@@ -163,7 +163,7 @@ GET /website/logs/_search
     }
 }
 ----
-// SENSE: 300_Aggregations/65_percentiles.json
+// AUTOSENSE
 <1> First we separate our latencies into buckets, depending on their zone.
 <2> Then we calculate the percentiles per zone.
 <3> The +percents+ parameter accepts an array of percentiles that we want returned,
@@ -254,7 +254,7 @@ GET /website/logs/_search
     }
 }
 ----
-// SENSE: 300_Aggregations/65_percentiles.json
+// AUTOSENSE
 <1> The `percentile_ranks` metric accepts an array of values that you want ranks for.
 
 After running this aggregation, we get two values back: