[8.16] [Docs] Update Known Issues (#200240) (#200263)

# Backport

This will backport the following commits from `main` to `8.16`:
- [[Docs] Update Known Issues
(#200240)](#200240)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"wajihaparvez","email":"wajiha.parvez@elastic.co"},"sourceCommit":{"committedDate":"2024-11-14T21:29:56Z","message":"[Docs]
Update Known Issues (#200240)\n\n## Summary\r\n\r\nFixed some typos and
updated sentence
structure","sha":"8ede68b7ec2c1eccc944b921a02db2d5ad9d825a","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","v8.16.0","backport:version","v8.17.0","v8.16.1"],"title":"[Docs]
Update Known
Issues","number":200240,"url":"https://github.com/elastic/kibana/pull/200240","mergeCommit":{"message":"[Docs]
Update Known Issues (#200240)\n\n## Summary\r\n\r\nFixed some typos and
updated sentence
structure","sha":"8ede68b7ec2c1eccc944b921a02db2d5ad9d825a"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200240","number":200240,"mergeCommit":{"message":"[Docs]
Update Known Issues (#200240)\n\n## Summary\r\n\r\nFixed some typos and
updated sentence
structure","sha":"8ede68b7ec2c1eccc944b921a02db2d5ad9d825a"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co>

docs/CHANGELOG.asciidoc

@@ -93,37 +93,36 @@ The 8.16.0 release includes the following known issues.
 
 [discrete]
 [[known-199902]]
-.Stack Monitoring shows "Unable to load page error"
+.Stack Monitoring shows "Unable to load page" error
 [%collapsible]
 ====
 *Details* +
-The Stack Monitoring pages Overview, Nodes, Logs can stop working with the error "Unable to load page error". The Stack trace mentions `TypeError: Cannot read properties of undefined (reading 'logsLocator')`.
+The Overview, Nodes, and Logs pages in Stack Monitoring show an "Unable to load page" error. The Stack trace mentions `TypeError: Cannot read properties of undefined (reading 'logsLocator')`.
 
 *Workaround* +
-Disabling the `Set feature visibility > Logs` feature at Kibana Space settings level will prevent the error to occur. Please note the `Logs` feature will not be available on such space.
+Disabling the `Set feature visibility > Logs` feature at the Kibana Space settings level will prevent the error from occurring. Please note the `Logs` feature will not be available on those spaces.
 
-It's also possible to `Observability > Logs` feature privilege to `None` on the role level - this will hide the `Logs` feature for individual users and prevent the error for these users as well.
+It's also possible to set the `Observability > Logs` feature privilege to `None` at the role level. This will hide the `Logs` feature from individual users and prevent the error for these users as well.
 
 For more information, refer to {kibana-issue}199902[#199902].
 ====
 
 [discrete]
 [[known-199891-199892]]
-.Onboarding, tutorial of APM and OpenTelemetry and some "Beats Only" integrations will show the error "Unable to load page error"
+.Onboarding, tutorial of APM and OpenTelemetry and some "Beats Only" integrations shows "Unable to load page" error
 [%collapsible]
 ====
 *Details* +
-Tutorials linked from the {kib} home page show an error "Unable to load page error". The Stack trace mentions `The above error occurred in tutorial_TutorialUi`.
+Tutorials linked from the {kib} home page show an "Unable to load page" error. The Stack trace mentions `The above error occurred in tutorial_TutorialUi`.
 
 *Workaround* +
-The APM / OpenTelemetry tutorials represented a shortcut to get important parameters to use in the configuration files quickly.
-It is still possible to obtain the same parameters following the documentation tutorials of APM.
+The APM / OpenTelemetry tutorials represented a shortcut to quickly add important parameters to the configuration files.
+It is still possible to obtain the same parameters following the tutorials in the APM documentation.
 
 More information can be found in the {observability-guide}/apm-collect-application-data.html[APM documentation] and the {observability-guide}/get-started-with-fleet-apm-server.html[Fleet documentation].
 
 For information about how to create APM API keys, please check the {observability-guide}/apm-api-key.html#apm-create-an-api-key[API key documentation].
 
-
 For more information, refer to {kibana-issue}199891[#199891] and {kibana-issue}199892[#199892].
 ====