Updated consistently the docs

Author: andsel

docs/static/monitoring/monitoring-internal-legacy.asciidoc

@@ -7,7 +7,7 @@
 
 deprecated[7.9.0]
 
-NOTE: Starting from version 9.0, legacy monitoring is deactivated and behind a feature flag. Set `allow.legacy.monitoring` to `true` to allow access to the feature.
+NOTE: Starting from version 9.0, legacy monitoring is deactivated and behind a feature flag. Set `xpack.monitoring.allow_legacy_collection` to `true` to allow access to the feature.
 
 ==== Components for legacy collection
 
@@ -59,7 +59,7 @@ monitoring cluster will show the Logstash metrics under the _monitoring_ cluster
 
 --
 
-. Verify that the `xpack.monitoring.collection.enabled` setting is `true` on the
+. Verify that the `xpack.monitoring.allow_legacy_collection` and `xpack.monitoring.collection.enabled` settings are `true` on the
 production cluster. If that setting is `false`, the collection of monitoring data
 is disabled in {es} and data is ignored from all other sources.
 

docs/static/settings-file.asciidoc

@@ -365,8 +365,4 @@ separating each log lines per pipeline could be helpful in case you need to trou
 | Determine where to allocate memory buffers, for plugins that leverage them.
 Currently defaults to `direct` but can be switched to `heap` to select Java heap space, which will become the default in the future.
 | `direct` Check out <<reducing-off-heap-usage>> for more info.
-
-| `allow.legacy.monitoring`
-| Set to `true` to allow <<monitoring-internal-collection-legacy,internal legacy monitoring>>.
-| `false`
 |=======================================================================