/* ANL - Modified to allow Configurable Authentication Paths.
* This modification removes the restriction on the choice of realm
* names, i.e. they nolonger have to be hierarchical. This
- * is allowed by RFC 1510: "If a hierarchical orginization is not used
+ * is allowed by RFC 1510: "If a hierarchical organization is not used
* it may be necessary to consult some database in order to construct
* an authentication path between realms." The database is contained
* in the [capaths] section of the krb5.conf file.
* entries if the same krb5.conf is used for clients and servers)
*
* for example: ESnet will be running a KDC which will share
- * inter-realm keys with its many orginizations which include among
- * other ANL, NERSC and PNL. Each of these orginizations wants to
+ * inter-realm keys with its many organizations which include among
+ * other ANL, NERSC and PNL. Each of these organizations wants to
* use its DNS name in the realm, ANL.GOV. In addition ANL wants
* to authenticatite to HAL.COM via a K5.MOON and K5.JUPITER
* A [capaths] section of the krb5.conf file for the ANL.GOV clients
*
* This version of the Configurable Authentication Path modification
* differs from the previous versions prior to K5 beta 5 in that
- * the profile routines are used, and the explicite path from
- * client's realm to server's realm must be given. The modifications
- * will work together.
+ * the profile routines are used, and the explicit path from client's
+ * realm to server's realm must be given. The modifications will work
+ * together.
* DEE - 5/23/95
*/