diff options
| author | Jan Engelhardt <[email protected]> | 2013-03-30 03:27:50 +0100 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2013-04-02 10:44:52 -0700 |
| commit | 4e95cc99b029f519ec1d3fd86df2910e7cb0d156 (patch) | |
| tree | 805233e7af5760861bbad4822ad5a3d08797ffe6 /module | |
| parent | 4a5b1218088842cd5004d167da25ea96eb9a1a11 (diff) | |
build: resolve orthographic and other grammatical errors
Signed-off-by: Jan Engelhardt <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'module')
| -rw-r--r-- | module/zfs/vdev_disk.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/module/zfs/vdev_disk.c b/module/zfs/vdev_disk.c index 1f6507f2f..08f64a913 100644 --- a/module/zfs/vdev_disk.c +++ b/module/zfs/vdev_disk.c @@ -268,13 +268,13 @@ vdev_disk_open(vdev_t *v, uint64_t *psize, uint64_t *max_psize, * Devices are always opened by the path provided at configuration * time. This means that if the provided path is a udev by-id path * then drives may be recabled without an issue. If the provided - * path is a udev by-path path then the physical location information + * path is a udev by-path path, then the physical location information * will be preserved. This can be critical for more complicated * configurations where drives are located in specific physical * locations to maximize the systems tolerence to component failure. - * Alternately you can provide your own udev rule to flexibly map + * Alternatively, you can provide your own udev rule to flexibly map * the drives as you see fit. It is not advised that you use the - * /dev/[hd]d devices which may be reorder due to probing order. + * /dev/[hd]d devices which may be reordered due to probing order. * Devices in the wrong locations will be detected by the higher * level vdev validation. */ |