From 241bb09db1cb107e256e413a21aa2e2735cc7916 Mon Sep 17 00:00:00 2001
From: Karel Minarik <karmi@elasticsearch.com>
Date: Thu, 23 Jan 2014 20:35:44 +0100
Subject: [PATCH] [DOCS] More assertive statement about requiring `query` in
 _count, etc

---
 docs/reference/migration/migrate_1_0.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reference/migration/migrate_1_0.asciidoc b/docs/reference/migration/migrate_1_0.asciidoc
index a684a9c1e1a..be53d64585c 100644
--- a/docs/reference/migration/migrate_1_0.asciidoc
+++ b/docs/reference/migration/migrate_1_0.asciidoc
@@ -175,7 +175,7 @@ behaviour can be reenabled on an index-by-index basis with the setting:
 While the `search` API takes a top-level `query` parameter, the
 <<search-count,`count`>>, <<docs-delete-by-query,`delete-by-query`>> and
 <<search-validate,`validate-query`>> requests expected the whole body to be a
-query. These have been changed to all accept a top-level `query` parameter:
+query. These now _require_ a top-level `query` parameter:
 
 [source,json]
 ---------------