Now that we automatically format GCE PD, remove formatting from the e2e test.

Also remove docs that note that it is necessary.

docs/volumes.md

@@ -41,7 +41,7 @@ Watch out when using this type of volume, because:
   - When Kubernetes adds resource-aware scheduling, as is planned, it will not be able to account for resources used by a HostDir.
 
 ### GCEPersistentDisk
-__Important: You must create and format a PD before you can use it__
+__Important: You must create a PD using ```gcloud``` or the GCE API before you can use it__
 
 A Volume with a GCEPersistentDisk property allows access to files on a Google Compute Engine (GCE)
 [Persistent Disk](http://cloud.google.com/compute/docs/disks).
@@ -55,20 +55,10 @@ There are some restrictions when using a GCEPersistentDisk:
     - replication controllers with replicas > 1 can only be created for pods that use read-only mounts.
 
 #### Creating a PD
-Before you can use a GCE PD with a pod, you need to create it and format it.
-
-__We are actively working on making this more streamlined.__
+Before you can use a GCE PD with a pod, you need to create it.
 
 ```sh
-DISK_NAME=my-data-disk
-DISK_SIZE=500GB
-ZONE=us-central1-a
-
-gcloud compute disks create --size=$DISK_SIZE --zone=$ZONE $DISK_NAME
-gcloud compute instances attach-disk --zone=$ZONE --disk=$DISK_NAME --device-name temp-data kubernetes-master
-gcloud compute ssh --zone=$ZONE kubernetes-master \
-  --command "sudo mkdir /mnt/tmp && sudo /usr/share/google/safe_format_and_mount /dev/disk/by-id/google-temp-data /mnt/tmp"
-gcloud compute instances detach-disk --zone=$ZONE --disk $DISK_NAME kubernetes-master
+gcloud compute disks create --size=500GB --zone=us-central1-a my-data-disk
 ```
 
 #### GCE PD Example configuration:
@@ -88,7 +78,7 @@ desiredState:
       - name: testpd
         source:
           persistentDisk:
-            # This GCE PD must already exist and be formatted ext4
+            # This GCE PD must already exist.
             pdName: test
             fsType: ext4
 id: testpd