btrfs-progs: README: spelling fixes

Signed-off-by: Diego Viola <[email protected]>

Author: diegoviola

README.md

@@ -30,26 +30,26 @@ testing information and [ci/README.md](ci/README.md) for CI information.
 Release cycle
 -------------
 
-The major version releases are time-based and follow the cycle of the linux
-kernel releases. The cycle usually takes 2 months. A minor version releases may
+The major version releases are time-based and follow the cycle of the Linux
+kernel releases. The cycle usually takes 2 months. A minor version release may
 happen in the meantime if there are bug fixes or minor useful improvements
 queued.
 
 The release tags are signed with a GPG key ID `F2B4 1200 C54E FB30 380C  1756 C565 D5F9 D76D 583B`,
 release tarballs are hosted at [kernel.org](https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/).
 See file [CHANGES](CHANGES) or [changelogs on RTD](https://btrfs.readthedocs.io/en/latest/CHANGES.html).
 
-Releases with changelog are also published at [Github release page](https://github.com/kdave/btrfs-progs/releases).
+Releases with changelog are also published at [GitHub release page](https://github.com/kdave/btrfs-progs/releases).
 
 ### Static binaries
 
 For each release there are static binaries of `btrfs` and `btrfs.box` provided.
 These can be used in rescue environments and are built for `x86_64`
-architecture (with maximum backward compatibility), inside the [Github Actions
+architecture (with maximum backward compatibility), inside the [GitHub Actions
 workflow](https://github.com/kdave/btrfs-progs/actions/workflows/artifacts-static-build.yml).
 The `btrfs.box` is an all-in-one tool in the [busybox](https://www.busybox.net)
 style, the functionality is determined by the binary names (either symlink,
-hradlink or a file copy).
+hardlink or a file copy).
 
 ### Feature compatibility
 
@@ -67,7 +67,7 @@ The supported compilers are [gcc](https://gcc.gnu.org/) (minimal version 4.8)
 and [clang](https://clang.llvm.org/) (minimal version 3.4).
 
 Build tests are done on [several distributions](https://github.com/kdave/btrfs-progs/blob/master/.github/workflows/ci-build-test.yml), see
-[Github actions workflow](https://github.com/kdave/btrfs-progs/actions/workflows/ci-build-test.yml).
+[GitHub Actions workflow](https://github.com/kdave/btrfs-progs/actions/workflows/ci-build-test.yml).
 
 Reporting bugs
 --------------
@@ -76,18 +76,18 @@ There are several ways, each has its own specifics and audience that can give
 feedback or work on a fix. The following list is sorted in the order of
 preference:
 
-* [Github issue tracker](https://github.com/kdave/btrfs-progs/issues)
+* [GitHub issue tracker](https://github.com/kdave/btrfs-progs/issues)
 * to the mailing list *[email protected]* -- (not required to
   subscribe), beware that the mail might get overlooked in other traffic
-* IRC (irc.libera.chat #btrfs) -- good for discussions eg. if a bug is already
+* IRC (irc.libera.chat #btrfs) -- good for discussions e.g. if a bug is already
   known, but reports could miss developers' attention
 * please don't use https://bugzilla.kernel.org for btrfs-progs bugs
 
 Development
 -----------
 
 The development takes place in the mailing list (*[email protected]*)
-or at Github (issues, pull requests). Changes should be split to logical parts
+or at GitHub (issues, pull requests). Changes should be split to logical parts
 if possible, documentation may be included in the same patch as to code or
 separately.
 
@@ -106,14 +106,14 @@ The development model of btrfs-progs shares a lot with the kernel model. The
   change, you can read more about the
   [The Developer's Certificate of Origin (chapter 11)](https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin)
   * if you are not used to the signed-off style, your contributions won't be
-    rejected just because of it's missing, the _Author:_ tag will be added as a
+    rejected just because of it missing, the _Author:_ tag will be added as a
     substitute in order to allow contributions without much bothering with
     formalities
 
 ### Pull requests
 
-The pull requests on Github may be used for code or documentation
-contributions. There are basic build checks enabled in the Github actions CI
+The pull requests on GitHub may be used for code or documentation
+contributions. There are basic build checks enabled in the GitHub Actions CI
 for pull requests. The status can be checked at the
 [workflow page](https://github.com/kdave/btrfs-progs/actions/workflows/pull-request.yml).
 
@@ -135,7 +135,7 @@ The documentation for writing and running tests can be found in
 [tests/](tests/README.md) and continuous integration/container images in
 [ci/](ci/README.md).
 
-Development branches are tested by Github
+Development branches are tested by GitHub
 [Action workflows](https://github.com/kdave/btrfs-progs/actions).
 
 Code coverage provided by [codecov.io](https://codecov.io) can be found
@@ -173,7 +173,7 @@ The builtin implementations uses the following sources:
 [SHA256](https://tools.ietf.org/html/rfc4634),
 [BLAKE2](https://github.com/BLAKE2/BLAKE2).
 
-Some other code is borrowed from kernel, eg. the raid5 tables or data structure
+Some other code is borrowed from kernel, e.g. the raid5 tables or data structure
 implementation (list, rb-tree).
 
 References