diff --git a/docs/content/Data_formats.md b/docs/content/Data_formats.md
index 1a6c5b3393d..08917bca012 100644
--- a/docs/content/Data_formats.md
+++ b/docs/content/Data_formats.md
@@ -63,7 +63,7 @@ If you use the [indexing service](Indexing-Service.html) for ingesting the data,
 
 Specified here are the location of the datafile, the timestamp column, the format of the data, and the columns that will become dimensions in Druid.
 
-Since the CSV data does not contain the column names, they will have to be added before that data can be processed:
+Since the CSV data cannot contain the column names (no header is allowed), these must be added before that data can be processed:
 
 ```json
     "firehose" : {
diff --git a/docs/content/TimeseriesQuery.md b/docs/content/TimeseriesQuery.md
index e73e51df51e..97fc5ea2e6c 100644
--- a/docs/content/TimeseriesQuery.md
+++ b/docs/content/TimeseriesQuery.md
@@ -52,7 +52,7 @@ There are 7 main parts to a timeseries query:
 |granularity|Defines the granularity of the query. See [Granularities](Granularities.html)|yes|
 |filter|See [Filters](Filters.html)|no|
 |aggregations|See [Aggregations](Aggregations.html)|yes|
-|postAggregations|See [Post Aggregations](Post-Aggregations.html)|no|
+|postAggregations|See [Post Aggregations](Post-aggregations.html)|no|
 |intervals|A JSON Object representing ISO-8601 Intervals. This defines the time ranges to run the query over.|yes|
 |context|An additional JSON Object which can be used to specify certain flags.|no|
 
@@ -69,4 +69,4 @@ To pull it all together, the above query would return 2 data points, one for eac
     "result": { "sample_name1": <some_value>, "sample_name2": <some_value>, "sample_divide": <some_value> }
   }
 ]
-```
\ No newline at end of file
+```