Skip to content

Commit badfc93

Browse files
authored
1 parent 6925bc9 commit badfc93

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Docs live in **three places**:
1717

1818
1. **Reference content** lives in this repo. This covers low-level stuff like settings and configuration information that is tightly coupled to code.
1919
- 👩🏽‍💻 **Engineers** own the bulk of this content.
20-
2. **API reference docs** live in the [Elasticsearch specification](https://github.com/elastic/elasticsearch-specification)
20+
2. **API reference docs** live in the [Elasticsearch specification](https://github.com/elastic/elasticsearch-specification/blob/main/README.md#how-to-generate-the-openapi-representation)
2121
- This is where you need to update API docs published in the [new API docs system](https://www.elastic.co/docs/api/doc/elasticsearch/v8/)
2222
- 👩🏽‍💻 **Engineers** own this content.
2323
3. **Narrative, overview, and conceptual content** mostly lives in the [`docs-content`](https://github.com/elastic/docs-content/) repo.
@@ -106,4 +106,4 @@ This allows slightly more expressive testing of the snippets. Since that syntax
106106
% TEST[s/\n$/\nstartyaml\n - compare_analyzers: {index: thai_example, first: thai, second: rebuilt_thai}\nendyaml\n/]
107107
```
108108

109-
Any place you can use json you can use elements like `$body.path.to.thing` which is replaced on the fly with the contents of the thing at `path.to.thing` in the last response.
109+
Any place you can use json you can use elements like `$body.path.to.thing` which is replaced on the fly with the contents of the thing at `path.to.thing` in the last response.

0 commit comments

Comments
 (0)