You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Docs live in **three places**:
17
17
18
18
1.**Reference content** lives in this repo. This covers low-level stuff like settings and configuration information that is tightly coupled to code.
19
19
- 👩🏽💻 **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)
21
21
- 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/)
22
22
- 👩🏽💻 **Engineers** own this content.
23
23
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
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