diff options
| author | Michael Olbrich <m.olbrich@pengutronix.de> | 2021-07-16 12:11:08 +0200 |
|---|---|---|
| committer | Michael Olbrich <m.olbrich@pengutronix.de> | 2021-07-16 21:24:44 +0200 |
| commit | 2e9845364f37febb476534bd7983b38dbcfecb3d (patch) | |
| tree | 3a27888dc43ca1735eab353b5a0905404f1f8a83 /doc | |
| parent | 4129dc58d1bc6f075d5dff9fcf36981088106386 (diff) | |
| download | ptxdist-2e9845364f37febb476534bd7983b38dbcfecb3d.tar.gz ptxdist-2e9845364f37febb476534bd7983b38dbcfecb3d.tar.xz | |
spelling fixes found by codespell
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/daily_work.inc | 4 | ||||
| -rw-r--r-- | doc/multi_image_platforms.inc | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/daily_work.inc b/doc/daily_work.inc index 8fe7739aa..3b436c21f 100644 --- a/doc/daily_work.inc +++ b/doc/daily_work.inc @@ -1443,9 +1443,9 @@ A different approach to have a writable ``/var`` without persistency is to use a so called *overlay filesystem*. This *overlay filesystem* is a transparent writable layer on top of a read-only filesystem. After the system's start the *overlay filesystem layer* is empty and all reads will be satisfied by the -underlaying read-only filesystem. Writes (new files, directories, changes of +underlying read-only filesystem. Writes (new files, directories, changes of existing files) are stored in the *overlay filesystem layer* and on the -next read satisfied by this layer, instead of the underlaying read-only +next read satisfied by this layer, instead of the underlying read-only filesystem. PTXdist supports this use case, by enabling the *overlay* feature for the diff --git a/doc/multi_image_platforms.inc b/doc/multi_image_platforms.inc index 2a8444391..2c8838f4e 100644 --- a/doc/multi_image_platforms.inc +++ b/doc/multi_image_platforms.inc @@ -96,5 +96,5 @@ To boot from SD-Card a disk image including bootloader, partition table and rootfs is needed. The ``image-genimage`` template can be uses again to create such an image for each variant. -.. note:: The genimage config files in ``config/images/`` are good examles +.. note:: The genimage config files in ``config/images/`` are good examples when writing genimage for the new images. |