[DOCS] Reallocates limitations to point-of-use (#79582)

* [DOCS] Reallocates limitations to point-of-use

* KQL changes

* Removed limitations file

* Review comments

docs/discover/search.asciidoc

@@ -74,6 +74,9 @@ status codes, you could enter `status:[400 TO 499]`.
 codes and have an extension of `php` or `html`, you could enter `status:[400 TO
 499] AND (extension:php OR extension:html)`.
 
+IMPORTANT: When you use the Lucene Query Syntax in the *KQL* search bar, {kib} is unable to search on nested objects and perform aggregations across fields that contain nested objects. 
+Using `include_in_parent` or `copy_to` as a workaround can cause {kib} to fail.
+
 For more detailed information about the Lucene query syntax, see the
 {ref}/query-dsl-query-string-query.html#query-string-syntax[Query String Query]
 docs.

docs/index.asciidoc

@@ -20,8 +20,6 @@ include::user/index.asciidoc[]
 
 include::accessibility.asciidoc[]
 
-include::limitations.asciidoc[]
-
 include::migration.asciidoc[]
 
 include::CHANGELOG.asciidoc[]

docs/limitations.asciidoc

@@ -4,12 +4,6 @@
 
 Following are the known limitations in {kib}.
 
-[float]
-=== Exporting data
-
-Exporting a data table or saved search from a dashboard or visualization report
-has known limitations. The PDF report only includes the data visible on the screen.
-
 [float]
 === Nested objects
 
@@ -22,17 +16,3 @@ the query bar.
 Using `include_in_parent` or `copy_to` as a workaround is not supported and may stop functioning in future releases.
 ==============================================
 
-[float]
-=== Graph
-
-Graph has limited support for multiple indices.
-Go to <<graph-limitations, Graph limitations>> for details.
-
-[float]
-=== Other limitations
-
-These {stack} features have limitations that affect {kib}:
-
-* {ref}/watcher-limitations.html[Alerting]
-* {ml-docs}/ml-limitations.html[Machine learning]
-* {ref}/security-limitations.html[Security]

docs/management/watcher-ui/index.asciidoc

@@ -27,6 +27,8 @@ threshold watch, take a look at the different watcher actions. If you are
 creating an advanced watch, you should be familiar with the parts of a
 watch—input, schedule, condition, and actions.
 
+NOTE: There are limitations in *Watcher* that affect {kib}. For information, refer to {ref}/watcher-limitations.html[Alerting].
+
 [float]
 [[watcher-security]]
 === Watcher security

docs/user/ml/index.asciidoc

@@ -26,6 +26,8 @@ If {stack-security-features} are enabled, users must have the necessary
 privileges to use {ml-features}. Refer to 
 {ml-docs}/setup.html#setup-privileges[Set up {ml-features}].
 
+NOTE: There are limitations in {ml-features} that affect {kib}. For more information, refer to {ml-docs}/ml-limitations.html[Machine learning].
+
 --
 
 [[xpack-ml-anomalies]]

docs/user/reporting/index.asciidoc

@@ -55,6 +55,8 @@ click the share icon image:user/reporting/images/canvas-share-button.png["Canvas
 +
 A notification appears when the report is complete.
 
+NOTE: When you export a data table or saved search from a dashboard report, the PDF includes only the visible data.
+
 [float]
 [[reporting-layout-sizing]]
 == Layout and sizing

docs/user/security/index.asciidoc

@@ -10,6 +10,8 @@ auditing. For more information, see
 {ref}/secure-cluster.html[Secure a cluster] and
 <<using-kibana-with-security,Configuring Security in {kib}>>.
 
+NOTE: There are security limitations that affect {kib}. For more information, refer to {ref}/security-limitations.html[Security].
+
 [float]
 === Required permissions