fix(handbook): fix typos

Author: gsanchietti

handbook/README.md

@@ -1,6 +1,6 @@
 # Build the documentation
 
-The documentation is built using Github pages on each commit to the main branch.
+The documentation is built using GitHub pages on each commit to the main branch.
 
 ## Build locally
 

handbook/commit_messages.md

@@ -9,7 +9,7 @@ nav_order: 6
 A commit message is a brief description of the changes made in a commit. It is a way to communicate the purpose of the change to other developers.
 A good commit message helps to understand the changes made in the commit and why they were made.
 
-All Netesis projects follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard for commit messages.
+All Nethesis projects follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard for commit messages.
 
 ## Conventional Commits standard
 

handbook/index.md

@@ -1,13 +1,13 @@
 ---
 layout: default
-title: Developer Handbook
+title: Development Handbook
 nav_order: 1
 ---
 
-# Nethesis Developer Handbook
+# Nethesis development process handbook
 {: .no_toc }
 
-[Nethesis](https://www.nethesis.it) is an Italian company specializing in the development and suppoer of Open Source software solutions. 
+[Nethesis](https://www.nethesis.it) is an Italian company specialized in the development and support of Open Source software solutions. 
 Nethesis offers a range of services including consulting, support, and training to ensure that their clients can effectively implement and benefit from their solutions.
 
 This handbook is intended to provide a comprehensive guide to the development process at Nethesis.

handbook/issues.md

@@ -144,7 +144,7 @@ Issues can be tagged using a set of well-known labels:
   to other related issue when using this tag.
 
 Before introducing new labels, please discuss them with the development team
-and make sure to describe carefully the new label inside the [NethServer label page](https://github.com/NethServer/dev/labels) or [NethSecurity labl page](https://github.com/NethServer/nethsecurity/labels).
+and make sure to describe carefully the new label inside the [NethServer label page](https://github.com/NethServer/dev/labels) or [NethSecurity label page](https://github.com/NethServer/nethsecurity/labels).
 
 ## Process the issue
 
@@ -155,7 +155,7 @@ If a developer assigns a draft issue to themselves, it indicates their intention
 This helps the developer keep track of pending tasks to address after completing their current task.
 
 When an issue is marked as in progress, it means that the assignee is actively working on it.
-Multiple assignees can collaborate on the same issue.
+Multiple assignee can collaborate on the same issue.
 
 Thus, the assignee not only shows who is responsible for a task but also assists in future planning and task management.
 
@@ -238,5 +238,5 @@ After the *QA member* has completed the testing phase:
 
 When the package is CLOSED, all related [documentation](#documentation) must be in place.
 
-At any time of the issue lifecycle they ensure that there are no release
+At any time of the issue life-cycle they ensure that there are no release
 conflict with other issues.

handbook/management.md

@@ -46,15 +46,15 @@ The meeting should include the following topics:
 - discussion of any blockers or issues
 - planning for the next steps
 
-A good pratice is to schedule the metting on fixed day and time, so everyone can plan their work accordingly.
+A good practice is to schedule the meeting on fixed day and time, so everyone can plan their work accordingly.
 If there is nothing to discuss, the team can just meet for a quick check-in.
 
 ## Project boards
 
 Project boards are used to track the progress of issues and requests. They are divided into columns that represent the status of the issue. The active project boards are:
 
 - [NethServer](https://github.com/orgs/NethServer/projects/8): NethServer is container orchestration platform, it contains the core modules and many applications, including NethVoice
-- [NethVoice](https://github.com/orgs/NethServer/projects/11): NethVoice is a VoIP platform, it's a module of NethServer and it contains many submodules like the PBX, a CTI and a desktop client
+- [NethVoice](https://github.com/orgs/NethServer/projects/11): NethVoice is a VoIP platform, it's a module of NethServer and it contains many sub-modules like the PBX, a CTI and a desktop client
 - [NethSecurity](https://github.com/orgs/NethServer/projects/10): NethSecurity is an UTM firewall, based on OpenWrt
 
 ### Project views

handbook/pull_requests.md

@@ -14,7 +14,7 @@ A pull request is a way to submit contributions to a project. It is a request to
 
 In NethServer, each repository is associated with one or more container images: changes to the code
 produce new releases of modules.
-In NethtSecurity, most of the work is done on the main repository: changes to the code produce new packages or a new image.
+In NethSecurity, most of the work is done on the main repository: changes to the code produce new packages or a new image.
 
 ## Pull requests
 
@@ -33,7 +33,7 @@ When submitting a PR, check that:
 3. PR comment contains a link to the related issue, in the form:
 
    - for NethServer and NethVoice ``NethServer/dev#<number>`` like NethServer/dev#1122
-   - for NethtSecurity ``#<number>`` when committing to the main repositority, like `#1145` or ``NethServer/nethsecurity#<number>`` like ``NethServer/nethsecurity#1155`` when committing to a module repository
+   - for NethtSecurity ``#<number>`` when committing to the main repository, like `#1145` or ``NethServer/nethsecurity#<number>`` like ``NethServer/nethsecurity#1155`` when committing to a module repository
 
 4. PR comment describes the changes and how the feature is supposed to work
 

handbook/version_numbering.md

@@ -27,7 +27,7 @@ the development process.
   site](https://semver.org/). Stable releases are published and deployed
   to production systems.
 
-- **Pre-releases or testing releases** include a prerelease suffix. This
+- **Pre-releases or testing releases** include a pre-release suffix. This
   consists of a `-` (minus sign), a word, a dot `.`, and a number, e.g.,
   `1.3.0-testing.3`. Testing releases are meant for development. In rare
   cases, they can be used in production, but only if they address specific