openstack/api-site
Code Issues Proposed changes

cleanup source doc files for api-site

Browse Source 
reproducable to reproducible
maintanance to maintenance
concerened to concerned
intrinsicly to intrinsically
specifed to specified
priniciples to principles
applicaiton to application
throughsome to through some
attibute to attribute

Change-Id: I664a7b7476fbeafcde514fa63f42524d91e0c56a
This commit is contained in:
Shilla Saebi 2015-05-28 18:48:02 -04:00
parent ccd0483415
commit 44136cbf5b
5 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
firstapp/source/advice.rst
View File

@ -31,7 +31,7 @@ health check.
Backups
~~~~~~~
Where instances store information that is not reproducable (such as a
Where instances store information that is not reproducible (such as a
database server, a file server, or even log files for an application),
it is important to back up this information as you would a normal
non-cloud server. It sounds simple, but just because it is 'in the

6
firstapp/source/durability.rst
View File

@ -41,7 +41,7 @@ replicating each object at least twice before returning 'write
success' to your API call. It will always work to ensure that there
are three copies of your objects (by default) at all times -
replicating them around the system in case of hardware failure,
maintanance, network outage or any other kind of breakage. This is
maintenance, network outage or any other kind of breakage. This is
very convenient for app creation - you can just dump objects into
object storage and not have to care about any of this additional work
to keep them safe.
@ -64,9 +64,9 @@ immediate attention if disks fail.
The Object Storage service manages many of these tasks that normally
would require the application owner to manage them, and presents a
scalable and durable API that you can use for the fractals app,
without having to be concerened with the low level details of how the
without having to be concerned with the low level details of how the
objects are stored and replicated, and growing the storage pool. In
fact, Object Storage handles replication intrinsicly, storing multiple
fact, Object Storage handles replication intrinsically, storing multiple
copies of each object and returning one of them on demand using the
API.

2
firstapp/source/getting_started.rst
View File

@ -288,7 +288,7 @@ how to upload images, see
Set the image and size variables to appropriate values for your cloud. We'll
use these variables in later sections.
First, tell the connection to get a specifed image by using the ID of the
First, tell the connection to get a specified image by using the ID of the
image that you picked in the previous section:
.. only:: fog

4
firstapp/source/introduction.rst
View File

@ -40,7 +40,7 @@ Cloud application architecture principles
Cloud applications typically share several design principles.
These principles influenced the design of the Fractals application.
.. todo:: Do you want to state the core design priniciples or assume
.. todo:: Do you want to state the core design principles or assume
the reader can follow below.
@ -183,7 +183,7 @@ How the Fractals application interacts with OpenStack
-----------------------------------------------------
.. todo:: Description of the components of OpenStack and how they
relate to the Fractals applicaiton and how it runs on the cloud.
relate to the Fractals application and how it runs on the cloud.
TF notes this is already covered in the guide, just split
across each section. Adding it here forces the
introduction of block storage, object storage, orchestration

4
firstapp/source/orchestration.rst
View File

@ -27,7 +27,7 @@ The OpenStack Orchestration API contains the following constructs:
Stacks are created from Templates, which contain Resources. Resources
are an abstraction in the HOT (Heat Orchestration Template) template language, which enables you to define different
cloud resources by setting the `type` attibute.
cloud resources by setting the `type` attribute.
For example, you might use the Orchestration API to create two compute
instances by creating a Stack and by passing a Template to the Orchestration API.
@ -41,7 +41,7 @@ compute instances, networking topology, and security policies.
.. note:: The Orchestration module isn't deployed by default in every cloud. If these commands don't work, it means the Orchestration API isn't available; ask your support team for assistance.
This section introduces the `HOT templating language <http://docs.openstack.org/developer/heat/template_guide/hot_guide.html>`_,
and takes you throughsome of the common calls you will make when working with OpenStack Orchestration.
and takes you through some of the common calls you will make when working with OpenStack Orchestration.
Unlike previous sections of this guide, in which you used your SDK to programmatically interact with
OpenStack, in this section you'll be using the Orchestration API directly through Template files,