Update instructions (#123)

Author: kgolubic

pages/help-center/errors/_meta.json

@@ -1,6 +1,6 @@
 {
   "auth": "Auth",
-  "durability": "durability",
+  "durability": "Durability",
   "memory": "Memory",
   "modules": "Modules",
   "overview": "Overview",

pages/help-center/errors/snapshots.mdx

@@ -34,31 +34,47 @@ start Memgraph again.
 
 ## Why is data lost when Memgraph is restarted?
 
-<Tabs items={['Docker 🐳', 'Linux']}> 
-  <Tab>
-    Docker containers don’t persist data by default (all changes are lost when the
-  container is stopped). You need to use local volumes to store the data
-  permanently which is why Memgraph is started with the `-v` flags:
-
-  ```console
-  docker run -p 7687:7687 -v mg_lib:/var/lib/memgraph memgraph/memgraph
-  ```
-
-  More information on Docker Volumes can be found
-  [here](https://docs.docker.com/storage/volumes/).
-  </Tab>  
-  <Tab>
-
-  Make sure that Memgraph is searching for the snapshot files in the right
-  directory. The Memgraph configuration is available in
-  `/etc/memgraph/memgraph.conf` and you can specify the directory with the
-  `--data-directory` flag. If the configuration file is altered, Memgraph needs to
-  be restarted. The default directory is `/var/lib/memgraph`. To learn about all
-  the configuration options, check out the [reference
-  guide](/configuration/configuration-settings).
-
-  </Tab>
-</Tabs>
+When you stop a Docker container, the data and state within that container are
+preserved until the container is explicitly removed. This means that any data or
+changes you've made within the container are retained and can be accessed again
+when the container is restarted. 
+
+To access this data, you need to ensure you're starting the same container
+instance that you used previously. Here's how you can do that:
+
+### Starting a Named Container
+
+If you had named your Memgraph container as "memgraph", for instance, you can
+easily restart it using the following command:
+
+```
+docker start memgraph
+```
+
+This command will bring the named container back to life, retaining all the data
+and changes you had made in it.
+
+### Starting an Unnamed Container
+
+If you didn't assign a specific name to your container when you created it,
+Docker would have given it a random name. To find and restart the correct
+container list all the containers on your system using the following command:
+
+```
+docker ps -a
+```
+
+From the list, identify the container you want to restart. Note down the
+container ID associated with it and use it to restart the container:
+
+```
+docker start [CONTAINER_ID]
+```
+
+Replace `[CONTAINER_ID]` with the actual ID you noted down. Once executed, your
+container will be up and running again, with all its data intact.
+
+---
 
 <Callout type="info">
 If you weren't able to find the error, please submit it through a <a href="https://support.memgraph.com"