Removed references to planning future features

Related to: https://docs.gitlab.com/ee/development/documentation/styleguide/index.html\#promising-features-in-future-versions

doc/administration/monitoring/prometheus/index.md

@@ -294,8 +294,8 @@ To use an external Prometheus server:
 You can visit `http://localhost:9090` for the dashboard that Prometheus offers by default.
 
 If SSL has been enabled on your GitLab instance, you may not be able to access
-Prometheus on the same browser as GitLab if using the same FQDN due to [HSTS](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security). We plan to
-[provide access via GitLab](https://gitlab.com/gitlab-org/multi-user-prometheus), but in the interim there are
+Prometheus on the same browser as GitLab if using the same FQDN due to [HSTS](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security).
+[A test project exists](https://gitlab.com/gitlab-org/multi-user-prometheus) to provide access via GitLab, but in the interim there are
 some workarounds: using a separate FQDN, using server IP, using a separate browser for Prometheus, resetting HSTS, or
 having [NGINX proxy it](https://docs.gitlab.com/omnibus/settings/nginx.html#inserting-custom-nginx-settings-into-the-gitlab-server-block).
 

doc/user/analytics/index.md

@@ -27,9 +27,9 @@ When we describe GitLab analytics, we use the following terms:
       [production environment](../../ci/environments/index.md#deployment-tier-of-environments) for
       all MRs deployed in the given time period. This measure under-estimates lead time because
       merge time is always later than commit time. The
-      [standard definition](https://github.com/GoogleCloudPlatform/fourkeys/blob/main/METRICS.md#lead-time-for-changes) uses median commit time. We plan to start
-      [measuring from "issue first commit"](https://gitlab.com/gitlab-org/gitlab/-/issues/328459)
-      as a better proxy, although still imperfect.
+      [standard definition](https://github.com/GoogleCloudPlatform/fourkeys/blob/main/METRICS.md#lead-time-for-changes) uses median commit time.
+      [An issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/328459) to start
+      measuring from "issue first commit" as a better proxy, although still imperfect.
 
   - **Stability**
     - **Change Failure Rate:** The percentage of deployments causing a failure in production.

doc/user/clusters/integrations.md

@@ -22,8 +22,8 @@ Although, the [Cluster management project template](management_project_template.
 requires that you manually do the last steps of these sections,
 [Enable Prometheus integration for your cluster](#enable-prometheus-integration-for-your-cluster)
 or [Enable Elastic Stack integration for your cluster](#enable-elastic-stack-integration-for-your-cluster)
-depending on which application you are installing. We plan to also automate this step in the future,
-see the [opened issue](https://gitlab.com/gitlab-org/gitlab/-/issues/326565).
+depending on which application you are installing. [An issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/326565)
+to automate this step.
 
 ## Prometheus cluster integration
 

doc/user/profile/preferences.md

@@ -54,9 +54,10 @@ See the epic for:
 If you find an issue that isn't listed, please leave a comment on the epic or create a
 new issue.
 
-Dark mode is available as a navigation theme, for MVC and compatibility reasons. In
-the future, we plan to make it configurable in its own section along with support for
-[different navigation themes](https://gitlab.com/gitlab-org/gitlab/-/issues/219512).
+Dark mode is available as a navigation theme, for MVC and compatibility reasons.
+[An issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/219512)
+to make it configurable in its own section along with support for
+different navigation themes.
 
 Dark theme only works with the **Dark** syntax highlighting theme.