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/configure/content-set/navigation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@ The TOC in principle follows the directory structure on disk.
123
123
- folder: subsection
124
124
```
125
125
126
-
If a folder does not explicitly define `children` all markdown files within that folder are included automatically
126
+
If a folder does not explicitly define `children` all Markdown files within that folder are included automatically
127
127
128
128
If a folder does define `children` all markdown files within that folder have to be included. `docs-builder` will error if it detects dangling documentation files.
Copy file name to clipboardExpand all lines: docs/syntax/frontmatter.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ If you define `products` in a page's Markdown file and the `docset.yml` file als
52
52
You can _not_ override doc set level `products` at the page level.
53
53
54
54
:::{tip}
55
-
`products` is distinct from `applies_to`, which is used to indicate feature availability and applicability.
55
+
The purpose of the `products`field is different from `applies_to`: the former provides metadata to search engines, while the latter indicates feature availability and applicability.
56
56
57
57
% Is this true?
58
58
For example, while a page might contain content that is _applicable_ to Elastic Cloud Serverless projects,
0 commit comments