openstack/openstack-manuals
Code Issues Proposed changes

Changed sentence structure and grammar

Browse Source 
Capitalized word after period
Added created in vs. in which

Change-Id: If3e91a0dc291304acb895f17b52e083aa0f868a0
This commit is contained in:
Shilla 2013-12-02 11:27:59 -05:00
parent fd9d76d4bb
commit 1601177a4a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/admin-guide-cloud/section_multi_backend.xml
View File

@ -4,7 +4,7 @@
xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
<title>Configure a multiple-storage back-end</title>
<para>This section presents the multi back-end storage feature
introduced with the Grizzly release. multi back-end allows the
introduced with the Grizzly release. Multi back-end allows the
creation of several back-end storage solutions serving the
same OpenStack Compute configuration. Basically, multi
back-end launches one <systemitem class="service"
@ -12,8 +12,8 @@
<para>In a multi back-end configuration, each back-end has a name
(<literal>volume_backend_name</literal>). Several
back-ends can have the same name. In that case, the scheduler
properly decides in which back-end the volume has to be
created.</para>
properly decides which back-end the volume has to be
created in.</para>
<para>The name of the back-end is declared as an
extra-specification of a volume type (such as,
<literal>volume_backend_name=LVM_iSCSI</literal>). When a