Commit 2448d764 authored by Robert Ricci's avatar Robert Ricci

Spellcheck

parent f3ea7992
......@@ -42,7 +42,7 @@ experiment and the hardware (physical or virtual) that the software needs to
run. By providing a hardware platform for running these profiles, Apt
essentially enables researchers to build their own testbed environments and
share them with others, without having to buy, build, or maintain the
underlying infastructure.
underlying infrastructure.
Apt is built on @hyperlink["http://www.emulab.net/"]{Emulab} and
@hyperlink["http://www.geni.net/"]{GENI} technologies. It is built and operated
......
......@@ -206,7 +206,7 @@ If you chose to make your profile publicly visible, it will show up in the main
your profiles so that you can share them with others, post them on your
website, publish them in papers, etc. The link can be found on the profile's
detail page, which is linked for your ``My Profiles'' page. If you chose to
make your profile accessable to anyone, the link will take the form
make your profile accessible to anyone, the link will take the form
@code[(apturl "p/<project-id>/<profile-id>")]. If you didn't make the profile
public, the URL will have the form @code[(apturl "/p/<UUID>")], where
@code{UUID} is a 128-bit number so that the URL is not guessable. You can still
......
......@@ -72,7 +72,7 @@ Start by pointing your browser at @url[(apturl)].
a small OpenStack installation with one master node and one compute
node. It provides a simple example of how complex software stacks can
be packaged up within @(tb). If you'd prefer to start from bare metal,
look for one of the profiles that installs a stock operating sytem on
look for one of the profiles that installs a stock operating system on
physical machines.}
}
......
......@@ -75,7 +75,7 @@
@url{@(apturl "/#availability")} for an up to date deployment schedule.}
While @(tb) is in its technology preview stage, it is running on a small
cluster at the Universtiy of Utah. The size and capabilities of this
cluster at the University of Utah. The size and capabilities of this
cluster are not meant to be indicative of the larger @(tb). A description
of the hardware that will eventually comprise @(tb) can be found at
@url[(@apturl "/hardware.php")]
......
......@@ -125,11 +125,11 @@ will develop interfaces to expose, explore, and export this information.
Today, switches in @(tb) are treated as infrastructure; that is, they
are under @(tb)'s control and, while we provide a high degree of
transparenccy, we do not let users control them directly. We plan to
transparency, we do not let users control them directly. We plan to
make at least some switches---in most cases, ToRs, and in others,
spine and/or core---directly accessible to users. This means that
users will have console access to the switches, and will be able to
reconfigure them and/or load diferent versions of firmware on them.
reconfigure them and/or load different versions of firmware on them.
(This will only be offered on switches that are only used by a single
experiment at a time.)
}
......@@ -139,7 +139,7 @@ will develop interfaces to expose, explore, and export this information.
All switches in @(tb) will be OpenFlow-capable. In the case of
exclusive-access @seclink["planned-bare-metal-switches"]{bare metal
switches}, users will get direct and complte OpenFlow access to the
switches}, users will get direct and complete OpenFlow access to the
switches. In the case of shared switches, we are investigating the use of
@hyperlink["http://globalnoc.iu.edu/sdn/fsfw.html"]{FlowSpace Firewall}
from the @hyperlink["http://globalnoc.iu.edu"]{GRNOC} and
......
......@@ -17,13 +17,13 @@ There are several caveats that go with this preview:
@item{It is @bold{not running on actual @(tb) hardware}, which has not yet
been brought up; see @url{@(apturl "/hardware.php")} for a description
of the eventual @(tb) hardware, and @url{@(apturl "/#availability")}
for a schedule for avaiability. See the @seclink["hardware"]{hardware
for a schedule for availability. See the @seclink["hardware"]{hardware
chapter} for a description of the cluster that it is running on today.}
@item{It allows only @bold{very small} clouds to be built. This technology
preview is not intended for full-scale experimentation.}
@item{We have only built a @bold{single cloud-specifc
@item{We have only built a @bold{single cloud-specific
@seclink["profiles"]{profile}} so far, a small installation of
OpenStack. Experimentation on @(tb) is
@italic{not} limited to OpenStack, nor to this profile; it is merely
......
......@@ -12,7 +12,7 @@
useful and want to start using it for ``real work,'' you should
@seclink["register"]{sign up for a (free) account}, because a guest account
(1) won't let you hold your experiments for very long and (2) only allows
you to use @seclink["virtual-machines"]{virutal machines}, which are not
you to use @seclink["virtual-machines"]{virtual machines}, which are not
ideal for @seclink["repeatable-research"]{reproducing results}, since they
don't have strong performance isolation from other users.
......
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