fixed typos

This commit is contained in:
GammaSQ 2019-03-04 23:39:37 +01:00
parent afa8308c46
commit 48fa6ff8bb
No known key found for this signature in database
GPG Key ID: D552FD2F98647C64
3 changed files with 4 additions and 4 deletions

View File

@ -110,7 +110,7 @@ If no specific `sourceVM:deviceID` combination is given, *all devices of that DE
[block]:/doc/usb-devices-in-qubes-R4.0/
[USB]:/dock/usb-devices-in-qubes-R4.0/
[USB]:/doc/usb-devices-in-qubes-R4.0/
[PCI]:/doc/pci-devices-in-qubes-R4.0/
[security considerations]: /doc/device-considerations/

View File

@ -134,8 +134,8 @@ or
[device handling in qubes]: /doc/device-handling/
[security considerations]: /doc/device-considerations/#pci-security
[block]:/dock/usb-devices-in-qubes-R4.0/
[USB]:/dock/usb-devices-in-qubes-R4.0/
[block]:/doc/usb-devices-in-qubes-R4.0/
[USB]:/doc/usb-devices-in-qubes-R4.0/
[appmenu]: /attachment/wiki/Devices/qubes-appmenu-select.png
[domain manager icon]: /attachment/wiki/Devices/qubes-logo-icon.png
[qvm-device]: /doc/device-handling-in-qubes-R4.0/#general-qubes-device-widget-behavior-and-handling

View File

@ -64,7 +64,7 @@ If not specified otherwise, block devices will show up as `/dev/xvdi*` in a linu
where `xvdi2` needs to be replaced with the partition you want to mount.
This will make your drive content accessible under `~/mnt`.
Beware that when you attach a whole block device, partitions can be identified by their trailing integer (i.e. `/dev/xvdi2` for the second partition, `/dev/xvdi` for the whole device), whereas if you attach a single parition, the partition has *no trailing integer*.
Beware that when you attach a whole block device, partitions can be identified by their trailing integer (i.e. `/dev/xvdi2` for the second partition, `/dev/xvdi` for the whole device), whereas if you attach a single partition, the partition has *no trailing integer*.
If several different block-devices are attached to a single VM, the last letter of the device node name is advanced through the alphabet, so after `xvdi` the next device will be named `xvdj`, the next `xvdk`, and so on.