Update 03.share_app.md

docs/03.share_app.md

@@ -45,30 +45,30 @@ be able to see your app.
 
 Before your collaborator can run a job with your app, they must also have
 correct permissions on the app execution system. If you built your app to use
-one of the public execution systems (e.g. `hpc-tacc-maverick`), then no more
+one of the public execution systems (e.g. `hpc-tacc-wrangler`), then no more
 changes should be necessary. If you built your app to use a private execution
-system (e.g. `hpc-tacc-maverick-username`), then you must also grant your
+system (e.g. `hpc-tacc-wrangler-username`), then you must also grant your
 collaborator the correct permissions on that system.
 
 *Tip: The app execution system is listed in the `app.json` file, or can be found
 by issuing: '`apps-list -v --filter executionSystem app-name`'.*
 
 [Elsewhere in this user guide](03.old_create_app.md) we deployed our private
-app on our private exection system, `hpc-tacc-maverick-username`. Use the
+app on our private exection system, `hpc-tacc-wrangler-username`. Use the
 `systems-roles-list` command to see who can access it:
 ```
-% systems-roles-list hpc-tacc-maverick-username
+% systems-roles-list hpc-tacc-wrangler-username
 sd2eadm OWNER
 username ADMIN
 ```
 
 Grant your collaborator `USER` access with the following:
 ```
-% systems-roles-addupdate -u my_collaborator -r USER hpc-tacc-maverick-username
-Successfully updated roles for user my_collaborator on hpc-tacc-maverick-username
+% systems-roles-addupdate -u my_collaborator -r USER hpc-tacc-wrangler-username
+Successfully updated roles for user my_collaborator on hpc-tacc-wrangler-username
 
 # list permissions again
-% systems-roles-list hpc-tacc-maverick-username
+% systems-roles-list hpc-tacc-wrangler-username
 sd2eadm OWNER
 username ADMIN
 my_collaborator USER