Must. Stop. Tweaking.

emulab-transition.scrbl

@@ -3,8 +3,6 @@
 
 @title[#:tag "emulab-transition" #:version apt-version]{Transitioning from the ``Classic'' Interface to the ``Portal''}
 
-@(under-construction)
-
 The new Emulab portal interface is a custom version of the
 @hyperlink["http://cloudlab.us"]{CloudLab} interface, so if you are familiar
 with that interface, using the Emulab portal will be easy!
@@ -29,7 +27,7 @@ Besides a much updated look and feel, the portal interface offers significant
 new features and improvements to existing features.
 
 @subsection{Profiles}
-One significant change that is more than just an interface issue,
+One important change that is more than just an interface issue,
 is the clear delineation between an experiment's @italic{description}
 and its @italic{instantiation}. 
 
@@ -54,7 +52,7 @@ for details.
 In addition, the Emulab portal provides its own method for
 @seclink["emulab-conversion"]{converting classic experiments to profiles}.
 
-A profile's representation of an experiment is different from that of
+The profile representation of an experiment is different from that of
 the classic experiment.
 In the classic interface, experiments are described using @tt{ns-2},
 a network simulator scripting language based on TCL.
@@ -74,8 +72,8 @@ These fields support @seclink["markdown"]{Markdown} formatting allowing more
 expressive text.
 Classic experiments allow only a short, ASCII-only description.
 
-Profile can also have @italic{parameters} with descriptions and default
-values. This permits customized instantiations using a single profile.
+Profiles can also have @italic{parameters} with descriptions and default
+values. This permits customized instantiations from a single profile.
 For example, you can
 have parameters to specify the number or types of nodes in an experiment.
 In classic experiments this customization is accomplished by setting TCL
@@ -103,8 +101,9 @@ and view activity graphs.
 Custom disk images are now created by taking a @italic{snapshot} of an
 experiment node or @italic{cloning} an existing experiment to create
 a new profile.
-The disk image format has not changed, but the way in which images are
-named in an experiment description is different.
+The disk image format has not changed---the same images are used for
+classic or portal experiments---but the way in which images are
+named in a profile is different.
 Images are now identified by URNs.
 For example, you would use
 @tt{urn:publicid:IDN+emulab.net+image+emulab-ops//FBSD103-64-STD}
@@ -145,15 +144,20 @@ for more information.
 @subsection{Resource Reservations}
 
 A major new feature supported via the portal interface is the ability to
-automatically reserve node resources for a future time.
+automatically reserve node resources at a future time.
 Emulab has traditionally been a first-come-first-serve, best-effort facility
 and reserving nodes required prior arrangement with Emulab staff.
+Through the portal, you can now ensure that a given number of nodes of a
+specific type will be available during a future time window.
 See the section on @seclink["reservations"]{reservations} for details.
 
 @section[#:tag "emulab-missing-features"]{Classic Features Not Currently Supported in the Portal}
 
-A number of less frequently used features of Emulab and not supported via
-the portal interface:
+@(under-construction)
+
+A number of Emulab features are not currently supported via the portal
+interface.
+These include:
 
 @itemlist[
 @item{Events.}
@@ -167,8 +171,10 @@ the portal interface:
 @section[#:tag "emulab-conversion"]{Converting an Emulab experiment to a Profile}
 
 @bold{Note:} if you have no classic Emulab experiments (swapped in or swapped out)
-then you can skip this section. The following assumes you have an existing
-experiment created via the classic interface.
+then you can skip this section and return to the
+@seclink["getting-started"]{getting started} section.
+The following assumes you have an existing experiment created via the classic
+interface.
 
 When you login to the new portal interface at @url[(apturl)], you will be
 taken to your @italic{dashboard} on which there are a number of tabs.