From 19a7e501beb1b4e985023d59273631d59e6ffb63 Mon Sep 17 00:00:00 2001
From: Chris Evich <cevich@redhat.com>
Date: Wed, 30 Nov 2022 09:42:25 -0500
Subject: [PATCH] Docs update

Signed-off-by: Chris Evich <cevich@redhat.com>
---
 README.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 896f3c5..db6a71a 100644
--- a/README.md
+++ b/README.md
@@ -37,17 +37,19 @@ once, prior to registering your runners:
 
 ```bash
 $ for VOLUME in pipglr-podman-root pipglr-config pipglr-podman-cache; do \
-    PUPVM="podman unshare podman volume mount $VOLUME"
-    podman volume create $VOLUME && \
-    podman unshare chown 1000:1000 $($PUPVM) && \
-    podman unshare chmod 02770 $($PUPVM) && \
-    podman unshare ls -land $($PUPVM) ; \
+    VOLPTH=$(podman unshare podman volume mount $VOLUME)
+    podman volume create $VOLUME; \
+    podman unshare chown -R 1000:1000 $VOLPTH && \
+    podman unshare chmod 02770 $VOLPTH && \
+    podman unshare ls -land $VOLPTH ; \
+    podman unshare podman volume unmount $VOLUME ; \
   done
 ```
 
 If you get `podman system service` startup permission-denied errors, or
 errors from gitlab-runner, unable to connect to the podman socket, this is
-likely the cause.  You can fix it after-the-fact using the same commands as above, just add a `-R` option to the `chown`/`chmod`, and additionally target `./*`.
+likely the cause.  You can fix it after-the-fact using the same commands
+above.  additionally target `./*`.
 
 #### Runner registration
 
@@ -107,7 +109,7 @@ sure to use the `podman unshare` command-wrapper to enter the usernamespace.
 For example, to display the config:
 
 ```bash
-$ podman unshare $(podman unshare podman volume mount pipglr-config)/config.toml
+$ podman unshare cat $(podman unshare podman volume mount pipglr-config)/config.toml
 ```
 
 #### Debugging