[lxc-devel] [lxd/master] doc/backup.md: update snap path

[simondeziel on Github]

A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 349 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20180417/2907b905/attachment.bin>
-------------- next part --------------
From 3786254da7cda441aa5b163189fb743a6455dc69 Mon Sep 17 00:00:00 2001
From: Simon Deziel <simon at sdeziel.info>
Date: Tue, 17 Apr 2018 16:22:39 -0400
Subject: [PATCH] doc/backup.md: update snap path

Signed-off-by: Simon Deziel <simon at sdeziel.info>
---
 doc/backup.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/backup.md b/doc/backup.md
index 91b122ee8..29664f30f 100644
--- a/doc/backup.md
+++ b/doc/backup.md
@@ -4,7 +4,7 @@ To backup a LXD instance different strategies are available.
 
 ## Full backup
 This requires that the whole `/var/lib/lxd` or
-`/var/lib/snap/lxd/common/lxd` (for the snap) folder be backuped up.
+`/var/snap/lxd/common/lxd` (for the snap) folder be backuped up.
 Additionally, it is necessary to backup all storage pools as well.
 
 In order to restore the LXD instance the old `lxd` folder needs to be
@@ -40,7 +40,7 @@ manually.
 
 The container must be available under
 `/var/lib/lxd/storage-pools/POOL-NAME/containers/NAME` or
-`/var/lib/snap/lxd/common/lxd/storage-pools/POOL-NAME/containers/NAME`
+`/var/snap/lxd/common/lxd/storage-pools/POOL-NAME/containers/NAME`
 in the case of the LXD snap.
 
 LXD will then locate the container and read its `backup.yaml` file,