Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Commit dc7e5d6

Browse files
committed
Edited 030_Data/10_Index.asciidoc with Atlas code editor
1 parent 0de1063 commit dc7e5d6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

030_Data/10_Index.asciidoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[[index-doc]]
22
=== Indexing a Document
33

4-
Documents are _indexed_--stored and made ((("documents", "indexing")))((("indexes", "indexing a document")))searchable--by using the `index`
4+
Documents are _indexed_—stored and made ((("documents", "indexing")))((("indexes", "indexing a document")))searchable--by using the `index`
55
API. But first, we need to decide where the document lives. As we just
66
discussed, a document's `_index`, `_type`, and `_id` uniquely identify the
77
document. We can either provide our own `_id` value or let the `index` API
@@ -57,7 +57,7 @@ and includes the `_index`, `_type`, and `_id` metadata, and a new element:
5757

5858
Every document in Elasticsearch has a version number. Every time a change is
5959
made to a document (including deleting it), the `_version` number is
60-
incremented. In <<version-control>>, we discuss how to use the `_version`
60+
incremented. In <<version-control>>, we discuss how to use the `_version`
6161
number to ensure that one part of your application doesn't overwrite changes
6262
made by another part.
6363

0 commit comments

Comments
 (0)