diff --git a/doc/admin-guide-cloud/section_multi_backend.xml b/doc/admin-guide-cloud/section_multi_backend.xml
index be91ffac38..7b98675348 100644
--- a/doc/admin-guide-cloud/section_multi_backend.xml
+++ b/doc/admin-guide-cloud/section_multi_backend.xml
@@ -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