README.md: Fix typos and spelling errors

Signed-off-by: Bernhard Kaindl <bernhard.kaindl@cloud.com>

Author: bernhardkaindl

README.md

@@ -6,7 +6,7 @@
 [![](https://img.shields.io/badge/License-BSD--2--Cause%20%26%20MIT-brightgreen)](https://github.com/xenserver/python-libs/blob/master/LICENSE)
 
 The `xcp` directory contains the Common XenServer and XCP-ng Python packages.
-They are intented for use in XenServer and XCP-ng Dom0 only and deal with logging,
+They are for use in XenServer and XCP-ng Dom0 only and deal with logging,
 Hardware/PCI, networking, and other Dom0 tasks.
 
 The package name is `python-libs` which is also the `rpm` package name in XenServer.
@@ -23,26 +23,23 @@ Please see [CONTRIBUTING.md] for installing a local development environment.
 This package has CI which can be run locally but is also run in GitHub CI to ensure
 Test-driven development.
 
-The Continuous Integration Tests feature:
+CI features:
 
 - Combined coverage testing of Python 2.7 and Python 3.8 code branches
 - Automatic Upload of the combined coverage to CodeCov (from the GitHub Workflow)
 - Checking of the combined coverage against the diff to master: Fails if changes are not covered!
-- Pylint report in the GitHub Action Summary page, with Warning and Error annotatios, even in the code review.
-- Check that changes don't generate pylint warnings (if warning classes which are enabled in .pylintrc)
+- Pylint report in the GitHub Action Summary page, with Warning and Error annotations, even in the code review.
+- Check that changes don't generate pylint warnings (if warning classes which are enabled in `.pylintrc`)
 - Static analysis using `mypy`, `pylint`, `pyright` and `pytype`
 
 This enforces that any change (besides whitespace):
 
-- has code coverage and
+- Has code coverage,
 - does not introduce a `pylint` warning which is not disabled in `.pylintrc`
 - does not introduce a type of static analysis warning which is currently suppressed.
 
 ## Status Summary
 
-- The warnings shown on the GitHub Actions Summary Page indicate the remaining
-  work for full Pyhon3 support (excluding missing tests).
-
 ## `Pylint` results from GitHub CI in GitHub Actions page
 
 A step of the GitHub workflow produces a browser-friendly `pylint` report:
@@ -81,19 +78,19 @@ For the installation of the general development dependencies, visit [INSTALL.md]
 - Commit with `--signoff` on a new branch and push it and check the triggered GitHub Action run succeeds.
 - Open a new PR
 
-The list of `virtualenvs` configured in tox can be shown using this command: `tox -av`
+The list of `virtualenvs` configured in `tox` can be shown using this command: `tox -av`
 
 ```ml
 $ tox -av
 default environments:
 py36-lint              -> Run in a py36 virtualenv: Run pylint and fail on warnings remaining on lines in the diff to master
-py311-pyright          -> Run in a py311 virtualenv: Run pyright for static analyis
-py38-pytype            -> Run in a py38 virtualenv: Run pytype for static analyis, intro: https://youtu.be/abvW0mOrDiY
-py310-covcombine-check -> Run in a py310 virtualenv: Generate combined coverage reports with py27-test coverage merged Run mypy for static analyis
+py311-pyright          -> Run in a py311 virtualenv: Run pyright for static analysis
+py38-pytype            -> Run in a py38 virtualenv: Run pytype for static analysis, intro: https://youtu.be/abvW0mOrDiY
+py310-covcombine-check -> Run in a py310 virtualenv: Generate combined coverage reports with py27-test coverage merged Run mypy for static analysis
 
 additional environments:
-cov                    -> Run in a python virtualenv: Generate coverage html reports (incl. diff-cover) for this environment
-covcp                  -> Run in a python virtualenv: Copy the generated .converage and coverage.xml to the UPLOAD_DIR dir
+cov                    -> Run in a python virtualenv: Generate coverage html reports for this environment
+covcp                  -> Run in a python virtualenv: Copy the generated .coverage and coverage.xml to the UPLOAD_DIR dir
 fox                    -> Run in a python virtualenv: Generate combined coverage html reports and open them in firefox
 mdreport               -> Run in a python virtualenv: Make a test report (which is shown in the GitHub Actions Summary Page)
 test                   -> Run in a python virtualenv: Run pytest in this environment with --cov for use in other stages
@@ -109,8 +106,8 @@ which runs the tests in GitHub CI as well. But of course, because they code is l
 still not yet typed, no strict checks can be enabled so far. However, every checker
 which is possible now, is enabled.
 
-Checking the contents of untyped functions is enabled for all but four modules which
-would need more work. Look for `check_untyped_defs = false` in `pytproject.toml`.
+Checking the contents of not typed functions is enabled for all but four modules which
+would need more work. Look for `check_untyped_defs = false` in `pyproject.toml`.
 
 The goal or final benefit would be to have it to ensure internal type correctness
 and code quality but also to use static analysis to check the interoperability with
@@ -124,7 +121,7 @@ tools like `mypy` and `pyright` (VS Code):
 
 Quoting from <https://stackoverflow.com/questions/53306458/python-3-type-hints-in-python-2>:
 
-> Function annotations were introduced in [PEP 3107](https://www.python.org/dev/peps/pep-3107/) for Python 3.0. The usage of annotations as type hints was formalized in in [PEP 484](https://www.python.org/dev/peps/pep-0484/) for Python 3.5+.
+> Function annotations were introduced in [PEP 3107](https://www.python.org/dev/peps/pep-3107/) for Python 3.0. The usage of annotations as type hints was formalized in [PEP 484](https://www.python.org/dev/peps/pep-0484/) for Python 3.5+.
 >
 > Python < 3.0 does support the type hints syntax, but
 > [PEP 484](https://www.python.org/dev/peps/pep-0484/#suggested-syntax-for-python-2-7-and-straddling-code)
@@ -137,7 +134,7 @@ def get_default_device(use_gpu=True):
     ...
 ```
 
-Many type checkers support this syntax: mypy, pyright/pylance, pytype
+Many type checkers support this syntax: mypy, pyright, pytype
 
 As proof, these examples show how the comment below triggers the checks: