[cloudstack-documentation] branch volume-snap-policies-doc-update updated: typos fix

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

andrijapanic pushed a commit to branch volume-snap-policies-doc-update
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/volume-snap-policies-doc-update by this push:
     new 3a14095  typos fix
3a14095 is described below

commit 3a14095aa3de8f1c86cbae6fa3a136af41d1ecf5
Author: Andrija Panic <45...@users.noreply.github.com>
AuthorDate: Mon Aug 5 15:13:16 2019 +0200

    typos fix
---
 source/adminguide/storage.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 6fd2460..a391c74 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -652,12 +652,12 @@ both root disks and data disks are supported. However, CloudStack does
 not currently support booting a VM from a recovered root disk. A disk
 recovered from snapshot of a root disk is treated as a regular data
 disk; the data on recovered disk can be accessed by attaching the disk
-to a VM. Exception to this is when using KVM with NFS - with this setup,
+to a VM. An exception to this is when using KVM with NFS - with this setup,
 both root and data volumes can be restored to their previous state.
 
 A completed snapshot is copied from primary storage to secondary
 storage, where it is stored until deleted or purged by newer snapshot.
-The copy process can optionally be asynchronous (parameter asynbackupc=true)
+The copy process can optionally be asynchronous (parameter asyncbackup=true)
 meaning that API call will complete once the snapshot is created initially 
 on the Primary Storage, and after that the snapshot will be copied in the
 background to the Secondary Storage.