doc: Fix typos

Author: jntesteves

README.md

@@ -15,7 +15,7 @@ To propose new components, it is necessary to open a [Pull Request](https://gith
 
 To do it, there is currently two methods.
 
-### 1 - Add an entry to the CI (prefered method)
+### 1 - Add an entry to the CI (preferred method)
 For most components, new stable versions (and experimental builds if they exist) are automatically pulled. This is accomplished by the [pull-components.yml](https://github.com/bottlesdevs/components/blob/main/.github/workflows/pull-components.yml) workflow, where components are described in the following format:
 
 ```yaml
@@ -31,13 +31,13 @@ Sub-category: "",
 ```
 where:
 - **repo** is the GitHub repository in the format `owner/repository`
-- **workflow** is the workflow filename used to generate exerimental builds, if any
-- **branch** is the **workflow** branch used to generate exerimental builds, if any
-- **name-prefix** is used to generate the full name of the component using **name-prefix** + `version` + **name-suffix** (e.g. `dxvk-` + `2.0` + ∅), and look for release/experimental asset whose filename is begining by **name-prefix**
-- **name-suffix** serves the exact same purpose as **name-prefix**, is only used when multiple variants are available for one component (e.g. `-x86`, `-x64`, etc)
-- **version-prefix** is used to find the latest release version whose [tag](https://github.com/doitsujin/dxvk/tags) is begining by **version-prefix**, and to remove **version-prefix** from the final `version` string (e.g. `v2.0` will become `2.0`)
+- **workflow** is the workflow filename used to generate experimental builds, if any
+- **branch** is the **workflow** branch used to generate experimental builds, if any
+- **name-prefix** is used to generate the full name of the component using **name-prefix** + `version` + **name-suffix** (e.g. `dxvk-` + `2.0` + ∅), and look for release/experimental asset whose filename is beginning by **name-prefix**
+- **name-suffix** serves the exact same purpose as **name-prefix**, is only used when multiple variants are available for one component (e.g. `-x86`, `-x64`, etc.)
+- **version-prefix** is used to find the latest release version whose [tag](https://github.com/doitsujin/dxvk/tags) is beginning by **version-prefix**, and to remove **version-prefix** from the final `version` string (e.g. `v2.0` will become `2.0`)
 - **yaml-file** is the YAML component filename located in the [input_files](https://github.com/bottlesdevs/components/blob/main/input_files) directory
-- **Category** and **Sub-category** are repectively the Category and Sub-category as described in the **yaml-file** (e.g. [14-dxvk.yml](https://github.com/bottlesdevs/components/blob/main/input_files/14-dxvk.yml))
+- **Category** and **Sub-category** are respectively the Category and Sub-category as described in the **yaml-file** (e.g. [14-dxvk.yml](https://github.com/bottlesdevs/components/blob/main/input_files/14-dxvk.yml))
 
 ### 2 - Manually (legacy method)
 Each poster must follow the following layout:
@@ -51,9 +51,7 @@ File:
   file_checksum: 659ee0ee3dbe5274825734ad19692e12
   rename: caffe-7.2-x86_64.tar.xz
 ```
-old json manifests can be converted using this [online tool](https://www.json2yaml.com).
-
-where:
+Old JSON manifests can be converted using this [online tool](https://www.json2yaml.com), where:
 - **Name** is a name without spaces, including version, of the component (must reflect the name of the manifest file)
 - **Provider** is the name of the component supplier (not the maintainer)
 - **Channel** should be stable or unstable
@@ -74,9 +72,9 @@ Post:
 
 We provide an [automatic tools](https://github.com/bottlesdevs/tools/blob/main/MaintainersHelpers/component-generator.py) for generating the manifest.
 
-In addition to the manifest, en entry must be created in the corresponding file located in the [input_files](https://github.com/bottlesdevs/components/blob/main/input_files) directory. The index can then be regenerated using the [generate_index.sh](https://github.com/bottlesdevs/components/blob/main/generate_index.sh) script.
+In addition to the manifest, an entry must be created in the corresponding file located in the [input_files](https://github.com/bottlesdevs/components/blob/main/input_files) directory. The index can then be regenerated using the [generate_index.sh](https://github.com/bottlesdevs/components/blob/main/generate_index.sh) script.
 
-Please double check and test using the `LOCAL_COMPONENTS=/path/to/components flatpak run com.usebottles.bottles` command before open a pull request.
+Please double-check and test using the `LOCAL_COMPONENTS=/path/to/components flatpak run com.usebottles.bottles` command before open a pull request.
 
 ### Guidelines
 The sources of the components must be public and searchable and must not infringe any copyright. Also, each archive must contain the compiled version and not the source code.