Commit 70c95d1d authored by Robert Ricci's avatar Robert Ricci

Another spellcheck pass

parent c87f48fc
......@@ -97,7 +97,7 @@ then you already have an account at @(tb).
@instructionstep["Authorize CloudLab to use your GENI account"
#:screenshot "tutorial/authorize.png"]{
@margin-note{What's happening in this step is that your browser
uses your GENI user ceritificate (which it obtained from the GENI
uses your GENI user certificate (which it obtained from the GENI
portal) to cryptographically sign a
@link["http://groups.geni.net/geni/wiki/GAPI_AM_API_DRAFT/SpeaksFor"]{``speaks-for'' credential }
that authorizes the @(tb) portal to make
......@@ -140,11 +140,11 @@ the facility, but running on resources that are dedicated to you, which you
have complete control over. This profile uses local disk space on the nodes, so
anything you store there will be lost when the experiment terminates.
@margin-note{The OpenStack clould we will build in this tutorial is very small, but @(tb)
@margin-note{The OpenStack cloud we will build in this tutorial is very small, but @(tb)
has @seclink["hardware"]{large clusters} that can be used for larger-scale
experiments.}
For this tutorial, we wil use a basic profile that brings up a small OpenStack
For this tutorial, we will use a basic profile that brings up a small OpenStack
cloud. The @(tb) staff have built this profile by capturing
@seclink["disk-images"]{disk images} of a partially-completed OpenStack installation
and scripting the remainder of the install (customizing it for the specific
......@@ -194,7 +194,7 @@ information about how they work.
@(tb) will take a few minutes to bring up your copy of OpenStack, as
many things happen at this stage, including selecting suitable
hardware, loading disk images on local storage, booting bare-metal
machines, reconfiguring the network topology, etc. While this is
machines, re-configuring the network topology, etc. While this is
happening, you will see this status page:
@screenshot["tutorial/status-waiting.png"]
......@@ -314,7 +314,7 @@ enabling you to do rich scripting that is fully aware of both the requested
topology and assigned resources.
@margin-note{Most of the information displayed on the @(tb) status page comes
directly from this manifest; it is parsed and layed out in-browser.}
directly from this manifest; it is parsed and laid out in-browser.}
@screenshot["tutorial/experiment-manifest.png"]
......@@ -361,7 +361,7 @@ Two things of note:
@(tb) provides serial console access for all nodes, which can be used
in the event that normal IP or @(ssh) access gets intentionally or
untintentionally broken. Like the browser-based shell, it is launched through
unintentionally broken. Like the browser-based shell, it is launched through
the access menu, and the same caveats listed above apply as well. In addition:
@itemlist[
......@@ -585,7 +585,7 @@ You can define a new network for instances in your cloud to connect to:
@instructionstep["Enable DHCP"
#:screenshot "tutorial/os-network-dhcp.png"]{
On the final screen, make sure DHPC is enabled, and click the
On the final screen, make sure DHCP is enabled, and click the
``Create'' button.
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment