@@ -31,7 +31,7 @@ Release cycle
3131-------------
3232
3333The major version releases are time-based and follow the cycle of the linux
34- kernel releases. The cycle usually takes 2 months. A minor version releases may
34+ kernel releases. The cycle usually takes 2 months. A minor version release may
3535happen in the meantime if there are bug fixes or minor useful improvements
3636queued.
3737
@@ -49,7 +49,7 @@ architecture (with maximum backward compatibility), inside the [Github Actions
4949workflow] ( https://github.com/kdave/btrfs-progs/actions/workflows/artifacts-static-build.yml ) .
5050The ` btrfs.box ` is an all-in-one tool in the [ busybox] ( https://www.busybox.net )
5151style, the functionality is determined by the binary names (either symlink,
52- hradlink or a file copy).
52+ hardlink or a file copy).
5353
5454### Feature compatibility
5555
@@ -106,7 +106,7 @@ The development model of btrfs-progs shares a lot with the kernel model. The
106106 change, you can read more about the
107107 [ 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 )
108108 * if you are not used to the signed-off style, your contributions won't be
109- rejected just because of it's missing, the _ Author:_ tag will be added as a
109+ rejected just because it's missing, the _ Author:_ tag will be added as a
110110 substitute in order to allow contributions without much bothering with
111111 formalities
112112
0 commit comments