[FIX] fix some typos

docsource/040_run_migration.rst

@@ -14,7 +14,7 @@ OpenUpgrade
 Make the `openupgrade_framework` and the `openupgrade_scripts` modules
 available in the addons path in the Odoo instance of the new version.
 
-Or, for older versions: check out the OpenUpgrade source code from Github
+Or, for older versions: check out the OpenUpgrade source code from GitHub
 for the branches you need. Each branch migrates to its version from the
 previous version, so branch 13.0 migrates from 12.0 to 13.0. If you are
 migrating across multiple versions, you need to run each version of
@@ -87,7 +87,7 @@ Run the upgrade and check for errors. You will probably learn a lot about
 your data and have to do some manual clean up before and after the upgrade.
 Expect to repeat the process several times as you encounter errors, clean up
 your data, and try again. If necessary, ask for help or report bugs on
-Github.
+GitHub.
 
 Write the missing migration scripts
 ...................................

docsource/070_migration_files.rst

@@ -117,7 +117,7 @@ The change description flags the following types of change:
       stopped doing so. You need to audit the function for any change in
       possible values and may need to map any differences you encounter.
 
-      (Of course, a selection function could change the set of posible values
+      (Of course, a selection function could change the set of possible values
       in between functions.)
 
     * The field changes type. This always calls for action in your upgrade
@@ -130,7 +130,7 @@ The change description flags the following types of change:
       res.partner.title.
 
     * A relation field's relation changes. You need to migrate the one target
-      model to the other, and update the references to them
+      model to the other, and update the references to them.
 
     * A field is deleted from the model (marked by 'DEL'). Also fields from
       deleted models are marked in this way. TODO: mark fields from deleted
@@ -183,4 +183,4 @@ When XML ids of such record types change, the record will be recreated under
 the new id, and the old record will be unlinked.
 
 To manage changes to data defined with the noupdate flag,
-please refer to the following use case :doc:`use_cases/xml_id_renaming`.
+please refer to the following use case :doc:`use_cases/xml_id_renaming`.

docsource/080_migration_script_development.rst

@@ -32,7 +32,7 @@ See `OpenUpgrade API <https://oca.github.io/openupgradelib/API.html>`_
 For many modules, a developer will not even need to write any function, but will
 "simply" need to call pre-existing functions from `openupgradelib` with the appropriate
 arguments. The main complexities becomes to learn what are the functions available in
-`openupgradelib` and then to select appropriatly the arguments (usually according to
+`openupgradelib` and then to select appropriately the arguments (usually according to
 the `openupgrade_analysis.txt`, see below).
 
 For instance, the migration to version 13 of mass_mailing did not require any custom

docsource/090_contribute.rst

@@ -27,7 +27,7 @@ module from version 15.0 to version 16.0:
   * Then, ensure that all the dependencies of the module are mark as ``done`` or
     ``Nothing to do`` in OpenUpgrade for that version.
     For that purpose, refer to :doc:`030_coverage_analysis`.
-    In our example, check the ``depends`` key of the `manifest <https://github.com/odoo/odoo/blob/16.0/addons/account/__manifest__.py#L18>`_ of the ``account`` module 
+    In our example, check the ``depends`` key of the `manifest <https://github.com/odoo/odoo/blob/16.0/addons/account/__manifest__.py#L18>`_ of the ``account`` module
     If some dependencies are missing, you should start by migrating these modules.
 
 **Note**
@@ -96,7 +96,7 @@ Writing migration scripts for Odoo is a lot of work, that can not be
 accomplished by a single party.  We need your help.
 
 If you are at all interested in discussing strategic, functional or
-technical issues, please post an issue on the Github project:
+technical issues, please post an issue on the GitHub project:
 `<https://github.com/OCA/OpenUpgrade>`_.
 
 If you are a developer, give the OpenUpgrade software a go and give us

docsource/100_maintain_repository.rst

@@ -24,7 +24,7 @@ Manual changes
 
 * In the ``OpenUpgrade``/``documentation`` branch, add a new line in ``build_openupgrade_docs``.
 
-* Push a test database for the old release to Github (see https://github.com/OCA/OpenUpgrade/wiki/How-to-create-a-reference-database)
+* Push a test database for the old release to GitHub (see https://github.com/OCA/OpenUpgrade/wiki/How-to-create-a-reference-database)
 
 * Execute the technical migration of ``openupgrade_framework``.