Tried to link "too directly." fixed.

[wiki.git] / doc / RootInstance

diff --git a/doc/RootInstance b/doc/RootInstance
index a999e227401d410ac0860e698404a12b093a0386..d7a64a6d95cfd700a4e022e6d2e332f896c022fe 100644 (file)
--- a/doc/RootInstance
+++ b/doc/RootInstance
@@ -31,8 +31,8 @@ These aliases are also careful to get shorter lifetime tickets that are marked n
 
 === Extra instances ===
 
 
 === Extra instances ===
 

-Another thing you might want are extra instance tickets. Some people use these as another set of root tickets, with slightly lower security. But a common use is something _less_ secure than your null instance. For example, if you're writing a zephyrbot to run on scripts.mit.edu or something, the zephyrbot will need Kerberos tickets to subscribe to classes. But you don't want to leave your Kerberos password in a file in your locker, so you can leave your extra instance's password instead.
+Another thing you might want is an ''extra instance''. Some people use these just like another root instance, with slightly lower security. But a common use is something _less_ secure than your null instance. For example, if you're writing a zephyrbot to run on a shared server like scripts.mit.edu, the zephyrbot will need Kerberos tickets to subscribe to zephyrs. But you don't want to leave your Kerberos password in a file in your locker, so you can leave your extra instance's password instead.

 
 === Getting them ===
 
 
 === Getting them ===
 

-You need to show up in person to IS&T User Accounts in N42 with a photo ID to receive alternate tickets. For the reasons mentioned above, being in control of your null instance and sending a zephyr or authenticated e-mail with it does not mean that you can go ahead and make changes to your root instance too, While you're there, be sure to ask for a pts id, if you want to use your tickets with AFS.
\ No newline at end of file
+You need to show up in person to IS&T User Accounts in N42 with a photo ID to obtain new Kerberos identities. For the reasons described above, being in control of your null instance and sending a zephyr or authenticated e-mail with it does not mean that you can go ahead and make changes to your root or extra instance too.  While you're there, be sure to ask for a pts id, if you want to use your tickets with AFS.