final changes and revert to old nav

apps/volume-manage.html.markerb

@@ -1,13 +1,13 @@
 ---
 title: Manage volume storage
 layout: docs
-nav: volumes
+nav: firecracker
 order: 40
 ---
 
 Manage Fly Volumes using the [`fly volumes`](/docs/flyctl/volumes/) command.
 
-<div class="callout">**Note**: `fly volumes` is aliased to `fly volume` and `fly vol`.</div>
+<div class="note icon">**Note**: `fly volumes` is aliased to `fly volume` and `fly vol`.</div>
 
 ## Create a volume
 

apps/volume-storage.html.markerb

@@ -1,17 +1,17 @@
 ---
 title: Add volume storage
 layout: docs
-nav: volumes
+nav: firecracker
 order: 30
 ---
 
 Fly Volumes are local persistent storage for [Fly Machines](/docs/machines/). Learn [how Fly Volumes work](/docs/reference/volumes/).
 
 ## Launch a new app with a Fly Volume
 
-Launch a new app with one Machine and an attached volume, and then clone the Machine to scale out.
+Use [Fly Launch](/docs/apps/) to create a new app with one Machine and an attached volume, and then clone the Machine to scale out.
 
-1. Launch a new app, and type `N` at the "deploy now?" prompt:
+1. Launch a new app from your project source directory, and type `N` at the "deploy now?" prompt:
 
     ```cmd
     fly launch 
@@ -41,7 +41,7 @@ Launch a new app with one Machine and an attached volume, and then clone the Mac
 
 1. [Confirm that the volume is attached to a Machine](#confirm-the-volume-is-attached-to-a-machine).
 
-1. (Recommended) Clone the first Machine to scale out to two Machines with volumes:
+1. (Recommended if your app handles replication) Clone the first Machine to scale out to two Machines with volumes:
 
     ```cmd
     fly machine clone <machine id>
@@ -66,6 +66,8 @@ Launch a new app with one Machine and an attached volume, and then clone the Mac
 
 ## Add volumes to an existing app
 
+Add a volume to an app created with [Fly Launch](/docs/apps/).
+
 1. Add a [`[mounts]` section](/docs/reference/configuration/#the-mounts-section) in the app's `fly.toml`, where `source` is the volume name and `destination` is the directory where the volume should be mounted on the Machine file system. For example:
 
     ```toml

reference/volumes.html.markerb

@@ -1,7 +1,7 @@
 ---
 title: Fly Volumes overview
 layout: docs
-nav: volumes
+nav: firecracker
 order: 20
 ---
 
@@ -24,8 +24,8 @@ If volumes don't work for your use case, then explore other options for data sto
 
 ## Volume redundancy
 
-<div class="warning">
-<b>Always run at least two volumes per app.</b> We usually recommend running at least two Machines per app to increase availability, and if you're using volumes, then each machine should have an attached volume. If you only have one Machine and volume, then you'll have downtime if there's a host or network failure, and whenever you deploy your app. Also remember that volumes don't have built-in replication between them.
+<div class="important icon">
+<b>Important: Always run at least two volumes per app.</b> We usually recommend running at least two Machines per app to increase availability, and if you're using volumes, then each machine should have an attached volume. If you only have one Machine and volume, then you'll have downtime if there's a host or network failure, and whenever you deploy your app. Also remember that volumes don't have built-in replication between them.
 </div>
 
 In a few cases, you can run a single Machine with an attached volume. For example, if you're running an app with a standard SQLite database, or your app is in development and you're not yet worried about downtime.

volumes/index.html.markerb

@@ -1,7 +1,7 @@
 ---
 title: "Fly Volumes"
 layout: docs
-nav: volumes
+nav: firecracker
 toc: false
 order: 10
 ---
@@ -22,7 +22,7 @@ Get things done with volumes.
 
 [Manage volume storage](/docs/apps/volume-manage/)
 
-More volume how-tos:
+Related how-tos:
 
 [Scale an app with volumes](/docs/apps/scale-count/#scale-an-app-with-volumes)