diff --git a/en_US.ISO8859-1/books/handbook/geom/chapter.sgml b/en_US.ISO8859-1/books/handbook/geom/chapter.sgml index 8c142e6a27..fbb7988c71 100644 --- a/en_US.ISO8859-1/books/handbook/geom/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/geom/chapter.sgml @@ -430,9 +430,9 @@ OK? boot Now to mount the device on the client machine, issue the following commands: - &prompt.root; ggatec create -o rw 192.168.1.1 /dev/da0s4d - ggate0 - &prompt.root; mount /dev/ggate0 /mnt + &prompt.root; ggatec create -o rw 192.168.1.1 /dev/da0s4d +ggate0 +&prompt.root; mount /dev/ggate0 /mnt From here on, the device may be accessed through the /mnt mount point. @@ -510,15 +510,15 @@ OK? boot the auto detection associated with permanent labels, and the fact that this type of label will be persistent across reboots. These labels are given a special directory in - /dev, which will be named + /dev, which will be named based on their file system type. For example, UFS2 file system labels will be created in - the /dev/ufs2 + the /dev/ufs2 directory. A generic label will go away with the next reboot. These labels will be created in the - /dev/label directory and + /dev/label directory and are perfect for experimentation.