doc/user/project/merge_requests/conflicts.md

@@ -67,7 +67,7 @@ For example, these changes don't create a conflict:
 1. Branch `one` renames `example.txt` to `example1.txt`
 1. Branch `two` renames `example.txt` to `example_old.txt`.
 
-When these branches merge, both `example1.txt` and `example_old` are present.
+When these branches merge, both `example1.txt` and `example_old.txt` are present.
 
 ## Methods of resolving conflicts
 

doc/user/project/merge_requests/creating_merge_requests.md

@@ -141,7 +141,7 @@ You can create a merge request by running Git commands on your local machine.
    ```
 
    To reduce the number of fields to edit later in the merge request, use
-   [push options](../../../gitlab-basics/add-file.md#push-options-for-merge-requests) to set the value of fields.
+   [push options](../../../topics/git/commit.md#push-options-for-merge-requests) to set the value of fields.
 
 1. In the response to the `git push`, GitLab provides a direct link to create the merge request:
 

doc/user/project/merge_requests/drafts.md

@@ -78,6 +78,8 @@ Draft merge requests run the same pipelines as merge requests marked as ready.
 In GitLab 15.0 and earlier, you must [mark the merge request as ready](#mark-merge-requests-as-ready)
 if you want to run [merged results pipelines](../../../ci/pipelines/merged_results_pipelines.md).
 
+To skip a pipeline for a draft merge request, see [Skip pipelines for draft merge requests](../../../ci/yaml/workflow.md#skip-pipelines-for-draft-merge-requests).
+
 <!-- ## Troubleshooting
 
 Include any troubleshooting steps that you can foresee. If you know beforehand what issues

doc/user/project/merge_requests/duo_in_merge_requests.md

@@ -21,6 +21,7 @@ DETAILS:
 **Status:** Beta
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/10401) in GitLab 16.2 as an [experiment](../../../policy/experiment-beta-support.md#experiment).
+> - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/429882) to beta in GitLab 16.10.
 
 Use GitLab Duo Merge request summary to create a merge request description when you
 create or edit a merge request.
@@ -64,7 +65,7 @@ Provide feedback on this experimental feature in [issue 408991](https://gitlab.c
 ## Generate a merge commit message
 
 DETAILS:
-**Tier:** Ultimate with [GitLab Duo Enterprise](../../../subscriptions/subscription-add-ons.md)
+**Tier:** Ultimate for a limited time. In the future, Ultimate with [GitLab Duo Enterprise](../../../subscriptions/subscription-add-ons.md).
 **Offering:** GitLab.com, Self-managed, GitLab Dedicated
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/10453) in GitLab 16.2 as an [experiment](../../../policy/experiment-beta-support.md#experiment) [with a flag](../../../administration/feature_flags.md) named `generate_commit_message_flag`. Disabled by default.

doc/user/project/merge_requests/reviews/index.md

@@ -14,7 +14,7 @@ DETAILS:
 Merge requests are the primary method of making changes to files in a
 GitLab project. [Create and submit](../creating_merge_requests.md) a merge request
 to propose changes. Your team leaves [comments](../../../discussions/index.md) on
-your merge request, and makes [Code Suggestions](suggestions.md) you can accept
+your merge request, and makes [suggestions](suggestions.md) you can accept
 from the user interface. When a teammate reviews your work, they can choose
 to accept or reject it.
 
@@ -177,6 +177,8 @@ When this happens, the merge request reports area shows the message
 **The change requests must be completed or resolved.** To unblock the merge request,
 the reviewer who requested changes should [re-review and approve](#re-request-a-review) the merge request.
 
+### Bypass a request for changes
+
 If the user who requested changes is unable to re-review or provide an approval,
 another user with permission to merge the merge request can override this check in the
 merge request reports area by selecting **Bypass**:
@@ -187,7 +189,14 @@ merge request reports area by selecting **Bypass**:
 1. On the merge request **Overview**, scroll to the merge request reports area.
 1. Next to **The change requests must be completed or resolved**, select **Bypass**:
 
-   ![A merge request that has been blocked by a user requesting changes](img/bypass_17_2.png)
+   ![A merge request that is blocked because a user requested changes](img/bypass_17_2.png)
+
+1. The merge reports area shows `Merge with caution: Override added`. To see which check
+   was bypassed, select **Expand merge checks** (**{chevron-lg-down}**) and find the
+   check that contains a warning (**{status_warning}**) icon. In this example, the
+   author bypassed **The change requests must be completed or resolved**:
+
+   ![This merge request contains a bypassed check, and should be merged with caution.](img/status_warning_v17_4.png)
 
 ### See how reviewers map to approval rules
 

doc/user/project/organize_work_with_projects.md

@@ -17,10 +17,10 @@ GitLab does not limit the number of private projects you can create.
 
 | | | |
 |--|--|--|
-| [**Getting started**](../../user/get_started/get_started_projects.md) **{chevron-right}** | [**Create a project**](index.md) **{chevron-right}** | [**Manage projects**](working_with_projects.md) **{chevron-right}** |
-| [**Project visibility**](../public_access.md) **{chevron-right}** | [**Project settings**](working_with_projects.md) **{chevron-right}** | [**Description templates**](../../user/project/description_templates.md) **{chevron-right}** |
-| [**Project access tokens**](../project/settings/project_access_tokens.md) **{chevron-right}** | [**Deploy keys**](../../user/project/deploy_keys/index.md) **{chevron-right}** | [**Deploy tokens**](../../user/project/deploy_tokens/index.md) **{chevron-right}** |
-| [**Share projects**](../project/members/share_project_with_groups.md) **{chevron-right}** | [**Reserved project and group names**](../../user/reserved_names.md) **{chevron-right}** | [**Search**](../../user/search/index.md) **{chevron-right}** |
-| [**Badges**](../../user/project/badges.md) **{chevron-right}** | [**Project topics**](../../user/project/project_topics.md) **{chevron-right}** | [**Code intelligence**](../../user/project/code_intelligence.md) **{chevron-right}** |
-| [**Import and migrate**](../../user/project/import/index.md) **{chevron-right}** | [**System notes**](../../user/project/system_notes.md) **{chevron-right}** | [**Transfer a project to another namespace**](../../user/project/import/index.md) **{chevron-right}** |
-| [**Use a project as a Go package**](../../user/project/use_project_as_go_package.md) **{chevron-right}** | [**Tutorial: Build a protected workflow for your project**](../../tutorials/protected_workflow/index.md) **{chevron-right}** | [**Troubleshooting**](../../user/project/troubleshooting.md) **{chevron-right}** |
+| [**Getting started**](../../user/get_started/get_started_projects.md) **{chevron-right}**<br><br>Overview of how features fit together. | [**Create a project**](index.md) **{chevron-right}**<br><br>New project, project templates. | [**Manage projects**](working_with_projects.md) **{chevron-right}**<br><br>Settings, configuration, project activity, project deletion.  |
+| [**Project visibility**](../public_access.md) **{chevron-right}****<br><br>Public, private, internal. | [**Project settings**](working_with_projects.md) **{chevron-right}**<br><br>Project features, analytics, project permissions. | [**Description templates**](../../user/project/description_templates.md) **{chevron-right}**<br><br>Issue templates, merge request templates, instance and group templates. |
+| [**Project access tokens**](../project/settings/project_access_tokens.md) **{chevron-right}**<br><br>Authentication, create, revoke, token expiration. | [**Deploy keys**](../../user/project/deploy_keys/index.md) **{chevron-right}**<br><br>Public SSH keys, repository access, bot users, read-only access.  | [**Deploy tokens**](../../user/project/deploy_tokens/index.md) **{chevron-right}**<br><br>Repository cloning, token creation, container registry. |
+| [**Share projects**](../project/members/share_project_with_groups.md)**{chevron-right}**<br><br>Member roles, invitations, group access. | [**Reserved project and group names**](../../user/reserved_names.md) **{chevron-right}**<br><br>Naming conventions, restrictions, reserved names. | [**Search**](../../user/search/index.md) **{chevron-right}**<br><br>Basic, advanced, exact, search scope, commit SHA search. |
+| [**Badges**](../../user/project/badges.md) **{chevron-right}**<br><br>Pipeline status, group, project, custom badges. | [**Project topics**](../../user/project/project_topics.md) **{chevron-right}**<br><br>Project organization, subscribe, view.  | [**Code intelligence**](../../user/project/code_intelligence.md) **{chevron-right}**<br><br>Type signatures, symbol documentation, go-to definition. |
+| [**Import and migrate**](../../user/project/import/index.md) **{chevron-right}**<br><br>Repository migration, third-party repositories, user contribution mapping. | [**System notes**](../../user/project/system_notes.md) **{chevron-right}**<br><br>Event history, activity log, comments history. | [**Transfer a project to another namespace**](../../user/project/import/index.md) **{chevron-right}**<br><br>Namespace transfer, subscription transfer. |
+| [**Use a project as a Go package**](../../user/project/use_project_as_go_package.md) **{chevron-right}**<br><br>Go modules, import calls. | [**Tutorial: Build a protected workflow for your project**](../../tutorials/protected_workflow/index.md) **{chevron-right}**<br><br>Security, approval rules, branch protection. | [**Troubleshooting**](../../user/project/troubleshooting.md) **{chevron-right}**<br><br>Problem solving, common issues, debugging, error resolution. |

doc/user/project/protected_branches.md

@@ -49,7 +49,7 @@ When a branch is protected, the default behavior enforces these restrictions on
    for that branch at the project level are ignored. All other protections continue
    to use project level settings.
 
-You can implement a [merge request approval policy](../application_security/policies/scan-result-policies.md#approval_settings)
+You can implement a [merge request approval policy](../application_security/policies/merge_request_approval_policies.md#approval_settings)
 to prevent protected branches being unprotected or deleted.
 
 ### When a branch matches multiple rules

doc/user/project/push_options.md

 ---
-redirect_to: '../../gitlab-basics/add-file.md'
+redirect_to: '../../topics/git/commit.md'
 remove_date: '2024-09-26'
 ---
 
-This document was moved to [another location](../../gitlab-basics/add-file.md).
+This document was moved to [another location](../../topics/git/commit.md).
 
 <!-- This redirect file can be deleted after <2024-09-26>. -->
 <!-- Redirects that point to other docs in the same project expire in three months. -->

doc/user/project/repository/code_explain.md

 ---
 stage: Create
-group: Code Review
+group: Code Creation
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Explain code in a file
 
 DETAILS:
-**Tier:** For a limited time, Premium and Ultimate. In the future, [GitLab Duo Pro or Enterprise](../../../subscriptions/subscription-add-ons.md).
-**Offering:** GitLab.com
-**Status:** Experiment
+**Tier: GitLab.com and Self-managed:** Premium or Ultimate for a limited time. In the future, Premium with GitLab Duo Pro or Ultimate with [GitLab Duo Pro or Enterprise](../../../subscriptions/subscription-add-ons.md). **GitLab Dedicated:** GitLab Duo Pro or Enterprise.
+**Offering:** GitLab.com, Self-managed, GitLab Dedicated
 
 > - Introduced in GitLab 15.11 as an [experiment](../../../policy/experiment-beta-support.md#experiment) on GitLab.com.
+> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/429915) in GitLab 16.8.
 
 If you spend a lot of time trying to understand code that others have created, or
 you struggle to understand code written in a language you are not familiar with,
@@ -42,4 +42,4 @@ We cannot guarantee that the large language model produces results that are corr
 You can also explain code in:
 
 - A [merge request](../../../user/project/merge_requests/changes.md#explain-code-in-a-merge-request).
-- The [IDE](../../../user/gitlab_duo_chat/examples.md#explain-code-in-the-ide).
+- The [IDE](../../../user/gitlab_duo_chat/examples.md#explain-selected-code).

doc/user/project/repository/code_suggestions/data.md

----
-redirect_to: '../../../ai_data_usage.md'
-remove_date: '2024-08-08'
----
-
-This document was moved to [another location](../../../ai_data_usage.md).
-
-<!-- This redirect file can be deleted after <2024-08-08>. -->
-<!-- Redirects that point to other docs in the same project expire in three months. -->
-<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
-<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->

doc/user/project/repository/code_suggestions/index.md

@@ -62,12 +62,15 @@ Prerequisites:
   [assigned you a seat](../../../../subscriptions/subscription-add-ons.md#assign-gitlab-duo-pro-seats).
 - For self-managed GitLab, you must have GitLab 16.8 or later, and have
   [configured proxy settings](../../../../subscriptions/subscription-add-ons.md#configure-network-and-proxy-settings).
-
 To use Code Suggestions:
 
+1. Open your Git project in a supported IDE.
+1. Add the project as a remote of your local repository using
+   [`git remote add`](../../../../gitlab-basics/start-using-git.md#git-remote-add).
+1. Add your project directory, including the hidden `.git/` folder, to your IDE workspace or project.
 1. Author your code.
-   As you type, suggestions are displayed. Code Suggestions provide code snippets
-   or complete the current line, depending on the cursor position.
+   As you type, suggestions are displayed. Code Suggestions provides code snippets
+   or completes the current line, depending on the cursor position.
 
 1. Describe the requirements in natural language.
    Code Suggestions generates functions and code snippets based on the context provided.
@@ -104,9 +107,11 @@ you might write something like:
 AI is non-deterministic, so you may not get the same suggestion every time with the same input.
 To generate quality code, write clear, descriptive, specific tasks.
 
+### Best practice examples
+
 For use cases and best practices, follow the [GitLab Duo examples documentation](../../../gitlab_duo_examples.md).
 
-## Open tabs as context
+#### Use open tabs as context
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/464767) in GitLab 17.2 [with a flag](../../../../administration/feature_flags.md) named `advanced_context_resolver`. Disabled by default.
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/462750) in GitLab 17.2 [with a flag](../../../../administration/feature_flags.md) named `code_suggestions_context`. Disabled by default.
@@ -118,54 +123,30 @@ FLAG:
 The availability of this feature is controlled by a feature flag.
 For more information, see the history.
 
-To get more accurate and relevant results from Code Suggestions and Code Generation, you can use
-the contents of the files open in tabs in your IDE. Similar to prompt engineering, these files
+For better results from GitLab Duo Code Suggestions, ensure that Open Tabs Context is enabled in your IDE settings.
+This feature uses the contents of the files currently open in your IDE to get more
+accurate and relevant results from Code Suggestions. Like prompt engineering, these files
 give GitLab Duo more information about the standards and practices in your code project.
 
-### Enable open tabs as context
+To get the most benefit from using your open tabs as context, open the files relevant to the code
+you want to create, including configuration files. When you start work in a new file,
+Code Suggestions offers you suggestions in the new file.
 
 Prerequisites:
 
-- GitLab Duo Code Suggestions must be enabled for your project.
-- For GitLab self-managed instances, the `code_suggestions_context`and the
-  `advanced_context_resolver` [feature flags](../../../feature_flags.md) must be enabled.
-- Use a supported code language:
-  - Code Completion: All configured languages.
-  - Code Generation: Go, Java, JavaScript, Kotlin, Python, Ruby, Rust, TypeScript (`.ts` and `.tsx` files),
-    Vue, and YAML.
-
-::Tabs
-
-:::TabTitle Visual Studio Code
-
-1. Install the [GitLab Workflow extension version 4.14.2 or later](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow)
-   from the Visual Studio Marketplace.
-1. Configure the [extension settings](https://gitlab.com/gitlab-org/gitlab-vscode-extension#extension-settings).
-1. Enable the feature by turning on the `gitlab.aiAssistedCodeSuggestions.enabledSupportedLanguages` setting.
-
-:::TabTitle JetBrains IDEs
-
-For installation instructions for JetBrains IDEs, see the
-[GitLab JetBrains Plugin documentation](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin#toggle-sending-open-tabs-as-context).
-
-::EndTabs
+- Requires GitLab 17.2 and later. Earlier GitLab versions that support Code Suggestions
+  cannot weight the content of open tabs more heavily than other files in your project.
+- Requires a [supported code language](#advanced-context-supported-languages).
 
-### Use open tabs as context
+1. Open the files you want to provide for context. Advanced Context uses the most recently
+   opened or changed files for context. If you don’t want a file sent as additional context, close it.
+1. To fine-tune your Code Generation results, add code comments to your file that explain
+   what you want to build. Code Generation treats your code comments like chat. Your code comments
+   update the `user_instruction`, and then improve the next results you receive.
 
-Open the files you want to provide for context:
-
-- Open tabs uses the most recently opened or changed files.
-- If you do not want a file used as additional context, close that file.
-
-When you start working in a file, GitLab Duo uses your open files
-as extra context, within [truncation limits](#truncation-of-file-content).
-
-You can adjust your Code Generation results by adding code comments to your file
-that explain what you want to build. Code Generation treats your code comments
-like chat. Your code comments update the `user_instruction`, and then improve
-the next results you receive.
-
-### Related topics
+As you work, GitLab Duo provides code suggestions that use your other open files
+(within [truncation limits](#truncation-of-file-content))
+as extra context.
 
 To learn about the code that builds the prompt, see these files:
 
@@ -173,11 +154,19 @@ To learn about the code that builds the prompt, see these files:
   [`ee/lib/api/code_suggestions.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/api/code_suggestions.rb#L76)
   in the `gitlab` repository.
 - **Code Completion**:
-  [`ai_gateway/code_suggestions/processing/completions.py`](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/blob/fcb3f485a8f047a86a8166aad81f93b6d82106a7/ai_gateway/code_suggestions/processing/completions.py#L273) in the `modelops` repository.
+  [`ai_gateway/code_suggestions/processing/completions.py`](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/blob/fcb3f485a8f047a86a8166aad81f93b6d82106a7/ai_gateway/code_suggestions/processing/completions.py#L273)
+  in the `modelops` repository.
 
-You can provide feedback about this feature in
+We'd love your feedback about the Advanced Context feature in
 [issue 258](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/issues/258).
 
+### Advanced Context supported languages
+
+The Advanced Context feature supports these languages:
+
+- Code Completion: all configured languages.
+- Code Generation: Go, Java, JavaScript, Kotlin, Python, Ruby, Rust, TypeScript (`.ts` and `.tsx` files), Vue, and YAML.
+
 ## Response time
 
 Code Suggestions is powered by a generative AI model.

doc/user/project/repository/code_suggestions/repository_xray.md

@@ -15,7 +15,7 @@ DETAILS:
 
 Repository X-Ray enhances [GitLab Duo Code Suggestions](index.md) by providing additional context to improve the accuracy and relevance of code recommendations.
 
-Repository X-Ray gives the code assistant more insight into the project's codebase and dependencies to generate better code suggestions. It does this by analyzing key project configuration files such as `Gemfile.lock`, `package.json`, and `go.mod` to build additional context.
+Repository X-Ray gives the code assistant more insight into the project's codebase and dependencies to generate better suggestions. It does this by analyzing key project configuration files such as `Gemfile.lock`, `package.json`, and `go.mod` to build additional context.
 
 By understanding the frameworks, libraries and other dependencies in use, Repository X-Ray helps the code assistant tailor suggestions to match the coding patterns, styles and technologies used in the project. This results in code recommendations that integrate more seamlessly and follow best practices for that stack.
 
@@ -66,7 +66,7 @@ xray:
 - The `$OUTPUT_DIR` environment variable defines the:
   - Output directory for reports.
   - Path that artifacts are uploaded from.
-- The added rules restrict the job to the default branch only. Restricting the job this way ensures development changes do not impact the baseline X-Ray data used for production code suggestions.
+- The added rules restrict the job to the default branch only. Restricting the job this way ensures development changes do not impact the baseline X-Ray data used for production Code Suggestions.
 
 After the initial x-ray job completes and uploads the repository analysis reports, no further action is required. Repository X-Ray automatically enriches all code generation requests from that point forward.
 

doc/user/project/repository/code_suggestions/supported_extensions.md

@@ -2,7 +2,7 @@
 stage: Create
 group: Code Creation
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
-description: "Code suggestions supports multiple editors and languages."
+description: "Code Suggestions supports multiple editors and languages."
 ---
 
 # Supported extensions and languages
@@ -11,12 +11,12 @@ DETAILS:
 **Tier:** Premium with GitLab Duo Pro or Ultimate with [GitLab Duo Pro or Enterprise](../../../../subscriptions/subscription-add-ons.md)
 **Offering:** GitLab.com, Self-managed, GitLab Dedicated
 
-Code suggestions are available in the following editor extensions and
+Code Suggestions is available in the following editor extensions and
 for the following languages.
 
 ## Supported editor extensions
 
-To use code suggestions, use one of these editor extensions:
+To use Code Suggestions, use one of these editor extensions:
 
 | IDE                                                                        | Extension                                                                                                                   |
 |----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
@@ -26,17 +26,17 @@ To use code suggestions, use one of these editor extensions:
 | JetBrains IDEs                                                             | [GitLab Duo Plugin for JetBrains](https://plugins.jetbrains.com/plugin/22325-gitlab-duo)                                    |
 | Neovim                                                                     | [`gitlab.vim` plugin](https://gitlab.com/gitlab-org/editor-extensions/gitlab.vim)                                           |
 
-A [GitLab Language Server](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp) is used in VS Code, Visual Studio, and Neovim. The Language Server supports faster iteration across more platforms. You can also configure it to support code suggestions in IDEs where GitLab doesn't provide official support.
+A [GitLab Language Server](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp) is used in VS Code, Visual Studio, and Neovim. The Language Server supports faster iteration across more platforms. You can also configure it to support Code Suggestions in IDEs where GitLab doesn't provide official support.
 
 You can express interest in other IDE extension support [in this issue](https://gitlab.com/gitlab-org/editor-extensions/meta/-/issues/78).
 
 ## Supported languages
 
-Code suggestions are aware of common popular programming languages, concepts, and
+Code Suggestions is aware of common popular programming languages, concepts, and
 infrastructure-as-code interfaces, like Kubernetes Resource Model (KRM),
 Google Cloud CLI, and Terraform.
 
-Code suggestions support these languages:
+Code Suggestions supports these languages:
 
 | Language                     | Web IDE                    | VS Code                                                                                    | JetBrains IDEs         | Visual Studio 2022 for Windows | Neovim                                                                                                |
 |-------------------------------|----------------------------|---------------------------------------------------------------------------------------------|-----------------------|--------------------------------|--------------------------------------------------------------------------------------------------------|
@@ -69,13 +69,13 @@ Some languages are not supported in all JetBrains IDEs, or might require additio
 plugin support. Refer to the JetBrains documentation for specifics on your IDE.
 
 Locally, you can add [more languages](#add-support-for-more-languages). For languages not listed in the table,
-code suggestions might not function as expected.
+Code Suggestions might not function as expected.
 
-## Manage languages for code suggestions
+## Manage languages for Code Suggestions
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/CHANGELOG.md#4210-2024-07-16) in GitLab Workflow for VS Code 4.21.0
 
-You can customize your coding experience in VS Code by enabling or disabling code suggestions for specific supported languages.
+You can customize your coding experience in VS Code by enabling or disabling Code Suggestions for specific supported languages.
 You can do this by editing your `settings.json` file directly, or from the VS Code user interface:
 
 1. In VS Code, open the extension settings for **GitLab Workflow**:
@@ -84,37 +84,117 @@ You can do this by editing your `settings.json` file directly, or from the VS Co
    1. Select **Extension Settings**.
 1. In your **User** settings, find the section titled **AI Assisted Code Suggestions: Enabled Supported Languages**.
 1. You will see a list of all supported languages with checkboxes next to each language.
-1. To enable code suggestions for a language, ensure its checkbox is checked.
-1. To disable code suggestions for a language, uncheck its checkbox.
+1. To enable Code Suggestions for a language, ensure its checkbox is checked.
+1. To disable Code Suggestions for a language, uncheck its checkbox.
 1. Your changes are automatically saved and will take effect immediately.
 
-When you disable code suggestions for a language, the Duo icon changes to show that suggestions are disabled
+When you disable Code Suggestions for a language, the Duo icon changes to show that suggestions are disabled
 for this language. On hover, it shows **Code Suggestions are disabled for this language**.
 
 ### Add support for more languages
 
-If your desired language doesn't have code suggestions available by default,
+If your desired language doesn't have Code Suggestions available by default,
 you can add support for your language locally.
 
+::Tabs
+
+:::TabTitle Visual Studio Code
+
 Prerequisites:
 
 - You have installed and enabled the
   [GitLab Workflow extension for VS Code](../../../../editor_extensions/visual_studio_code/index.md).
-- You have completed the [extension setup](https://gitlab.com/gitlab-org/gitlab-vscode-extension/#setup)
-  instructions, and authorized the extension to access your GitLab account.
+- You have completed the [VS Code extension setup](https://gitlab.com/gitlab-org/gitlab-vscode-extension/#setup)
+    instructions, and authorized the extension to access your GitLab account.
 
 To do this:
 
 1. Find your desired language in the list of
-   [language identifiers](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem)
-   for VS Code. You need the **Identifier** for a later step.
+   [language identifiers](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem).
+   You need the **Identifier** for your languages in a later step.
 1. In VS Code, open the extension settings for **GitLab Workflow**:
    1. On the top bar, go to **Code > Settings > Extensions**.
    1. Search for **GitLab Workflow** in the list, and select **Manage** (**{settings}**).
    1. Select **Extension Settings**.
    1. In your **User** settings, find
       **GitLab › Ai Assisted Code Suggestions: Additional Languages** and select **Add Item**.
-1. In **Item**, add the language identifier, and select **OK**.
+1. In **Item**, add the identifier for each language you want to support. Identifiers should be
+   lowercase, like `html` or `powershell`. Don't add leading periods from file suffixes to each identifier.
+1. Select **OK**.
+
+:::TabTitle JetBrains IDEs
+
+Prerequisites:
+
+- You have installed and enabled the
+  [GitLab plugin for JetBrains IDEs](../../../../editor_extensions/jetbrains_ide/index.md).
+- You have completed the [Jetbrains extension setup](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin#setup)
+    instructions, and authorized the extension to access your GitLab account.
+
+To do this:
+
+1. Find your desired language in the list of
+   [language identifiers](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem).
+   You need the **Identifier** for your languages in a later step.
+1. In your IDE, on the top bar, select your IDE name, then select **Settings**.
+1. On the left sidebar, select **Tools > GitLab Duo**.
+1. Under **Code Suggestions Enabled Languages > Additional languages**, add the identifier for each language
+   you want to support. Identifiers should be in lower case, like `html`. Separate multiple identifiers with commas,
+   like `html,powershell,latex`, and don't add leading periods to each identifier.
+1. Select **OK**.
+
+::EndTabs
+
+## Use open tabs as context
+
+> - [Introduced](https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/issues/206) in GitLab 17.2.
+
+To enhance the accuracy and relevance of GitLab Duo Code Suggestions, enable the use of
+open tabs as context in your IDE settings. This feature uses the contents of files most recently
+opened or changed in your IDE to provide more tailored code suggestions, within certain truncation limits.
+This extra context gives you:
+
+- More accurate and relevant code suggestions
+- Better alignment with your project's standards and practices
+- Improved context for new file creation
+
+Open tabs as context supports these languages:
+
+- Code Completion: All configured languages.
+- Code Generation: Go, Java, JavaScript, Kotlin, Python, Ruby, Rust, TypeScript (`.ts` and `.tsx` files),
+  Vue, and YAML.
+
+## Enable open tabs as context
+
+Prerequisites:
+
+- Requires GitLab 17.1 or later.
+- For GitLab self-managed instances, enable the `code_suggestions_context`and the
+  `advanced_context_resolver` [feature flags](../../../feature_flags.md).
+- GitLab Duo Code Suggestions enabled for your project
+- For Visual Studio Code, requires the GitLab Workflow extension, version 4.14.2 or later.
+
+::Tabs
+
+:::TabTitle Visual Studio Code
+
+1. Install the [GitLab Workflow extension](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow)
+   from the Visual Studio Marketplace.
+1. Configure the extension following the
+   [setup instructions](https://gitlab.com/gitlab-org/gitlab-vscode-extension#extension-settings).
+1. Enable the feature by toggling the `gitlab.aiAssistedCodeSuggestions.enabledSupportedLanguages` setting.
+
+:::TabTitle JetBrains IDEs
+
+For installation instructions for JetBrains IDEs, see the
+[GitLab JetBrains Plugin documentation](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin#toggle-sending-open-tabs-as-context).
+
+::EndTabs
+
+When you're ready to start coding:
+
+1. Open relevant files, including configuration files, to provide better context.
+1. Close any files you don't want to be used as context.
 
 ## View multiple code suggestions
 

doc/user/project/repository/code_suggestions/troubleshooting.md

@@ -26,18 +26,18 @@ You can verify that Code Suggestions is set up correctly on the server. Because
 
 A flash message with Code Suggestions check status is displayed at the top of the page.
 
-## Code Suggestions are not displayed
+## Suggestions are not displayed
 
-If Code Suggestions are not displayed, follow these steps:
+If suggestions are not displayed, follow these steps:
 
 1. Ensure you have [installed a supported IDE extension](supported_extensions.md#supported-editor-extensions)
 1. Ensure your administrator has [assigned you a seat](../../../../subscriptions/subscription-add-ons.md#assign-gitlab-duo-pro-seats).
 
-If Code Suggestions are still not displayed, try the following troubleshooting steps.
+If suggestions are still not displayed, try the following troubleshooting steps.
 
-### Code Suggestions not displayed in VS Code or GitLab Web IDE
+### Suggestions not displayed in VS Code or GitLab Web IDE
 
-If you are a self-managed user, ensure that Code Suggestions for the [GitLab Web IDE](../../../project/web_ide/index.md) are enabled. The same settings apply to VS Code as local IDE.
+If you are a self-managed user, ensure that Code Suggestions for the [GitLab Web IDE](../../../project/web_ide/index.md) is enabled. The same settings apply to VS Code as local IDE.
 
 1. On the left sidebar, select **Extensions > GitLab Workflow**.
 1. Select **Settings** (**{settings}**), and then select **Extension Settings**.
@@ -46,7 +46,7 @@ If you are a self-managed user, ensure that Code Suggestions for the [GitLab Web
 
 ### View Code Suggestions logs
 
-If the settings are enabled, but Code Suggestions are still not displayed, try the following steps:
+If the settings are enabled, but suggestions are still not displayed, try the following steps:
 
 1. In the GitLab Workflow **Extension Settings**, enable **GitLab: Debug**.
 1. Open the extension log in **View > Output** and change the dropdown list to **GitLab Workflow** as the log filter. The command palette command is `GitLab: Show Extension Logs`.
@@ -61,7 +61,7 @@ If the settings are enabled, but Code Suggestions are still not displayed, try t
 
 To enable debug logging for the Language Server (LS), enable **GitLab › Ls: Debug**.
 
-### Code Suggestions not displayed in JetBrains IDEs
+### Suggestions not displayed in JetBrains IDEs
 
 1. Ensure you have properly [set up the extension](https://gitlab.com/gitlab-org/editor-extensions/gitlab-intellij-plugin#setup).
 1. From the **Tools > GitLab Duo** menu, select **Verify setup**. Make sure the health check passes.
@@ -69,7 +69,7 @@ To enable debug logging for the Language Server (LS), enable **GitLab › Ls: De
    working on. Go to **Settings** > **Languages & Frameworks** to see the full list of
    languages and frameworks supported by your JetBrains IDE.
 
-### Code Suggestions not displayed in Microsoft Visual Studio
+### Suggestions not displayed in Microsoft Visual Studio
 
 1. Ensure you have properly [set up the extension](https://gitlab.com/gitlab-org/editor-extensions/gitlab-visual-studio-extension#setup).
 1. From the **Tools > Options** menu, find the **GitLab** option. Ensure **Log Level** is set to **Debug**.
@@ -82,12 +82,12 @@ To enable debug logging for the Language Server (LS), enable **GitLab › Ls: De
 14:48:21:346 LS(55096): time="2023-07-17T14:48:21-05:00" level=info msg="update context"
 ```
 
-## Code Suggestions return a 401 error
+## Code Suggestions returns a 401 error
 
-Code Suggestions [depend on a license token](../../../ai_features.md) that
+Code Suggestions [depends on a license token](../../../ai_features.md) that
 [synchronizes your subscription](../../../../administration/license.md) with GitLab.
 
-If the token expires, GitLab Duo code suggestions returns the following error
+If the token expires, GitLab Duo Code Suggestions returns the following error
 with status `401` when the token has expired:
 
 ```plaintext

doc/user/project/repository/files/jupyter_notebooks/index.md

@@ -39,7 +39,7 @@ When commits include changes to Jupyter Notebook files, GitLab:
 - Enables switching between raw and rendered diffs on the Commit and Compare pages. (Not available on merge request pages.)
 - Renders images on the diffs.
 
-Code Suggestions are not available on diffs and merge requests for `.ipynb` files.
+Code Suggestions is not available on diffs and merge requests for `.ipynb` files.
 
 Cleaner notebook diffs are not generated when the notebook is too large.
 

doc/user/project/repository/monorepos/index.md

@@ -240,7 +240,25 @@ performance problems.
 You can use [`git-sizer`](https://github.com/github/git-sizer) to get a snapshot
 of repository characteristics and discover problem aspects of your monorepo.
 
-For example:
+To get a _full_ clone of your repository, you need a full Git mirror or bare clone to
+ensure all Git references are present. To profile your repository:
+
+1. [Install `git-sizer`](https://github.com/github/git-sizer?tab=readme-ov-file#getting-started).
+1. Get a full clone of your repository:
+
+   ```shell
+   git clone --mirror <git_repo_url>
+   ```
+    
+   After cloning, the repository will be in the bare Git format that is compatible with `git-sizer`.
+1. Run `git-sizer` with all statistics in the directory of your Git repository:
+
+   ```shell
+   git-sizer -v
+   ```
+
+After processing, the output of `git-sizer` should look like the following with a level of concern
+on each aspect of the repository:
 
 ```shell
 Processing blobs: 1652370