Add latest changes from gitlab-org/gitlab@master

4 files changed, 22 insertions, 8 deletions

diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index 89134cf1705..943d4137185 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -51,7 +51,7 @@ To explore all public groups you are a member of:
 
 1. On the left sidebar, select **Search or go to**.
 1. Select **View all my groups**.
-1. At the top right, select **Explore groups**.
+1. In the upper right, select **Explore groups**.
 
 To view groups where you have direct or indirect membership:
 
@@ -129,7 +129,7 @@ When you leave a group:
 To leave a group:
 
 1. On the left sidebar, select **Search or go to** and find your group.
-1. On the group overview page, in the top right, select **Actions** (**{ellipsis_v})**.
+1. On the group overview page, in the upper-right corner, select **Actions** (**{ellipsis_v})**.
 1. Select **Leave group**, then **Leave group** again.
 
 ## Remove a group
@@ -196,7 +196,7 @@ As a user, you can request to be a member of a group, if an administrator allows
 
 1. On the left sidebar, select **Search or go to**.
 1. Select **View all my groups**.
-1. At the top right side, select **Explore groups**.
+1. In the upper right, select **Explore groups**.
 1. In the **Search by name** text box, enter the name of the group you want to join.
 1. In the search results, select the name of the group.
 1. On the group page, under the group name, select **Request Access**.
@@ -379,5 +379,5 @@ You might need the group ID if you want to interact with it using the [GitLab AP
 To copy the group ID:
 
 1. On the left sidebar, select **Search or go to** and find your group.
-1. On the group overview page, in the top right, select **Actions** (**{ellipsis_v})**.
+1. On the group overview page, in the upper-right corner, select **Actions** (**{ellipsis_v})**.
 1. Select **Copy group ID**.
diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md
index d765e6946e0..0fdd572ed7c 100644
--- a/doc/user/group/value_stream_analytics/index.md
+++ b/doc/user/group/value_stream_analytics/index.md
@@ -207,9 +207,10 @@ You can change the name of a project environment in your GitLab CI/CD configurat
 > - Filtering [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13216) in GitLab 13.3
 > - Horizontal stage path [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/12196) in 13.0 and [feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/323982) in 13.12
 > - Predefined date ranges dropdown list [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/408656/) in GitLab 16.5 [with a flag](../../../administration/feature_flags.md) named `vsa_predefined_date_ranges`. Disabled by default.
+> - Predefined date ranges dropdown list [enabled on self-managed and GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/433149) in GitLab 16.7.
 
 FLAG:
-On self-managed GitLab, by default the predefined date ranges dropdown list feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `vsa_predefined_date_ranges`. On GitLab.com, this feature is not available. The feature is not ready for production use.
+On self-managed GitLab, by default the predefined date ranges dropdown list feature is available. To hide the feature per user, an administrator can [disable the feature flag](../../../administration/feature_flags.md) named `vsa_predefined_date_ranges`. On GitLab.com, this feature is available.
 
 Prerequisites:
 
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index 47610ffd75d..744b5406707 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -246,7 +246,7 @@ go to `https://gitlab.example.com/projects/<id>`.
 To copy the project ID:
 
 1. On the left sidebar, select **Search or go to** and find your project.
-1. On the project overview page, in the top right, select **Actions** (**{ellipsis_v})**.
+1. On the project overview page, in the upper-right corner, select **Actions** (**{ellipsis_v})**.
 1. Select **Copy project ID**.
 
 For example, if in your personal namespace `alex` you have a project `my-project` with the ID `123456`, you can access the project
@@ -288,7 +288,7 @@ Prerequisites:
 To leave a project:
 
 1. On the left sidebar, select **Search or go to** and find your project.
-1. On the project overview page, in the top right, select **Actions** (**{ellipsis_v})**.
+1. On the project overview page, in the upper-right corner, select **Actions** (**{ellipsis_v})**.
 1. Select **Leave project**, then **Leave project** again..
 
 ## Add a compliance framework to a project **(PREMIUM)**
diff --git a/doc/user/workspace/gitlab_agent_configuration.md b/doc/user/workspace/gitlab_agent_configuration.md
index b7770b49d75..856b39814fa 100644
--- a/doc/user/workspace/gitlab_agent_configuration.md
+++ b/doc/user/workspace/gitlab_agent_configuration.md
@@ -96,7 +96,8 @@ remote_development:
 In this configuration:
 
 - The network policy is generated for each workspace because `enabled` is `true`.
-- The egress rules allow all traffic to the internet (`0.0.0.0/0`) except to the IP CIDR ranges `10.0.0.0/8`, `172.16.0.0/12`, and `192.168.0.0/16`.
+- The egress rules allow all traffic to the internet (`0.0.0.0/0`) except to the
+  IP CIDR ranges `10.0.0.0/8`, `172.16.0.0/12`, and `192.168.0.0/16`.
 
 The behavior of the network policy depends on the Kubernetes network plugin.
 For more information, see the [Kubernetes documentation](https://kubernetes.io/docs/concepts/services-networking/network-policies/).
@@ -139,3 +140,15 @@ In this example, traffic from the workspace is allowed if:
 
 - The destination IP is any range except `10.0.0.0/8`, `172.16.0.0/12`, or `192.168.0.0/16`.
 - The destination IP is `172.16.123.1/32`.
+
+## Configuring user access with remote development
+
+You can configure the `user_access` module to access the connected Kubernetes cluster with your GitLab credentials.
+This module is configured and runs independently of the `remote_development` module.
+
+Be careful when configuring both `user_access` and `remote_development` in the same GitLab agent.
+The `remote_development` clusters manage user credentials (such as personal access tokens) as Kubernetes Secrets.
+Any misconfiguration in `user_access` might cause this private data to be accessible over the Kubernetes API.
+
+For more information about configuring `user_access`, see
+[Configure Kubernetes access](../../user/clusters/agent/user_access.md#configure-kubernetes-access).