[DOCS] Tidied up various doc formatting errors

docs/reference/indices/flush.asciidoc

@@ -13,16 +13,6 @@ trigger flush operations as required in order to clear memory.
 $ curl -XPOST 'http://localhost:9200/twitter/_flush'
 --------------------------------------------------
 
-[float]
-=== Request Parameters
-
-The flush API accepts the following request parameters:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Name |Description
-|=======================================================================
-
 [float]
 === Multi Index
 

docs/reference/indices/optimize.asciidoc

@@ -17,26 +17,23 @@ $ curl -XPOST 'http://localhost:9200/twitter/_optimize'
 
 The optimize API accepts the following request parameters:
 
-[cols="<,<",options="header",]
-|=======================================================================
-|Name |Description
-|max_num_segments |The number of segments to optimize to. To fully
+[horizontal]
+`max_num_segments`:: The number of segments to optimize to. To fully
 optimize the index, set it to `1`. Defaults to simply checking if a
 merge needs to execute, and if so, executes it.
 
-|only_expunge_deletes |Should the optimize process only expunge segments
+`only_expunge_deletes`:: Should the optimize process only expunge segments
 with deletes in it. In Lucene, a document is not deleted from a segment,
 just marked as deleted. During a merge process of segments, a new
 segment is created that does not have those deletes. This flag allow to
 only merge segments that have deletes. Defaults to `false`.
 
-|flush |Should a flush be performed after the optimize. Defaults to
+`flush`::  Should a flush be performed after the optimize. Defaults to
 `true`.
 
-|wait_for_merge |Should the request wait for the merge to end. Defaults
+`wait_for_merge`:: Should the request wait for the merge to end. Defaults
 to `true`. Note, a merge can potentially be a very heavy operation, so
 it might make sense to run it set to `false`.
-|=======================================================================
 
 [float]
 === Multi Index

docs/reference/search/request/named-queries-and-filters.asciidoc

@@ -1,5 +1,5 @@
 [[search-request-named-queries-and-filters]]
-== Named Queries and Filters
+==== Named Queries and Filters
 
 Each filter and query can accept a `_name` in its top level definition.
 
@@ -51,9 +51,9 @@ query (just so there will be a place to set a name for it), for example:
 }
 --------------------------------------------------
 
-=== Named queries
+===== Named queries
 
 added[0.90.4]
 
 The support for the `_name` option on queries as available from version `0.90.4` and the support on filters is available
-also in versions before `0.90.4`.
+also in versions before `0.90.4`.

docs/reference/search/request/search-type.asciidoc

@@ -128,7 +128,7 @@ returned. The total_hits will be maintained between scroll requests.
 Note, scan search type does not support sorting (either on score or a
 field) or faceting.
 
-=== Clear scroll api
+===== Clear scroll api
 
 added[0.90.4]
 
@@ -148,4 +148,4 @@ If all scroll ids need to be cleared the reserved `_all` value can used instead
 [source,js]
 --------------------------------------------------
 curl -XDELETE 'localhost:9200/_search/scroll/_all'
---------------------------------------------------
+--------------------------------------------------