small fixes

Author: commit111

docs/concepts/observability.md

@@ -8,7 +8,7 @@ sidebar_position: 600
 
 You can easily monitor and debug your Defang services at build and runtime using the Defang CLI and portal.
 
-When you deploy a service using the `defang compose up` the CLI will automatically start tailing the build and runtime logs for your service. You can also view the logs for your service in the portal, or by using the `defang tail` command.
+When you deploy a service using the `defang compose up`, the CLI will automatically start tailing the build and runtime logs for your service. You can also view the logs for your service in the portal, or by using the `defang tail` command.
 
 :::warning
 Keep in mind that the Defang Portal only displays services deployed to Defang Playground.

docs/concepts/resources.md

@@ -43,6 +43,6 @@ const service = new defang.DefangService("gpu-service", {
 ```
 
 :::info GPUs
-If you require access to GPUs, you can specify this in the `deploy.resources.reservations.devices[0].capabilities` section of your service as in the examples above. You can learn more about this in the [docker-compose documentation](https://docs.docker.com/compose/gpu-support/). This is the only supported value in the `deploy.resources.reservations.devices` section.
+If you require access to GPUs, you can specify this in the `deploy.resources.reservations.devices[0].capabilities` section of your service as in the examples above. You can learn more about this in the [Docker-Compose documentation](https://docs.docker.com/compose/gpu-support/). This is the only supported value in the `deploy.resources.reservations.devices` section.
 :::
 

docs/providers/playground.md

@@ -9,7 +9,7 @@ The Defang Playground is a free tier that allows you to experiment with Defang.
 This page highlights architectural considerations when deploying to the Playground and any differences you might encounter when deploying to the Playground versus deploying to your own cloud account.
 
 :::info
-The Playground allows only 1 deployed project at a time. Use the CLI `defang down` to tear down a project before deploying a new one.
+The Playground allows only 1 deployed project at a time. Use the CLI `defang down` command to tear down a project before deploying a new one.
 :::
 
 ## Overview
@@ -18,4 +18,4 @@ Overall, the Defang Playground is very similar to deploying to your own cloud ac
 
 ### Managed services
 
-In essence, the Playground does not support any [managed storage](../concepts/managed-storage) services, ie. `x-defang-postgres` and `x-defang-redis` are ignored when deploying to the Playground. You can however run both postgres and redis as regular container services for testing purposes.
+In essence, the Playground does not support any [managed storage](../concepts/managed-storage) services, ie. `x-defang-postgres` and `x-defang-redis` are ignored when deploying to the Playground. You can however run both Postgres and Redis as regular container services for testing purposes.