Add latest changes from gitlab-org/gitlab@master

4 files changed, 66 insertions, 43 deletions

diff --git a/doc/user/group/reporting/git_abuse_rate_limit.md b/doc/user/group/reporting/git_abuse_rate_limit.md
index 1b14edb04d9..d32524b8f5f 100644
--- a/doc/user/group/reporting/git_abuse_rate_limit.md
+++ b/doc/user/group/reporting/git_abuse_rate_limit.md
@@ -13,7 +13,7 @@ On self-managed GitLab, by default this feature is not available. To make it ava
 
 This is the group-level documentation. For self-managed instances, see the [administration documentation](../../admin_area/reporting/git_abuse_rate_limit.md).
 
-Git abuse rate limiting is a feature to automatically ban users who download, clone, pull, fetch, or fork more than a specified number of repositories of a group in a given time frame. Banned users cannot access the top-level group or any of its non-public subgroups via HTTP or SSH. The rate limit also applies to users who authenticate with a [personal](../../../user/profile/personal_access_tokens.md) or [group access token](../../../user/group/settings/group_access_tokens.md). Access to unrelated groups is unaffected.
+Git abuse rate limiting is a feature to automatically ban users who download, clone, pull, fetch, or fork more than a specified number of repositories of a group in a given time frame. Banned users cannot access the top-level group or any of its non-public subgroups via HTTP or SSH. The rate limit also applies to users who authenticate with [personal](../../../user/profile/personal_access_tokens.md) or [group access tokens](../../../user/group/settings/group_access_tokens.md), as well as [CI/CD job tokens](../../../ci/jobs/ci_job_token.md). Access to unrelated groups is unaffected.
 
 Git abuse rate limiting does not apply to top-level group owners, [deploy tokens](../../../user/project/deploy_tokens/index.md), or [deploy keys](../../../user/project/deploy_keys/index.md).
 
diff --git a/doc/user/packages/composer_repository/index.md b/doc/user/packages/composer_repository/index.md
index d8662ef6512..6eac299e71f 100644
--- a/doc/user/packages/composer_repository/index.md
+++ b/doc/user/packages/composer_repository/index.md
@@ -225,7 +225,7 @@ To install a package:
    Using a CI/CD job token:
 
    ```shell
-   composer config gitlab-token.<DOMAIN-NAME> gitlab-ci-token ${CI_JOB_TOKEN}
+   composer config -- gitlab-token.<DOMAIN-NAME> gitlab-ci-token "${CI_JOB_TOKEN}"
    ```
 
    Result in the `auth.json` file:
diff --git a/doc/user/product_analytics/instrumentation/browser_sdk.md b/doc/user/product_analytics/instrumentation/browser_sdk.md
index 1cc74d037b6..912e157f67c 100644
--- a/doc/user/product_analytics/instrumentation/browser_sdk.md
+++ b/doc/user/product_analytics/instrumentation/browser_sdk.md
@@ -8,23 +8,29 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 This SDK is for instrumenting web sites and applications to send data for the GitLab [product analytics functionality](../index.md).
 
-## How to use the Browser-SDK
+## How to use the Browser SDK
 
 ### Using the NPM package
 
 Add the NPM package to your package JSON using your preferred package manager:
 
+::Tabs
+
+:::TabTitle yarn
+
 ```shell
 yarn add @gitlab/application-sdk-browser
 ```
 
-OR
+:::TabTitle npm
 
 ```shell
 npm i @gitlab/application-sdk-browser
 ```
 
-Then for browser usage you can import the client SDK:
+::EndTabs
+
+Then, for browser usage import the client SDK:
 
 ```javascript
 import { glClientSDK } from '@gitlab/application-sdk-browser';
@@ -52,9 +58,9 @@ You can use a specific version of the SDK like this:
 <script src="https://unpkg.com/@gitlab/application-sdk-browser@0.2.5/dist/gl-sdk.min.js"></script>
 ```
 
-## Browser-SDK initialization options
+## Browser SDK initialization options
 
-Apart from `appId` and `host`, the options below allow you to configure the Browser SDK.
+Apart from `appId` and `host`, you can configure the Browser SDK with the following options:
 
 ```typescript
 interface GitLabClientSDKOptions {
@@ -73,32 +79,48 @@ interface GitLabClientSDKOptions {
 }
 ```
 
-| Option                        | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| :---------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `appId`                       | This is the ID given by the GitLab Project Analytics setup guide. This is used to make sure your data is sent to your analytics instance.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `host`                        | This is the GitLab Project Analytics instance that is given by the setup guide.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `hasCookieConsent`            | To use cookies to identify unique users and record their full IP address. This is set to `false` by default. When `false`, users will be considered anonymous users. No cookies or other storage mechanisms will be used to identify users.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `respectGlobalPrivacyControl` | To respect the user's [GPC](https://globalprivacycontrol.org/) configuration to permit or refuse tracking. This is set to `true` by default. When `false`, events will be emitted regardless of user configuration.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `trackerId`                   | The `trackerId` is used to differentiate between multiple trackers running on the same page or application, as each tracker instance can be configured differently to capture different sets of data. This identifier helps ensure that the data sent to the collector is correctly associated with the correct tracker configuration. `Default trackerId value is set as gitlab`.                                                                                                                                                                                                                                                                                        |
-| `pagePingTracking`            | Page ping is a feature that allows you to `track user engagement on your website or application by sending periodic events while a user is actively browsing a page.` Page pings provide valuable insight into how users interact with your content, such as how long they spend on a page, which sections they are viewing, and if they are scrolling or not. `pagePingTracking` can be boolean or an object. If true it enables page ping with default options. if false, it will not enable page ping tracking. it can also be an object containing two options : `minimumVisitLength` - The minimum time that must have elapsed before first heartbeat. `heartbeatDelay` - The interval at which the callback is fired. |
-| `plugins`                     | Specify which plugins to enable or disable. By default all plugins are enabled.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Option                        | Description |
+| :---------------------------- | :---------- |
+| `appId`                       | The ID provided by the GitLab Project Analytics setup guide. This ID ensures your data is sent to your analytics instance. |
+| `host`                        | The GitLab Project Analytics instance provided by the setup guide. |
+| `hasCookieConsent`            | Whether to use cookies to identify unique users and record their full IP address. Set to `false` by default. When `false`, users are considered anonymous users. No cookies or other storage mechanisms are used to identify users. |
+| `respectGlobalPrivacyControl` | Whether to respect the user's [GPC](https://globalprivacycontrol.org/) configuration to permit or refuse tracking. Set to `true` by default. When `false`, events are emitted regardless of user configuration. |
+| `trackerId`                   | Used to differentiate between multiple trackers running on the same page or application, because each tracker instance can be configured differently to capture different sets of data. This identifier helps ensure that the data sent to the collector is correctly associated with the correct tracker configuration. Default value is `gitlab`. |
+| `pagePingTracking`            | Option to track user engagement on your website or application by sending periodic events while a user is actively browsing a page. Page pings provide valuable insight into how users interact with your content, such as how long they spend on a page, which sections they are viewing, and whether they are scrolling. `pagePingTracking` can be boolean or an object. As a boolean, set to `true` it enables page ping with default options, and set to `false` it disables page ping tracking. As an object, it has two options: `minimumVisitLength` (the minimum time that must have elapsed before the first heartbeat) and `heartbeatDelay` (the interval at which the callback is fired). |
+| `plugins`                     | Specify which plugins to enable or disable. By default all plugins are enabled. |
 
 ### Plugins
 
-- `Client Hints`: It is an alternative the tracking the User Agent, which is particularly useful in those browsers which are freezing the User Agent string.
+- `Client Hints`: An alternative to tracking the User Agent, which is particularly useful in browsers that are freezing the User Agent string.
 Enabling this plugin will automatically capture the following context:
 
-| Context                                                                                                                                                      | Example                                                                                                                  |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
-| [iglu:org.ietf/http_client_hints/jsonschema/1-0-0](https://github.com/snowplow/iglu-central/blob/master/schemas/org.ietf/http_client_hints/jsonschema/1-0-0) | `{"isMobile" : false, "brands" : [{"brand" : "Google Chrome", version : "89"}, {"brand" : "Chromium", version : "89"}]}` |
+  For example,
+  [iglu:org.ietf/http_client_hints/jsonschema/1-0-0](https://github.com/snowplow/iglu-central/blob/master/schemas/org.ietf/http_client_hints/jsonschema/1-0-0)
+  has the following configuration:
+
+  ```json
+  {
+     "isMobile":false,
+     "brands":[
+        {
+           "brand":"Google Chrome",
+           "version":"89"
+        },
+        {
+           "brand":"Chromium",
+           "version":"89"
+        }
+     ]
+  }
+  ```
 
-- `Link Click Tracking`: With this plugin, the tracker will add click event listeners to all link elements. Link clicks are tracked as self-describing events. Each link-click event captures the link’s href attribute. The event also has fields for the link’s ID, classes, and target (where the linked document is opened, such as a new tab or new window).
+- `Link Click Tracking`: With this plugin, the tracker adds click event listeners to all link elements. Link clicks are tracked as self-describing events. Each link-click event captures the link's `href` attribute. The event also has fields for the link's ID, classes, and target (where the linked document is opened, such as a new tab or new window).
 
-- `Performance Timing`: It collects performance-related data from a user's browser using the `Navigation Timing API`. This API provides detailed information about the various stages of loading a web page, such as domain lookup, connection time, content download, and rendering times. This plugin helps to gather insights into how well website performs for users, identify potential performance bottlenecks, and improve the overall user experience.
+- `Performance Timing`: It collects performance-related data from a user's browser using the `Navigation Timing API`. This API provides detailed information about the various stages of loading a web page, such as domain lookup, connection time, content download, and rendering times. This plugin helps to gather insights into how well a website performs for users, identify potential performance bottlenecks, and improve the overall user experience.
 
-- `Error Tracking`: It helps to capture and track errors that occur on website or application. By monitoring these errors, one can gain insights into potential issues with code or third-party libraries, which can help to improve the overall user experience and maintain the quality of website or application.
+- `Error Tracking`: It helps to capture and track errors that occur on a website or application. By monitoring these errors, you can gain insights into potential issues with code or third-party libraries, which can help to improve the overall user experience, and maintain the quality of the website or application.
 
-`By default all the plugins are enabled`. These plugins can be enabled or disabled through the `plugins` object:
+By default all plugins are enabled. You can disable or enable these plugins through the `plugins` object:
 
 ```typescript
 const tracker = glClientSDK({
@@ -124,7 +146,7 @@ glClient.identify(userId, userAttributes);
 
 | Property         | Type                        | Description                                                                   |
 | :--------------- | :-------------------------- | :---------------------------------------------------------------------------- |
-| `userId`         | `String`                    | The user identifier your application users to identify individual users.      |
+| `userId`         | `String`                    | The user identifier your application uses to identify individual users. |
 | `userAttributes` | `Object`/`Null`/`undefined` | The user attributes that need to be added to the session and tracking events. |
 
 ### `page`
@@ -152,9 +174,9 @@ glClient.track(eventName, eventAttributes);
 | `eventName`       | `String`                    | The name of the custom event.                                    |
 | `eventAttributes` | `Object`/`Null`/`undefined` | The event attributes that need to be added to the tracked event. |
 
-### refreshLinkClickTracking
+### `refreshLinkClickTracking`
 
-enableLinkClickTracking only tracks clicks on links which exist when the page has loaded. If new links can be added to the page after then which you wish to track, just use refreshLinkClickTracking.
+`enableLinkClickTracking` tracks only clicks on links that exist when the page has loaded. To track new links added to the page after it has been loaded, use `refreshLinkClickTracking`.
 
 ```javascript
 glClient.refreshLinkClickTracking();
@@ -163,9 +185,9 @@ glClient.refreshLinkClickTracking();
 ### `trackError`
 
 NOTE:
-While `trackError` is supported on the Browser SDK the resulting events are currently not yet used or available anywhere.
+`trackError` is supported on the Browser SDK, but the resulting events are not used or available.
 
-Used to capture errors. This works only when the `errorTracking` plugin is enabled. As mentioned in [Plugins](#plugins) section, By default it is enabled.
+Used to capture errors. This works only when the `errorTracking` plugin is enabled. The [plugin](#plugins) is enabled by default.
 
 ```javascript
 glClient.trackError(eventAttributes);
@@ -190,17 +212,17 @@ try {
 
 | Property          | Type     | Description                                                                                                          |
 | :---------------- | :------- | :------------------------------------------------------------------------------------------------------------------- |
-| `eventAttributes` | `Object` | The event attributes that need to be added to the tracked event. `messeage` is a mandatory key in `eventAttributes`. |
+| `eventAttributes` | `Object` | The event attributes that need to be added to the tracked event. `message` is a mandatory key in `eventAttributes`. |
 
 ### `addCookieConsent`
 
-`addCookieConsent` is used to allow tracking of user identifiers via cookies. By default `hasCookieConsent` is false and no user identifiers are passed. To enable tracking of user identifiers call the `addCookieConsent` method. This is not needed if you intialised the Browser SDK with `hasCookieConsent` set to true.
+`addCookieConsent` is used to allow tracking of user identifiers via cookies. By default `hasCookieConsent` is false, and no user identifiers are passed. To enable tracking of user identifiers, call the `addCookieConsent` method. This step is not needed if you intialized the Browser SDK with `hasCookieConsent` set to true.
 
 ```javascript
 glClient.addCookieConsent();
 ```
 
-### setCustomUrl
+### `setCustomUrl`
 
 Used to set a custom URL for tracking.
 
@@ -212,7 +234,7 @@ glClient.setCustomUrl(url);
 | :------- | :------- | :------------------------------------------------ |
 | `url`    | `String` | The custom URL that you want to set for tracking. |
 
-### setReferrerUrl
+### `setReferrerUrl`
 
 Used to set a referrer URL for tracking.
 
@@ -224,9 +246,9 @@ glClient.setReferrerUrl(url);
 | :------- | :------- | :-------------------------------------------------- |
 | `url`    | `String` | The referrer URL that you want to set for tracking. |
 
-### setDocumentTitle
+### `setDocumentTitle`
 
-Used to override document title.
+Used to override the document title.
 
 ```javascript
 glClient.setDocumentTitle(title);
@@ -234,18 +256,18 @@ glClient.setDocumentTitle(title);
 
 | Property | Type     | Description                        |
 | :------- | :------- | :--------------------------------- |
-| `title`  | `String` | The document title you want to set |
+| `title`  | `String` | The document title you want to set. |
 
 ## Contribute
 
-Want to contribute to Browser-SDK? follow [contributing guide](https://gitlab.com/gitlab-org/analytics-section/product-analytics/gl-application-sdk-js/-/blob/main/docs/Contributing.md).
+If you would like to contribute to Browser SDK, follow the [contributing guide](https://gitlab.com/gitlab-org/analytics-section/product-analytics/gl-application-sdk-js/-/blob/main/docs/Contributing.md).
 
 ## Troubleshooting
 
-If the Browser SDK is not sending events or is behaving in an unexpected way, take the following actions:
+If the Browser SDK is not sending events, or behaving in an unexpected way, take the following actions:
 
-- Verify that the appId and host values in the options object are correct.
-- Check if any browser privacy settings, extensions, or ad blockers are interfering with the Browser SDK.
+1. Verify that the `appId` and host values in the options object are correct.
+1. Check if any browser privacy settings, extensions, or ad blockers are interfering with the Browser SDK.
 
-For more information and assistance, consult the [Snowplow documentation](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/browser-tracker/browser-tracker-v3-reference/)
-or contact the [Analytics Instrumentation](https://about.gitlab.com/handbook/engineering/development/analytics/analytics-instrumentation/#team-members) team.
+For more information and assistance, see the [Snowplow documentation](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/browser-tracker/browser-tracker-v3-reference/)
+or contact the [Analytics Instrumentation team](https://about.gitlab.com/handbook/engineering/development/analytics/analytics-instrumentation/#team-members).
diff --git a/doc/user/project/issues/issue_weight.md b/doc/user/project/issues/issue_weight.md
index b1a1390d3d2..ddd08ee1de0 100644
--- a/doc/user/project/issues/issue_weight.md
+++ b/doc/user/project/issues/issue_weight.md
@@ -10,7 +10,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 When you have a lot of issues, it can be hard to get an overview.
 With weighted issues, you can get a better idea of how much time,
-value, or complexity a given issue has or costs.
+value, or complexity a given issue has or costs. You can also [sort by weight](sorting_issue_lists.md#sorting-by-weight)
+to see which issues need to be prioritized.
 
 ## View the issue weight