Apply suggestions from code review

Improve wording

Co-authored-by: Matti Schneider <[email protected]>

Author: Ndpnt

content/collections/how-to/manage-custom-terms-type.md

@@ -31,9 +31,9 @@ Review the [supported types list](https://github.com/OpenTermsArchive/terms-type
 
 ## Long-term solution
 
-The recommended approach is to contribute your new terms type to the official list. This helps maintain consistency across collections and enables better comparison of terms across different services.
+The recommended approach is to contribute your new terms type to the official list. This enables collections interoperability and comparison of terms across different services.
 
-You can propose your new terms type for inclusion in the official list of supported types via the [dedicated repository](https://github.com/OpenTermsArchive/terms-types), following the [contribution process](https://github.com/OpenTermsArchive/terms-types/blob/main/CONTRIBUTING.md#add-new-terms-types).
+You can suggest new terms type for the official list via the dedicated [contribution process](https://github.com/OpenTermsArchive/terms-types/blob/main/CONTRIBUTING.md#add-new-terms-types).
 
 This process has the following benefits:
 
@@ -42,7 +42,7 @@ This process has the following benefits:
 - It helps build a more comprehensive and useful shared list
 - Enables better comparison of terms across different services
 
-This solution can take some time to have your terms type to be approved, so if you need a faster solution, you can proceed with the following temporary solutions.
+Inclusion in the official terms types list has a delay for consensus building. In the meantime, you can proceed with the following temporary solutions.
 
 ## Temporary solutions
 

content/deployment/how-to/deploy.md

@@ -24,7 +24,7 @@ Before starting, ensure you have:
 - A server with admin access
 - All collections repositories created, if not, see the [guide to create repositories]({{< relref "collections/how-to/create-repositories" >}})
 - At least one declaration added to your collection
-- A GitHub user account dedicated to bot-related actions (commit entries in versions and snapshots repositories, report issues when tracking fails, publish releases, …)
+- A GitHub user account to automate actions such as committing entries in versions and snapshots repositories, reporting issues when tracking fails, publishing releases…
 - [Ansible](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) installed on your local machine
 
 > **Note**: This guide is intended for both Open Terms Archive organization members and external contributors. Some steps marked with "_Specific to Open Terms Archive organization members_" are only relevant for organization members as they involve access to the organization's shared password database. External contributors should adapt these steps to their own security practices while following the same deployment principles.
@@ -57,7 +57,7 @@ First, ensure your server provides unsupervised access:
 
    > **Note**: The `adduser` command might not be installed by default on your system. It can be installed with `sudo apt-get install adduser`.
 
-3. Configure passwordless sudo access for this user, by running the adding the following line to the `/etc/sudoers` file on the server:
+3. Configure passwordless sudo access for this user, by adding the following line to the `/etc/sudoers` file on the server:
 
    ```shell
    <deployment_user> ALL=(ALL) NOPASSWD:ALL