Edit language in tenant scale docs

doc/tutorials/convert_personal_namespace_to_group/index.md

@@ -10,18 +10,17 @@ DETAILS:
 **Tier:** Free, Premium, Ultimate
 **Offering:** GitLab.com
 
-If you've started out on GitLab with a personal [namespace](../../user/namespace/index.md), but now find
-that you've outgrown its capabilities and its limitations hinder the collaboration on your projects,
-you might want to switch to a group namespace instead.
-A group namespace allows you to create multiple subgroups, and manage their members and permissions.
+If you've started out with a personal [namespace](../../user/namespace/index.md), but find
+that you've outgrown its capabilities, you can switch to a group namespace instead.
+With a group namespace, you can create multiple subgroups and manage their members and permissions.
 
-You don't have to start from scratch - you can create a new group
+You don't have to start from scratch. You can create a new group
 and move your existing projects to the group to get the added benefits.
 To find out how, see [Tutorial: Move your personal project to a group](../move_personal_project_to_group/index.md).
 
-But you can go one step further and convert your personal namespace into a group namespace,
-so you get to keep the existing username and URL. For example, if your username is `alex`,
-you can continue using the `https://gitlab.example.com/alex` URL for your group.
+You can also go one step further and convert your personal namespace into a group namespace.
+Converting your namespace lets you keep the existing username and URL. For example, if your
+username is `alex`, you can continue using the `https://gitlab.example.com/alex` URL for your group.
 
 This tutorial shows you how to convert your personal namespace into a group namespace
 using the following steps:
@@ -40,7 +39,7 @@ rename the `alex` namespace to `alex-user`, and `alex-group` namespace to the no
 1. On the left sidebar, at the top, select **Create new** (**{plus}**) and **New group**.
 1. In **Group name**, enter a name for the group.
 1. In **Group URL**, enter a path for the group, which is used as the namespace.
-   Don't worry about the actual path, this is only temporary. You'll change this URL to the username of the personal namespace in the [final step](#rename-the-new-group-namespace-to-the-original-username).
+   Don't worry about the actual path, this is only temporary. You change this URL to the username of the personal namespace in the [final step](#rename-the-new-group-namespace-to-the-original-username).
 1. Choose the [visibility level](../../user/public_access.md).
 1. Optional. Fill in information to personalize your experience.
 1. Select **Create group**.
@@ -48,7 +47,7 @@ rename the `alex` namespace to `alex-user`, and `alex-group` namespace to the no
 ## Transfer projects from the personal namespace to the group
 
 Next, you must transfer your projects from the personal namespace to the new group.
-You can transfer only one project at a time, so if you want to transfer multiple projects,
+You can transfer only one project at a time. If you want to transfer multiple projects,
 you must perform the steps below for each project.
 
 Before you start the transfer process, make sure you:

doc/tutorials/move_personal_project_to_group/index.md

@@ -11,8 +11,8 @@ DETAILS:
 **Offering:** GitLab.com
 
 If you created a project under a [personal namespace](../../user/namespace/index.md),
-you can perform common tasks, like managing issue and merge requests,
-and using source control and CI/CD.
+you can perform common tasks, like managing issues, merge requests,
+source control, and CI/CD.
 
 However, at some point you might outgrow your personal project and
 want to move your project to a group namespace instead. With a group namespace, you can:

doc/user/get_started/get_started_projects.md

@@ -6,15 +6,19 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Get started organizing work with projects
 
-In GitLab, the data related to a specific development effort goes in a project.
-The project serves as a central hub for collaboration, version control, and project management.
+Projects in GitLab organize all the data for a specific development project.
+A project is where you work with your team, store your files, and manage your tasks.
 
-Projects provide the environment for managing and collaborating
-on software development projects, from planning and coding to testing and deployment.
+Use projects to:
+
+- Write and save code
+- Track issues and tasks
+- Collaborate on code changes
+- Test and deploy your app
 
 Project creation and maintenance is part of a larger workflow:
 
-![Workflow](img/get_started_projects_v16_11.png)
+![Organize work with projects is part of the plan stage in a development workflow.](img/get_started_projects_v16_11.png)
 
 ## Step 1: Create a project
 
@@ -24,13 +28,13 @@ documentation, and related resources.
 A project contains a repository. A repository contains all the files,
 directories, and data related to your work.
 
-Set the appropriate visibility level (public, internal, or private) for your project,
-based on your project's security and collaboration requirements.
-Configure project settings, like merge request approvals, issue tracking,
-and CI/CD pipelines, to align with your development workflow.
+When you create the project, review and configure the following settings to align with your development workflow and collaboration requirements:
 
-Use description templates to maintain consistency and provide essential information
-when creating issues, merge requests, or other project entities.
+- Visibility level
+- Merge request approvals
+- Issue tracking
+- CI/CD pipelines
+- Description templates for entities like issues or merge requests
 
 For more information, see:
 
@@ -42,15 +46,11 @@ For more information, see:
 
 ## Step 2: Secure and control access to projects
 
-To grant specific access rights to automated tools or external systems,
-helping ensure secure integration with your GitLab projects, generate project access tokens.
-
-If you want to securely deploy your project to external systems,
-create deploy keys. These keys can grant read-only access to your repositories.
+Use the following tools to manage secure access to your projects:
 
-And finally, to provide temporary and limited access to
-your project's repository and registry, create deploy tokens, which
-help enable secure deployments and automation.
+- Project access tokens: Grant specific access rights to automated tools or external systems for secure integration.
+- Deploy keys: Grant read-only access to your repositories to securely deploy your project to external systems.
+- Deploy tokens: Grant temporary, limited access to your project's repository and registry for secure deployments and automation.
 
 For more information, see:
 
@@ -63,33 +63,29 @@ For more information, see:
 You can invite multiple projects to a group, sometimes called
 `sharing a project with a group`. Each project has its own repository,
 issues, merge requests, and other features.
-When you have multiple projects in the same group, your team members can collaborate
-on specific projects while still maintaining
-a high-level overview of all the work being done in the group.
 
-To further refine who has access to which projects, you can
-add subgroups to your group.
+With multiple projects in a group, team members can collaborate on individual
+projects while having a high-level view of all the work done in the group.
+
+To further refine access to your projects, you can add subgroups to
+your group.
 
 For more information, see:
 
 - [Share projects](../project/members/sharing_projects_groups.md)
+- [Subgroups](../group/subgroups/index.md)
 
 ## Step 4: Enhance project discoverability and recognition
 
-To create a consistent and easily recognizable naming scheme for your projects,
-use reserved project and group names. Consistent names can help make projects
-more discoverable.
-
-Use the search functionality to quickly find specific projects,
+Use the search box to quickly find specific projects,
 issues, merge requests, or code snippets across your GitLab instance.
 
-Another way to make your projects more discoverable is to add badges
-to your project's `README` file. Badges can display important information,
-like build status, test coverage, or version number. They provide a
-quick overview of your project's health and status.
+To make projects easier to find:
 
-And finally, topics are labels that you can assign to projects
-to help you organize and find them. You can assign a topic to several projects.
+- Create a consistent and recognizable naming scheme for your projects with reserved project and group names.
+- Add badges to your project's `README` file. Badges can display important information,
+like build status, project health, test coverage, or version number.
+- Assign project topics. Topics are labels that help you organize and find projects.
 
 For more information, see:
 
@@ -100,9 +96,14 @@ For more information, see:
 
 ## Step 5: Boost development efficiency and maintain code quality
 
-Use the code intelligence features, like code navigation,
-hover information, and auto-completion, to enhance your productivity and
-maintain a high-quality codebase. Code intelligence is a range of tools
+Use code intelligence features to enhance your productivity and
+maintain a high-quality codebase, such as:
+
+- Code navigation
+- Hover information
+- Auto-completion
+
+Code intelligence is a range of tools
 that help you efficiently explore, analyze, and maintain your codebase.
 
 To quickly locate and go to specific files in your project,
@@ -115,14 +116,14 @@ For more information, see:
 
 ## Step 6: Migrate projects into GitLab
 
-When necessary, use file exports to migrate projects to GitLab.
-You can migrate from other version control systems or GitLab instances.
-When you migrate a frequently accessed repository to GitLab, you can continue to
-access it by its original name by using a project alias.
+Use file exports to migrate projects to GitLab from other systems or GitLab instances.
+
+When you migrate a frequently accessed repository to GitLab, you can use a project alias to
+continue to access it by its original name.
 
-On GitLab.com, you can transfer a project from one namespace to another,
-which is essentially moving it so that another group or team can have
-access or ownership.
+On GitLab.com, you can transfer a project from one namespace to another.
+A transfer essentially moves a project to another group
+so its members have access or ownership.
 
 For more information, see:
 

doc/user/group/subgroups/index.md

@@ -70,9 +70,7 @@ To view the subgroups of a group:
 ### Private subgroups in public parent groups
 
 In the hierarchy list, public groups with private subgroups have an expand option (**{chevron-down}**),
-which indicates the group has nested subgroups. The expand option (**{chevron-down}**) is visible
-to all users, but the private group is displayed only to users who are direct or inherited members
-of the private subgroup.
+which indicates the group has nested subgroups. All users can view the expand option (**{chevron-down}**), but only direct or inherited members of the private subgroup can view the private group.
 
 If you prefer to keep information about the presence of nested subgroups private,
 you should add private subgroups only to private parent groups.

doc/user/group/troubleshooting.md

@@ -89,16 +89,16 @@ Administrators can find a user's maximum permissions for a group or project.
 
 ## Unable to remove billable members with badge `Project Invite/Group Invite`
 
-```plaintext
-Members who were invited via a group invitation cannot be removed. You can either remove the entire group, or ask an Owner of the invited group to remove the member.
-```
+The following error typically occurs when the user belongs to an external group that has been shared with your [projects](../project/members/sharing_projects_groups.md) or [groups](../project/members/sharing_projects_groups.md#invite-a-group-to-a-group):
+
+`Members who were invited via a group invitation cannot be removed. You can either remove the entire group, or ask an Owner of the invited group to remove the member.`
 
-This error typically occurs when the user you're trying to remove is part of an external group that has been [shared with one or more of your projects](../project/members/sharing_projects_groups.md) or [groups](../project/members/sharing_projects_groups.md#invite-a-group-to-a-group). To remove the user as a billable member, follow one of the options:
+To remove the user as a billable member, follow one of these options:
 
 - Remove the invited group membership from your project or group members page.
 - Recommended. Remove the user directly from the invited group, if you have access to the group.
 
-The feature request to **Update `billable_members` endpoint to include invited group** is currently being worked on. For more information, see [issue 386583](https://gitlab.com/gitlab-org/gitlab/-/issues/386583)
+The feature request to **Update `billable_members` endpoint to include invited group** is being worked on. For more information, see [issue 386583](https://gitlab.com/gitlab-org/gitlab/-/issues/386583).
 
 ## Missing or insufficient permission, delete button disabled
 

doc/user/profile/achievements.md

@@ -19,7 +19,8 @@ an administrator can [enable the feature flag](../../administration/feature_flag
 This feature is not ready for production use.
 
 Achievements are a way to reward users for their activity on GitLab.
-As a namespace maintainer or owner, you can create custom achievements for specific contributions, which you can award to or revoke from users based on your criteria.
+As a namespace maintainer or owner, you can create custom achievements for specific contributions. You can award these
+achievements to users or revoke them based on defined criteria.
 
 As a user, you can collect achievements to highlight your contributions to different projects or groups on your profile.
 An achievement consists of a name, a description, and an avatar.

doc/user/project/organize_work_with_projects.md

@@ -7,10 +7,13 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Organize work with projects
 
-In GitLab, you can create projects to host
-your codebase. You can also use projects to track issues, plan work,
-collaborate on code, and continuously build, test, and use
-built-in CI/CD to deploy your app.
+Create projects to host your codebase in GitLab.
+You can also use projects to:
+
+- Track issues
+- Plan work
+- Collaborate on code
+- Use CI/CD tools to continuously build, test, and deploy your app
 
 Projects can be available [publicly, internally, or privately](../public_access.md).
 GitLab does not limit the number of private projects you can create.