Improve markup a bit; also disklabel64 (default used) c part. isn't whole disk, delet...

diff --git a/docs/newhandbook/environmentquickstart/index.mdwn b/docs/newhandbook/environmentquickstart/index.mdwn
index f39b446..562e740 100644 (file)
--- a/docs/newhandbook/environmentquickstart/index.mdwn
+++ b/docs/newhandbook/environmentquickstart/index.mdwn
@@ -1,4 +1,4 @@
-This document describes the dragonfly environment one will find on a newly installed system using the default options in the installer after selecting HAMMER for the file systems option.
+This document describes the DragonFly environment one will find on a newly installed system using the default options in the installer after selecting HAMMER for the file systems option.
 
 [[!toc levels=3 ]]
 
@@ -24,7 +24,7 @@ left with a system with the following disk configuration
 
 In this example
 
-**/dev/serno/9VMBWDM1** is the hard disk specified with QUID
+**/dev/serno/9VMBWDM1** is the hard disk specified with serial number,
 
 **/dev/serno/9VMBWDM1.s1** is the first slice on the hard disk.
 
@@ -63,23 +63,22 @@ Let us see its disklabel
       d-stor_uuid: eb1c8b21-d2af-11df-b588-01138fad54f5
 
 
-The slice 1 has 3 partitions
+The slice has 3 partitions:
 
 a - for /boot
-b - for swap
 
-c- is usually for the whole hard disk in BSDs but it is not shown here
+b - for swap
 
-d - the hammer File system labeled ROOT
+d - for /, a HAMMER file system labeled ROOT
 
-When you create a hammer file system you should give it a label, here the Installer labeled it as "ROOT" and mounted it as
+When you create a HAMMER file system you must give it a label, here the Installer labeled it as "ROOT" and mounted it as
 
     ROOT                      288G    12G   276G     4%    /
 
-Now a PFS is a Pseudo hammer File System inside a hammer file system.The hammer file system in which the PFSes are created is referred to as the root file system.( You should not confuse the "root" file system with the Label "ROOT" the label can be anything it is just that the installer Labeled it as ROOT
-because it is mounted as / )
+Now a PFS is a Pseudo File System inside a HAMMER file system. The HAMMER file system in which the PFSes are created is referred to as the root file system. (You should not confuse the "root" file system with the Label "ROOT", the label can be anything it is just that the installer Labeled it as ROOT
+because it is mounted as /)
 
-Now Inside the ROOT hammer file system you find the installed created 7 PFSes from the 'df -h' output above, let us see how they are mounted in fstab
+Now inside the ROOT HAMMER file system you find the installed created 7 PFSes from the `df -h' output above, let us see how they are mounted in fstab
 
     # cat /etc/fstab
     # Device                Mountpoint      FStype  Options         Dump    Pass#
@@ -96,9 +95,9 @@ Now Inside the ROOT hammer file system you find the installed created 7 PFSes fr
     proc                    /proc           procfs  rw              0       0
 
 
-The PFSes are mounted using a NULL mount because they are also hammer file systems.You can read more on null mounts here [mount_null(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=mount_null&section=8).
+The PFSes are mounted using a NULL mount because they are also HAMMER file systems. You can read more on NULL mounts here [mount_null(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=mount_null&section=8).
 
-You don't need to specify a Size for the PFSes like you do for Logical Volumes inside a Volume Group for LVM. All the Free space in the root hammer file system is available for all the PFSes to grow.That is the reason in the "**df -h**" output above you saw free space is same for all PFSes and the root hammer file system.
+You don't need to specify a Size for the PFSes like you do for Logical Volumes inside a Volume Group for LVM. All the Free space in the root HAMMER file system is available for all the PFSes to grow. That is the reason in the `df -h' output above you saw free space is same for all PFSes and the root HAMMER file system.
 
 Now if you look in /var
 
@@ -123,15 +122,17 @@ If you look at the status of one of the PFSes say /usr you will see /var/hammer
         operating as a MASTER
         snapshots directory defaults to /var/hammer/<pfs>
     }
+   #
 
-But there is no "hammer" directory in /var now.That is because no snapshots are yet taken.You can verify this by checking the snapshots available for /usr
+
+But there is no "hammer" directory in /var now. That is because no snapshots are yet taken. You can verify this by checking the snapshots available for /usr
 
     # hammer snapls /usr
     Snapshots on /usr       PFS #3
     Transaction ID          Timestamp               Note
     #
 
-The best way to take a snapshot of the whole system is to run the command 'hammer cleanup'. It does a lot of things but the fist thing it does during cleanup of a PFS is to take its snapshots as configured.
+The best way to take a snapshot of the whole system is to run the command `hammer cleanup'. It does a lot of things but the fist thing it does during cleanup of a PFS is to take its snapshots as configured.
 
     # sudo hammer cleanup
     cleanup /                    - HAMMER UPGRADE: Creating snapshots
@@ -208,7 +209,7 @@ The best way to take a snapshot of the whole system is to run the command 'hamme
                   recopy - run....
     #
 
-You  must have noticed that snapshots were not taken for '/tmp', '/usr/obj' and '/var/tmp'.That is how it is automatically configured by the installer.
+You  must have noticed that snapshots were not taken for '/tmp', '/usr/obj' and '/var/tmp'. That is how it is automatically configured by the installer.
 
 Let us look again in /var now
 
@@ -251,7 +252,7 @@ We have a symlink pointing to the snapshot Transaction ID shown below.
     #
 
 
-You can read more about snapshots, prune, reblance,reblock,recopy etc from [hammer(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=hammer&section=8) especially look under the heading " cleanup [filesystem ...]"
+You can read more about snapshots, prune, reblance, reblock, recopy etc from [hammer(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=hammer&section=8) especially look under the heading "cleanup [filesystem ...]"
 
 You can learn more about PFS mirroring [here](http://www.dragonflybsd.org/docs/how_to_implement_hammer_pseudo_file_system__40___pfs___41___slave_mirroring_from_pfs_master/)
 
@@ -261,7 +262,7 @@ Described in detail [here](http://www.dragonflybsd.org/docs/docs/newhandbook/ssh
 
 ## Software/Programs and Configuration Files Location 
 
-DragonFlY default installation contains the base software/programs from the dragonfly project itself and few other software from [pkgsrc](http://www.netbsd.org/docs/software/packages.html) which is the dragonfly official package management system. Ready to install binary software from pkgsrc is referred to as "<b>Packages</b>".
+DragonFly default installation contains the base software/programs from the DragonFly project itself and few other software from [pkgsrc](http://www.netbsd.org/docs/software/packages.html) which is the DragonFly official package management system. Ready to install binary software from pkgsrc is referred to as "<b>Packages</b>".
 
 The base programs are located in the folders 
 
@@ -281,7 +282,7 @@ For those who are new to the BSD way of doing things can also have the Debian's
 
 **pkgin** does things similar to **apt-get** or **aptitude** or **yum** for that matter.
 
-First we need to configure pkgin to use a repository which contains the pkgsrc binary packages. You can get a list of dragonfly mirrors [here](http://www.dragonflybsd.org/mirrors/). For this example we will use the <b>Belarus</b> [HTTP mirror](http://mirror.datacenter.by/pub/DragonFlyBSD/) shown on that page first under Europe.
+First we need to configure pkgin to use a repository which contains the pkgsrc binary packages. You can get a list of DragonFly mirrors [here](http://www.dragonflybsd.org/mirrors/). For this example we will use the <b>Belarus</b> [HTTP mirror](http://mirror.datacenter.by/pub/DragonFlyBSD/) shown on that page first under Europe.
 
 
     #echo "http://mirror.datacenter.by/pub/DragonFlyBSD/packages/i386/DragonFly-2.7/stable/All/" > /usr/pkg/etc/pkgin/repositories.conf
@@ -392,8 +393,3 @@ All the **pkgin** commands can be seen [here](http://imil.net/pkgin/). **pkgin**
 
 To install a desktop you can [read the following](http://www.dragonflybsd.org/docs/newhandbook/X/)
 Other Docs can be found [here](http://www.dragonflybsd.org/docs/newhandbook/X/). When ever you find **pkg_add** or **pkg_radd** used to install a software just use **pkgin** instead.
-
-
-
-
-