diff --git a/Jupyter_Pages/README.md b/Jupyter_Pages/README.md
index 03c69ce4e6ad4493649b906321bd2be4e93512cd..c5fffd7d878c8aa9b5284bb568fb13c7011f735f 100644
--- a/Jupyter_Pages/README.md
+++ b/Jupyter_Pages/README.md
@@ -7,9 +7,22 @@ To commit updates when running this from a station's Jupyter Notebook, do:
 
 If you cannot login as lofarsys, ask for your public key to be added to `~tangosys/.ssh/authorized_keys`. 
 
-Git commits require you to state your identity, as to know who did this commit:
+Git commits require you to state your identity, as to know who did this commit. Do this manually each session:
 
-    git add <notebook>.ipynb # add file to commit list
-    GIT_AUTHOR_NAME="Your Name" GIT_AUTHOR_EMAIL="you@astron.nl" git commit -m "i added this very cool notebook update"
+    export GIT_AUTHOR_NAME="Your Name"
+    export GIT_AUTHOR_EMAIL="you@astron.nl"
+    export GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME"
+    export GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
 
-If you don't do this, ``git`` will tempt you to configure the name and email permanently. Doing so means all checkins from this system will be done under your name, however.
+    # add file(s) to commit list
+    git add <notebook>.ipynb
+
+    # do the commit
+    git commit -m "i added this very cool notebook update"
+
+    # push it to the server
+    git push
+
+If you don't provide your name and e-mail, ``git`` will tempt you to configure the name and email permanently. Doing so means all checkins from this system will be done under your name, however.
+
+To make the above easier, you could put the ``export`` commands in a personal ``myname.sh`` file which you then run in your shell using ``source myname.sh`` before running ``git commit``.