Documentation + docker-compose.yml update

packages/twenty-website/src/content/developers/frontend-development/hotkeys.mdx

@@ -16,7 +16,7 @@ For example, if you have a page that listens for the Enter key, and a modal that
 
 To handle this problem, we have a custom hook that makes it possible to listen to hotkeys without any conflict.
 
-You place it in a component and it will listen to the hotkeys only when the component is mounted AND when the specified **hotkey scope** is active.
+You place it in a component, and it will listen to the hotkeys only when the component is mounted AND when the specified **hotkey scope** is active.
 
 ## How to listen for hotkeys in practice ?
 

packages/twenty-website/src/content/developers/frontend-development/work-with-figma.mdx

@@ -31,7 +31,7 @@ On the left sidebar, you can access the different pages of Twenty's Figma. This
 
 ## Useful Tips
 
-With read-only access, you can't edit the design but you can access all features that will be useful to convert the designs into code.
+With read-only access, you can't edit the design, but you can access all features that will be useful to convert the designs into code.
 
 ### Use the Dev mode
 

packages/twenty-website/src/content/developers/self-hosting/docker-compose.mdx

@@ -83,7 +83,7 @@ curl -O https://raw.githubusercontent.com/twentyhq/twenty/refs/tags/v0.35.0/pack
 
 Start the Docker containers:
 ```bash
-docker-compose up -d
+docker compose up -d
 ```
 
 ### Step 4: Access the Application
@@ -158,8 +158,8 @@ We strongly recommend setting up Twenty behind a reverse proxy with SSL terminat
 
     For changes to take effect, restart the Docker containers:
     ```bash
-        docker-compose down
-        docker-compose up -d
+        docker compose down
+        docker compose up -d
     ```
 
 #### Considerations

packages/twenty-website/src/content/developers/self-hosting/troubleshooting.mdx

@@ -94,8 +94,8 @@ If you can't log in after setup:
     ```
 2. Restart the Docker containers:
     ```bash
-    docker-compose down
-    docker-compose up -d
+    docker compose down
+    docker compose up -d
     ```
 
 Note the database:reset command will completely erase your database and recreate it from scratch. 
@@ -125,7 +125,7 @@ If you encounter issues not covered in this guide:
 
     View container logs for error messages:
     ```bash
-    docker-compose logs
+    docker compose logs
     ```
 
 - Community Support:

packages/twenty-website/src/content/developers/self-hosting/upgrade-guide.mdx

@@ -19,7 +19,9 @@ If you used Docker Compose, follow these steps:
 
 2. Upgrade the version by changing the `TAG` value in the .env file near your docker-compose.
 
-3. Bring Twenty back online with `docker-compose up -d`
+3. Bring Twenty back online with `docker compose up -d`
+
+If you want to upgrade your instance by few versions, e.g. from 0.33.0 to 0.35.0, you have to upgrade your instance by each version, in this example from 0.33.0 to 0.34.0, then from 0.34.0 to 0.35.0.
 
 
 ## Version-specific upgrade steps
@@ -75,6 +77,8 @@ The `yarn command:prod cache:flush` command will flush the Redis cache.
 The `yarn database:migrate:prod` command will apply the migrations to the database structure (core and metadata schemas)
 The `yarn command:prod upgrade-0.33` takes care of the data migration of all workspaces.
 
+Starting from this version, twenty-postgres image for DB became deprecated and twenty-postgres-spilo is used instead.
+If you want to keep using twenty-postgres image, simply replace `twentycrm/twenty-postgres:${TAG}` with `twentycrm/twenty-postgres` in docker-compose.yml.
 
 ### v0.31.0 to v0.32.0