Update documentation

Author: raethlein

README.md

@@ -280,7 +280,7 @@ You can then start the standard workspace for that user or create a new workspac
 Via the ssh access button (3), you can send the user a command to connect to the started workspace via ssh. For more information about the ssh-feature in the workspace, checkout [this documentation section](https://github.com/ml-tooling/ml-workspace#ssh-access). If you created a workspace for another user, it might be necessary to click access on the workspace and authorize once per user to be able to use the ssh-access button.
 A user can also access the UI via ssh-ing into the workspace, printing the API token via `echo $JUPYTERHUB_API_TOKEN`, and then accessing the url of the hub in the browser under `/user/<username>/<workspace-name>/tree?token=<jupyterhub-api-token>`. The `JUPYTERHUB_API_TOKEN` gives access to *all* named servers of a user, so use different users for different persons in this scenario.
 
-> ℹ️ _Do **not** create different workspaces with the same Hub user and give access to different persons. Via the `$JUPYTERHUB_API_TOKEN` you get access to **all** workspaces of a server. In other words, if you create multiple named workspaces for the user 'admin' and distribute it to different persons, they can access all named workspaces._
+> ℹ️ _Do **not** create different workspaces for the same Hub user and then give access to them to different persons. Via the `$JUPYTERHUB_API_TOKEN` you get access to **all** workspaces of a user. In other words, if you create multiple named workspaces for the user 'admin' and distribute it to different persons, they can access all named workspaces for the 'admin' user._
 
 <img width=100% alt="Picture of admin panel" src="https://github.com/ml-tooling/ml-hub/raw/master/docs/images/admin-panel.png">
 <img width=100% alt="Picture of admin panel" src="https://github.com/ml-tooling/ml-hub/raw/master/docs/images/create-workspace.png">