Skip to content

Commit dbaf4ee

Browse files
authored
Merge pull request #300 from chuanchang/fix_typos
docs: fix typos
2 parents 8558c96 + 1831ab6 commit dbaf4ee

File tree

5 files changed

+9
-9
lines changed

5 files changed

+9
-9
lines changed

cli/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ default-run = "bootc"
1212
# See https://github.com/coreos/cargo-vendor-filterer
1313
[package.metadata.vendor-filter]
1414
# This list of platforms is not intended to be exclusive, feel free
15-
# to extend it. But missing a platfom will only matter for the case where
15+
# to extend it. But missing a platform will only matter for the case where
1616
# a dependent crate is *only* built on that platform.
1717
platforms = ["x86_64-unknown-linux-gnu", "aarch64-unknown-linux-gnu", "powerpc64le-unknown-linux-gnu", "s390x-unknown-linux-gnu", "riscv64gc-unknown-linux-gnu"]
1818

docs/relationship-particles.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The "bootc vision" aligns with parts of this, but differs in emphasis and also s
1515
The "particle" proposal mentions that the desktop case is most
1616
interesting; the bootc belief is that servers are equally
1717
important and interesting. In practice, this is not a real point
18-
of differentation, because the systemd project has done an excellent
18+
of differentiation, because the systemd project has done an excellent
1919
job in catering to all use cases (desktop, embedded, server) etc.
2020

2121
An important aspect related to this is that the bootc project exists and must
@@ -52,7 +52,7 @@ bootc aims to support the same. And in practice, nothing in "particles" strictl
5252
requires Secure Boot etc.
5353

5454
However, bootc has a stronger emphasis on continuing to support "unlocked"
55-
systems into the forseeable future in which key (even root level) operating system
55+
systems into the foreseeable future in which key (even root level) operating system
5656
changes can be that are outside of an explicit signed state and feel
5757
*equally* first class, not just "developer system extensions".
5858

@@ -266,7 +266,7 @@ The bootc project will align with podman in general, and make it easy to impleme
266266
a mechanism that chains keys stored alongside the operating system into composefs-signed
267267
application containers.
268268

269-
Configuration (effectively starting from `/etc` and the kernel commandline) in a "sealed" system is a complex topic. Many operting system builds will want to disable the default "etc merge" and make `/etc` always lifecycle bound with the OS: commonly writable but ephemeral.
269+
Configuration (effectively starting from `/etc` and the kernel commandline) in a "sealed" system is a complex topic. Many operating system builds will want to disable the default "etc merge" and make `/etc` always lifecycle bound with the OS: commonly writable but ephemeral.
270270

271271
This topic is covered more in the next section.
272272

docs/relationship.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ For example, `bootc status` at least will still function even if packages are la
7777
### Future bootc <-> podman binding
7878

7979
All the above said, it is likely that at some point bootc will switch to [hard binding with podman](https://github.com/containers/bootc/pull/215).
80-
This will reduce the role of ostree, and hence break compatibilty with rpm-ostree.
80+
This will reduce the role of ostree, and hence break compatibility with rpm-ostree.
8181
When such work lands, we will still support at least a "one way" transition from an
8282
ostree backend. But once this happens there are no plans to teach rpm-ostree
8383
to use podman too.

manpages-md/bootc-install-to-disk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ By default, all remaining space on the disk will be used.
5252

5353
By default, bootc install and install-to-filesystem assumes that it runs
5454
in a podman container, and it takes the container image to install from
55-
the podmans container registry. If \--source-imgref is given, bootc uses
55+
the podman's container registry. If \--source-imgref is given, bootc uses
5656
it as the installation source, instead of the behaviour explained in the
5757
previous paragraph. See skopeo(1) for accepted formats.
5858

@@ -77,7 +77,7 @@ previous paragraph. See skopeo(1) for accepted formats.
7777

7878
**\--skip-fetch-check**
7979

80-
: By default, the accessiblity of the target image will be verified
80+
: By default, the accessibility of the target image will be verified
8181
(just the manifest will be fetched). Specifying this option
8282
suppresses the check; use this when you know the issues it might
8383
find are addressed.

manpages-md/bootc-install-to-filesystem.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ be used.
6060

6161
By default, bootc install and install-to-filesystem assumes that it runs
6262
in a podman container, and it takes the container image to install from
63-
the podmans container registry. If \--source-imgref is given, bootc uses
63+
the podman's container registry. If \--source-imgref is given, bootc uses
6464
it as the installation source, instead of the behaviour explained in the
6565
previous paragraph. See skopeo(1) for accepted formats.
6666

@@ -85,7 +85,7 @@ previous paragraph. See skopeo(1) for accepted formats.
8585

8686
**\--skip-fetch-check**
8787

88-
: By default, the accessiblity of the target image will be verified
88+
: By default, the accessibility of the target image will be verified
8989
(just the manifest will be fetched). Specifying this option
9090
suppresses the check; use this when you know the issues it might
9191
find are addressed.

0 commit comments

Comments
 (0)