diff options
| author | Samanta Navarro <ferivoz@riseup.net> | 2022-12-30 11:52:49 +0000 |
|---|---|---|
| committer | Marian Csontos <mcsontos@redhat.com> | 2023-01-03 16:09:58 +0100 |
| commit | aec5e573afe610070eb2c6bed675d2a7c0efc7e8 (patch) | |
| tree | 23413bbc3535ca0ca7dc42c8ed5dcbca56222bf0 /doc/udev_assembly.txt | |
| parent | 118145b07249d96f4f61521bb1daf04cc8d4c1e9 (diff) | |
| download | lvm2-aec5e573afe610070eb2c6bed675d2a7c0efc7e8.tar.gz | |
doc: fix typos in documentation
Typos found with codespell.
Diffstat (limited to 'doc/udev_assembly.txt')
| -rw-r--r-- | doc/udev_assembly.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/udev_assembly.txt b/doc/udev_assembly.txt index 618640273..45af41209 100644 --- a/doc/udev_assembly.txt +++ b/doc/udev_assembly.txt @@ -35,7 +35,7 @@ VGs from PVs as they appear, and at the same time collect information on what is already available. A command, pvscan --cache is expected to be used to implement udev rules. It is relatively easy to make this command print out a list of VGs (and possibly LVs) that have been made available by adding any -particular device to the set of visible devices. In othe words, udev says "hey, +particular device to the set of visible devices. In other words, udev says "hey, /dev/sdb just appeared", calls pvscan --cache, which talks to lvmetad, which says "cool, that makes vg0 complete". Pvscan takes this info and prints it out, and the udev rule can then somehow decide whether anything needs to be done |