openstack/api-site
Code Issues Proposed changes

Change the wording from destroy to delete

Browse Source 
Change-Id: I9a818170e902986436733f103526644ace705572
This commit is contained in:
venkatamahesh 2015-11-15 15:58:16 +05:30
parent 884d8b2acb
commit 734ca6d0e3
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
firstapp/source/block_storage.rst
View File

@ -231,12 +231,12 @@ Extras
~~~~~~
You can detach the volume and reattach it elsewhere, or use the following
steps to destroy the volume.
steps to delete the volume.
.. warning::
The following operations are destructive and result in data loss.
To detach and destroy a volume:
To detach and delete a volume:
.. only:: libcloud

6
firstapp/source/getting_started.rst
View File

@ -33,7 +33,7 @@ robust, application.
The second application is an OpenStack application that enables you to:
* Create and destroy compute resources. These resources are virtual
* Create and delete compute resources. These resources are virtual
machine instances where the Fractals application runs.
* Make cloud-related architecture decisions such as turning
functions into micro-services and modularizing them.
@ -1008,7 +1008,7 @@ section.
Deploy the application to a new instance
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now that you know how to create and destroy instances, you can deploy the
Now that you know how to create and delete instances, you can deploy the
sample application. The instance that you create for the application is
similar to the first instance that you created, but this time, we'll briefly
introduce a few extra concepts.
@ -1018,7 +1018,7 @@ introduce a few extra concepts.
When you create an instance for the application, you'll want to give it a bit
more information than you supplied to the bare instance that you just created
and destroyed. We'll go into more detail in later sections, but for now,
and deleted. We'll go into more detail in later sections, but for now,
simply create the following resources so that you can feed them to the
instance:

4
firstapp/source/scaling_out.rst
View File

@ -33,7 +33,7 @@ that this feature can bring, as compared to traditional
infrastructure.
Of course, just having access to additional resources is only part of
the battle; while it's certainly possible to manually add or destroy
the battle; while it's certainly possible to manually add or delete
resources, you'll get more value -- and more responsiveness -- if the
application simply requests new resources automatically when it needs
them.
@ -382,7 +382,7 @@ redundant web services. If one dies, the others can be used.
corresponding Floating IPs. Replace FRACTAL_UUID the UUID
of an existing fractal.
Go ahead and test the fault tolerance. Start destroying workers and API
Go ahead and test the fault tolerance. Start deleting workers and API
instances. As long as you have one of each, your application should
be fine. There is one weak point though. The database contains the
fractals and fractal metadata. If you lose that instance, the