capitalize Compose file

Author: commit111

docs/concepts/deployments.md

@@ -6,7 +6,7 @@ sidebar_position: 500
 
 # Deployment
 
-When you deploy using Defang, whether it's with `defang compose up` with a [compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry. 
+When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry. 
 
 ## Deploying Updates
 

docs/concepts/managed-storage/managed-postgres.md

@@ -85,7 +85,7 @@ The AWS Console can be used to restore a snapshop into a new instance of postgre
 <!-- 
 ### Major Version Updating of Engine
 
-To update the database engine you can simply update the image to a later version in your compose file and apply it via ```defang compose up --provider=aws```. In the example below, we change from Postgres 15 to 16.
+To update the database engine you can simply update the image to a later version in your Compose file and apply it via ```defang compose up --provider=aws```. In the example below, we change from Postgres 15 to 16.
 
 Please note the upgrading will occur immediately and may result in the database being unavailable for some time.
 

docs/concepts/projects.md

@@ -6,11 +6,11 @@ sidebar_position: 200
 
 # Projects
 
-A _project_ refers to a cohesive collection of services which are defined and managed using a `compose.yaml` file.
+A _project_ refers to a cohesive collection of services which are defined and managed using a [`compose.yaml` file](./compose.md).
 
 ## Project Names
 
-The _project name_ can be defined in the compose file with [the `name` property](https://docs.docker.com/compose/compose-file/04-version-and-name/#name-top-level-element), otherwise the base name of the project directory will be used.
+The _project name_ can be defined in the Compose file with the [`name` property](https://docs.docker.com/compose/compose-file/04-version-and-name/#name-top-level-element), otherwise the base name of the project directory will be used.
 
 The project name may then be used when performing project-wide operations such as listing services, tailing logs, or deprovisioning. For example:
 ```

docs/concepts/services.md

@@ -6,17 +6,17 @@ sidebar_position: 200
 
 # Services
 
-Defang allows you deploy services defined as containers. You can define your services using a [compose file](./compose.md) or a [Pulumi program](./pulumi.md). Services can be exposed to the internet or kept private, and can communicate between themselves using the following conventions for hostnames:
+Defang allows you deploy services defined as containers. You can define your services using a [Compose file](./compose.md) or a [Pulumi program](./pulumi.md). Services can be exposed to the internet or kept private, and can communicate between themselves using the following conventions for hostnames:
 
 `<username>-<service-name>`
 
 You can learn more about accounts and usernames in the [accounts page](./accounts.md).
 
 :::tip Service Names
-Service names are defined in your compose file or your Pulumi program.
+Service names are defined in your Compose file or your Pulumi program.
 :::
 
-You can learn more about about how to define [services with compose files here](./compose.md) and [services with Pulumi here](./pulumi.md). You can learn more about how services are deployed in the [deployment page](./deployments.md).
+You can learn more about about how to define [services with Compose files here](./compose.md) and [services with Pulumi here](./pulumi.md). You can learn more about how services are deployed in the [deployment page](./deployments.md).
 
 :::info
 While this is the current state of the Defang model, we plan to add support for other types of services in the future, including serverless functions.

docs/tutorials/updating-your-services.md

@@ -10,7 +10,7 @@ To update your app (for example, updating the base image of your container, or m
 
 ## Deploying New Services or Removing Existing Services
 
-If you are using [compose files](../concepts/compose.md) to define your services, you can add/remove services, make changes to code, etc. When you run `defang compose up`, the update will be diffed against the current state and any necessary changes will be applied to make the current state match the desired state.
+If you are using [Compose files](../concepts/compose.md) to define your services, you can add/remove services, make changes to code, etc. When you run `defang compose up`, the update will be diffed against the current state and any necessary changes will be applied to make the current state match the desired state.
 
 ## Deployment Modes