瀏覽代碼

[Docs] Fix badly escaped keywords in migrate_7_0/search.asciidoc (#36964)

Damien Alexandre 6 年之前
父節點
當前提交
47f0a47f3d
共有 1 個文件被更改,包括 5 次插入4 次删除
  1. 5 4
      docs/reference/migration/migrate_7_0/search.asciidoc

+ 5 - 4
docs/reference/migration/migrate_7_0/search.asciidoc

@@ -174,9 +174,10 @@ major version.
 ==== `hits.total` is now an object in the search response
 
 The total hits that match the search request is now returned as an object
-with a `value` and a `relation`. `value indicates the number of hits that
-match and `relation indicates whether the value is accurate (`eq`) or a lower bound
+with a `value` and a `relation`. `value` indicates the number of hits that
+match and `relation` indicates whether the value is accurate (`eq`) or a lower bound
 (`gte`):
+
 ```
 {
     "hits": {
@@ -200,7 +201,7 @@ will be removed in the next major version (8.0).
 [float]
 ==== `hits.total` is omitted in the response if `track_total_hits` is disabled (false)
 
-If `track_total_hits` is set to `false in the search request the search response
+If `track_total_hits` is set to `false` in the search request the search response
 will set `hits.total` to null and the object will not be displayed in the rest
 layer. You can add `rest_total_hits_as_int=true` in the search request parameters
-to get the old format back (`"total": -1`).
+to get the old format back (`"total": -1`).