add service name resolution from compose to services page

Author: commit111

docs/concepts/compose.md

@@ -57,8 +57,8 @@ services:
     # add service-level properties here
 ```
 
-:::info Service Name Resolution
-Defang identifies services by the [account username](./accounts.md) and the service name (as defined in the `compose.yaml` file). This means that if you have multiple Defang projects with the same service name, they will conflict with each other. We recommend using a different name for each service you define. 
+:::info 
+Defang identifies services by the [account username](./accounts.md) and the service name (as defined in the `compose.yaml` file). This means that if you have multiple Defang projects with the same service name, they will conflict with each other. See our [Services](/docs/concepts/services) page for more.
 :::
 
 ### `version`

docs/concepts/services.md

@@ -10,14 +10,18 @@ Defang allows you deploy services defined as containers. You can define your ser
 
 `<username>-<service-name>`
 
-You can learn more about accounts and usernames in the [accounts page](./accounts.md).
+### Service Name Resolution
+As shown above, Defang identifies services by the [account username](./accounts.md) and the service name. 
 
-:::tip Service Names
+:::tip
 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).
+This means that if you have multiple Defang projects with the same service name, they will conflict with each other. To avoid naming conflicts, we recommend using a different name for each service you define. 
+
+### Service Deployment
+Defang manages the deployment process for services. 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.
+We plan to add support for other types of services in the future, including serverless functions.
 :::