leftover mentions of `user-writable` group

use `users` instead

base-notebook/Dockerfile

@@ -46,8 +46,7 @@ ENV PATH=$CONDA_DIR/bin:$PATH \
 
 ADD fix-permissions /usr/local/bin/fix-permissions
 # Create jovyan user with UID=1000 and in the 'users' group
-# and the user-writable group, which owns all of the
-# files we want users to write (/home/jovyan, packages)
+# and make sure these dirs are writable by the `users` group.
 RUN useradd -m -s /bin/bash -N -u $NB_UID $NB_USER && \
     mkdir -p $CONDA_DIR && \
     chown $NB_USER:$NB_GID $CONDA_DIR && \

base-notebook/README.md

@@ -58,7 +58,7 @@ You may customize the execution of the Docker container and the command it is ru
 * `-e NB_GID=100` - Specify the gid of the `jovyan` user. Useful to mount host volumes with specific file ownership. For this option to take effect, you must run the container with `--user root`. (The `start-notebook.sh` script will `su jovyan` after adjusting the group id.)
 * `-e GRANT_SUDO=yes` - Gives the `jovyan` user passwordless `sudo` capability. Useful for installing OS packages. For this option to take effect, you must run the container with `--user root`. (The `start-notebook.sh` script will `su jovyan` after adding `jovyan` to sudoers.) **You should only enable `sudo` if you trust the user or if the container is running on an isolated host.**
 * `-v /some/host/folder/for/work:/home/jovyan/work` - Mounts a host machine directory as folder in the container. Useful when you want to preserve notebooks and other work even after the container is destroyed. **You must grant the within-container notebook user or group (`NB_UID` or `NB_GID`) write access to the host directory (e.g., `sudo chown 1000 /some/host/folder/for/work`).**
-* `--group-add user-writable` - use this argument if you are also specifying
+* `--group-add users` - use this argument if you are also specifying
   a specific user id to launch the container (`-u 5000`), rather than launching the container as root and relying on NB_UID and NB_GID to set the user and group.
 
 

base-notebook/fix-permissions

@@ -5,7 +5,7 @@
 # It will make everything in the directory owned by the group $NB_GID
 # and writable by that group.
 # Deployments that want to set a specific user id can preserve permissions
-# by adding the `--group-add user-writable` line to `docker run`.
+# by adding the `--group-add users` line to `docker run`.
 
 # uses find to avoid touching files that already have the right permissions,
 # which would cause massive image explosion