Style edits and info updates

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/300312

doc/ci/review_apps/index.md

@@ -321,7 +321,3 @@ the user must enter a [personal access token](../../user/profile/personal_access
 with `api` scope before submitting feedback.
 
 This same method can be used to require authentication for any public projects.
-
-## Limitations
-
-Review App limitations are the same as [environments limitations](../environments/index.md#limitations).

doc/development/testing_guide/review_apps.md

@@ -112,7 +112,7 @@ Review Apps are automatically stopped 2 days after the last deployment thanks to
 the [Environment auto-stop](../../ci/environments/index.md#stop-an-environment-after-a-certain-time-period) feature.
 
 If you need your Review App to stay up for a longer time, you can
-[pin its environment](../../ci/environments/index.md#auto-stop-example) or retry the
+[pin its environment](../../ci/environments/index.md#override-a-deployments-scheduled-stop-time) or retry the
 `review-deploy` job to update the "latest deployed at" time.
 
 The `review-cleanup` job that automatically runs in scheduled

doc/user/project/clusters/protect/container_host_security/quick_start_guide.md

@@ -57,7 +57,7 @@ initial troubleshooting steps that resolve the most common problems:
 1. If things still aren't working, a more assertive set of actions may help get things back to a
    good state:
 
-   - Stop and [delete the problematic environment](../../../../../ci/environments/#delete-environments-through-the-ui)
+   - Stop and [delete the problematic environment](../../../../../ci/environments/#delete-a-stopped-environment)
      in GitLab.
    - Delete the relevant namespace in Kubernetes by running
      `kubectl delete namespaces <insert-some-namespace-name>` in your Kubernetes cluster.

doc/user/project/clusters/protect/container_network_security/quick_start_guide.md

@@ -131,7 +131,7 @@ initial troubleshooting steps that resolve the most common problems:
 1. If things still aren't working, a more assertive set of actions may help get things back into a
    good state:
 
-   - Stop and [delete the problematic environment](../../../../../ci/environments/index.md#delete-environments-through-the-ui) in GitLab.
+   - Stop and [delete the problematic environment](../../../../../ci/environments/index.md#delete-a-stopped-environment) in GitLab.
    - Delete the relevant namespace in Kubernetes by running `kubectl delete namespaces <insert-some-namespace-name>` in your Kubernetes cluster.
    - Rerun the application project pipeline to redeploy the application.