Add backup commands to documentation (#9224)

In documentation, there's mention to make a backup of database before
upgrading Twenty but there are no commands how to do it, so this PR
solves this problem by providing commands

packages/twenty-website/src/content/developers/backend-development/feature-flags.mdx

@@ -4,7 +4,7 @@ icon: TbFlag
 image: /images/user-guide/table-views/table.png
 ---
 
-Feature flags are used to hide experimental features. For twenty they are set on workspace level and not on a user level.
+Feature flags are used to hide experimental features. For Twenty, they are set on workspace level and not on a user level.
 
 ## Adding a new feature flag
 

packages/twenty-website/src/content/developers/backend-development/server-commands.mdx

@@ -33,7 +33,7 @@ npx nx run twenty-server:lint # pass --fix to fix lint errors
 npx nx run twenty-server:test:unit          # run unit tests
 npx nx run twenty-server:test:integration   # run integration tests
 ```
-Note : you can run `npx nx run twenty-server:test:integration:with-db-reset` in case you need to reset the database before running the integration tests.
+Note: you can run `npx nx run twenty-server:test:integration:with-db-reset` in case you need to reset the database before running the integration tests.
 
 ### Resetting the database
 

packages/twenty-website/src/content/developers/backend-development/zapier.mdx

@@ -8,7 +8,7 @@ Effortlessly sync Twenty with 3000+ apps using [Zapier](https://zapier.com/). Au
 
 ## About Zapier
 
-Zapier is a tool that allows you automate workflows by connecting the apps that your team uses everyday. The fundamental concept of Zapier is automation workflows, called Zaps, and include triggers and actions. 
+Zapier is a tool that allows you to automate workflows by connecting the apps that your team uses every day. The fundamental concept of Zapier is automation workflows, called Zaps, and include triggers and actions.
 
 You can learn more about how Zapier works [here](https://zapier.com/how-it-works).