diff --git a/jams/index.md b/jams/index.md index 6435ab7a1b4d4f01739c22bfc91e55c6d65e7a46..872d942153e641b55862d2b9288cc44f8131b846 100644 --- a/jams/index.md +++ b/jams/index.md @@ -16,8 +16,8 @@ Downloadable JAMS manuals: ```{toctree} :maxdepth: 1 -client admin +client ``` ## Introduction @@ -86,7 +86,7 @@ In order to be completely secure, JAMS does not generate certificates for device JAMS instead issues certificates based on a certificate signing request sent to it by the device. This therefore removes the requirement to send a private key over the wire. -The diagram below shows the entire process of how a device enrolls with JAMS: +The following diagram shows the entire process of how a device enrolls with JAMS:  @@ -210,7 +210,7 @@ If the enterprise provides an LDAP directory for user management, it is required ") -The admin should provide most of the required information; however, below is a detailed overview of each field: +The admin should provide most of the required information; however, the following is a detailed overview of each field: <table> <thead> @@ -244,18 +244,20 @@ The admin should provide most of the required information; however, below is a d </tr> <tr> <td><strong>BaseDN</strong></td> -<td>The base realm where the user accounts are located; in most cases, it is `ou=users,dc=enterprise,dc=org`.</td> +<td>The base realm where the user accounts are located; in most cases, it is <code>ou=users,dc=enterprise,dc=org</code>.</td> </tr> </tbody> </table> +<br> + #### Option 2: Microsoft Active Directory (AD) If the enterprise provides Active Directory (AD) for user management, it is required to know its access information and an automated account that has read-only rights to do use look-ups. ") -The admin should provide most of the required information; however, below is a detailed overview of each field: +The admin should provide most of the required information; however, the following is a detailed overview of each field: <table> <thead>