more vale

content/manuals/projects/_index.md

@@ -44,9 +44,9 @@
 
 ### Key features and benefits
 
  - One-click project setup: Open a local folder or clone a Git repository and run your project instantly.
  - Minimal Docker expertise required: Ideal for both beginners and experienced developers.
- - Custom `run` commands for your projects: Define and store preconfigured `run` commands that are equivalent to running `docker compose up`.
+ - Custom `run` commands for your projects: Define and store pre-configured `run` commands that are equivalent to running `docker compose up`.
  - Local and remote projects: Work on projects locally or sync artifacts to the cloud for cross-device access and easy collaboration.
 
 {{< grid >}}

content/manuals/projects/about.md

@@ -13,30 +13,30 @@ Docker Projects works as follows:
 
 1. Create or open a project. You can:
 
- - Open a local project: Select a folder on your machine that contains your project code.
- - Clone a Git repository: Provide a repository URL and clone the project into a local directory.
+   - Open a local project: Select a folder on your machine that contains your project code.
+   - Clone a Git repository: Provide a repository URL and clone the project into a local directory.
 
    Once a project is opened, Docker Desktop detects the Compose file and prepares the project for execution.
 
 2. Configure and run your project with pre-configured commands. These commands:
 
- - Work like `docker compose up`, launching services based on the Compose file.
- - Can be customized with additional flags, multiple Compose files, and environment variables.
- - Enable pre-run tasks, such as executing scripts before starting the services.
+   - Work like `docker compose up`, launching services based on the Compose file.
+   - Can be customized with additional flags, multiple Compose files, and environment variables.
+   - Enable pre-run tasks, such as executing scripts before starting the services.
 
    All of which means you can fine-tune your configurations without manually running complex CLI commands.
 
 3. Collaborate and share with teams. For projects linked to a Git repository, Docker Projects stores artifacts in the cloud, enabling easy collaboration:
 
- - Work across devices: Open a project from any machine and instantly access stored configurations.
- - Share configurations: Team members can access pre-defined run commands, reducing setup time.
+   - Work across devices: Open a project from any machine and instantly access stored configurations.
+   - Share configurations: Team members can access pre-defined run commands, reducing setup time.
 
    Collaboration is easy — new developers can join a team, open a project, and start working without complex setup steps.
 
 4. Manage and iterate. Once a project is up and running, Docker Projects makes it easy to monitor, update, and troubleshoot:
 
- - View logs to debug issues and track service activity.
- - Edit configurations and run commands as requirements change.
+   - View logs to debug issues and track service activity.
+   - Edit configurations and run commands as requirements change.
 
 ## What's next?
 

content/manuals/projects/edit.md

@@ -25,7 +25,7 @@ weight: 40
    > 
    > While the `--env-file` flag isn't currently supported, you can specify environment variables in your Compose file, or use the **Tasks** option to run a script that sets your environment variables. 
 
-   - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by deselecing the checkbox.
+   - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by deselecting the checkbox.
    - **Tasks (Advanced options)**: Optionally specify a command to run before running the project. For example, if you want to run a bash script from the project directory named `set-vars.sh`, you can specify bash `set-vars.sh`. Or, on Windows to run a script with `cmd.exe` named `set-vars.bat`, specify `set-vars.bat`. Note that a task can access environment variables from your terminal profile, but it can't access local shell functions nor aliases.
 
 4. Select **Save changes**. 

content/manuals/projects/open.md

@@ -5,7 +5,7 @@
 weight: 20
 ---
 
-> [!NOTE]
+> [!IMPORTANT]
 > 
 > In order to use Docker Projects, make sure you have enabled the **Access experimental features** setting on the **Features in development** tab. 
 
@@ -64,7 +64,7 @@
 
 1. Sign in to Docker Desktop, and go to **Projects**.
 
 2. Select **Clone a git repository**. This lets you specify a Git repository and a local folder to clone that repository to. The repository must contain at least your project’s code and a Compose file.
 
 3. Enter the remote source and choose the local destination to clone to. 
 
@@ -90,7 +90,7 @@
    > 
    > While the `--env-file` flag isn't currently supported, you can specify environment variables in your Compose file, or use the **Tasks** option to run a script that sets your environment variables. 
 
-   - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by deselecing the checkbox.
+   - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by deselecting the checkbox.
    - **Tasks (Advanced options)**: Optionally specify a command to run before running the project. For example, if you want to run a bash script from the project directory named `set-vars.sh`, you can specify bash `set-vars.sh`. Or, on Windows to run a script with `cmd.exe` named `set-vars.bat`, specify `set-vars.bat`. Note that a task can access environment variables from your terminal profile, but it can't access local shell functions nor aliases.
 
 7. Select **Save changes**.
@@ -107,7 +107,7 @@
 
 In the **Projects** view in Docker Desktop, existing remote projects display **No local copy** under the project. 
 
 You’ll see remote projects when you are new to the team and are accessing a shared project, remove a project from Docker Desktop, or access Docker Desktop from a new device after creating a project associated with a Git repository.
 
 To open an existing remote project, you can choose between:
 

content/manuals/projects/share.md

@@ -1,8 +1,8 @@
 ---
 title: Share and collaborate on a project
 linkTitle: Collaborate
-description: TBD
-keywords: TBD
+description: Learn how to collaborate on a project
+keywords: collaborate, projects, docker desktop, local, remote
 weight: 60
 ---