Fix typos in docs (#1811)

* Update ARCHITECTURE.md

* Update BACKENDS.md

* Update LOCKING.md

* Update fleets.md

* Update gateways.md

* Update server-deployment.md

* Update troubleshooting.md

docs/docs/concepts/fleets.md

@@ -239,7 +239,7 @@ To terminate and delete specific instances from a fleet, pass `-i INSTANCE_NUM`.
 
 #### Termination policy
 
-If you want a fleet to be automatically deleted after a certain idle time, you can set the
+If you want a fleet to be automatically deleted after a certain idle time,
 you can set the [`termination_idle_time`](../reference/dstack.yml/fleet.md#termination_idle_time) property.
 
 [//]: # (Add Idle time example to the reference page)
@@ -252,4 +252,4 @@ you can set the [`termination_idle_time`](../reference/dstack.yml/fleet.md#termi
 
 !!! info "Reference"
     See [.dstack.yml](../reference/dstack.yml/fleet.md) for all the options supported by
-    fleets, along with multiple examples.
+    fleets, along with multiple examples.

docs/docs/concepts/gateways.md

@@ -76,7 +76,7 @@ $ dstack delete -f examples/deployment/gateway.dstack.yml
 
 </div>
 
-[//]: # (TODO: Ellaborate on default)
+[//]: # (TODO: Elaborate on default)
 
 [//]: # (TODO: ## Accessing endpoints)
 
@@ -86,4 +86,4 @@ $ dstack delete -f examples/deployment/gateway.dstack.yml
 
 !!! info "Reference"
     See [.dstack.yml](../reference/dstack.yml/gateway.md) for all the options supported by
-    gateways, along with multiple examples.
+    gateways, along with multiple examples.

docs/docs/guides/server-deployment.md

@@ -92,7 +92,7 @@ To store the state externally, use the `DSTACK_DATABASE_URL` and `DSTACK_SERVER_
 ??? info "Migrate from SQLite to PostgreSQL"
     You can migrate the existing state from SQLite to PostgreSQL using `pgloader`:
 
-    1. Create an new PostgreSQL database
+    1. Create a new PostgreSQL database
     2. Clone the `dstack` repo and [install](https://github.com/dstackai/dstack/blob/master/contributing/DEVELOPMENT.md) `dstack` from source.
        Ensure you've checked out the tag that corresponds to your server version (e.g. `git checkout 0.18.10`).
     3. Apply database migrations to the new database:
@@ -154,7 +154,7 @@ The log group must be created beforehand, `dstack` won't try to create it.
     }
     ```
 
-## Deploying multiple replicase of the server
+## Deploying multiple replicas of the server
 
 If you'd like to deploy multiple server replicas, make sure to configure `dstack` to use [PostgreSQL](#postgresql)
-and [AWS CloudWatch](#aws-cloudwatch).
+and [AWS CloudWatch](#aws-cloudwatch).

docs/docs/guides/troubleshooting.md

@@ -13,7 +13,7 @@ Make sure to provide clear, detailed steps to reproduce the issue.
 Include server logs, CLI outputs, and configuration samples. Avoid using screenshots for logs or errors—use text instead. 
 
 To get more detailed logs, make sure to set the `DSTACK_CLI_LOG_LEVEL` and `DSTACK_SERVER_LOG_LEVEL` 
-environent variables to `debug` when running the CLI and the server, respectively.
+environment variables to `debug` when running the CLI and the server, respectively.
 
 > See these examples for well-reported issues: [this :material-arrow-top-right-thin:{ .external }](https://github.com/dstackai/dstack/issues/1640){:target="_blank"}
 and [this :material-arrow-top-right-thin:{ .external }](https://github.com/dstackai/dstack/issues/1551){:target="_blank"}.
@@ -119,4 +119,4 @@ Also, review the  `/root/.dstack/shim.log` file on each host used to create the
 
 ## Community
 
-If you have a question, please feel free to ask it in our [Discord server](https://discord.gg/u8SmfwPpMd).
+If you have a question, please feel free to ask it in our [Discord server](https://discord.gg/u8SmfwPpMd).