diff --git a/jams/index.md b/jams/index.md
index be96b6838ef4d991cd4a12f855dd32d12a33524e..a5e20121e76aa88570dca0c281e71b28bdf03a1f 100644
--- a/jams/index.md
+++ b/jams/index.md
@@ -44,27 +44,27 @@ The source code is available at <https://git.jami.net/savoirfairelinux/jami-jams
 </thead>
 <tbody>
 <tr>
-<td>**Processor**</td>
+<td><strong>Processor</strong></td>
 <td>1 gigahertz (GHz) or faster with 1 or more cores on a compatible 64-bit processor or System on a Chip (SoC).</td>
 </tr>
 <tr>
-<td>**RAM**</td>
+<td><strong>RAM</strong></td>
 <td>4 gigabytes (GB).</td>
 </tr>
 <tr>
-<td>**Storage**</td>
+<td><strong>Storage</strong></td>
 <td>1 gigabyte (GB) of available storage space.</td>
 </tr>
 <tr>
-<td>**Operating system**</td>
+<td><strong>Operating system</strong></td>
 <td>GNU/Linux, Apple macOS, or Microsoft Windows.</td>
 </tr>
 <tr>
-<td>**Java**</td>
+<td><strong>Java</strong></td>
 <td>Version 11 or higher.</td>
 </tr>
 <tr>
-<td>**Database**</td>
+<td><strong>Database</strong></td>
 <td>LDAP-compatible directory (such as [OpenLDAP](https://www.openldap.org/)), Microsoft Active Directory (AD), or a local embedded database.</td>
 </tr>
 </tbody>
@@ -147,15 +147,15 @@ java -jar jams-launcher.jar PORT SSL_CERTIFICATE SSL_CERTIFICATE_KEY
 </thead>
 <tbody>
 <tr>
-<td>**PORT**</td>
+<td><strong>PORT</strong></td>
 <td>The TCP port on which JAMS is to listen for incoming connections.</td>
 </tr>
 <tr>
-<td>**SSL_CERTIFICATE**</td>
+<td><strong>SSL_CERTIFICATE</strong></td>
 <td>The location of the PEM-formatted SSL Certificate file.</td>
 </tr>
 <tr>
-<td>**SSL_CERTIFICATE_KEY**</td>
+<td><strong>SSL_CERTIFICATE_KEY</strong></td>
 <td>The location of the PEM-formatted key file, which is used with the SSL Certificate file from above.</td>
 </tr>
 </tbody>
@@ -221,27 +221,27 @@ The admin should provide most of the required information; however, below is a d
 </thead>
 <tbody>
 <tr>
-<td>**Use StartTLS**</td>
+<td><strong>Use StartTLS</strong></td>
 <td>The LDAP server can be configured to use either TLS/STARTTLS or PLAIN sockets; if STARTTLS is used, mark the value as true.</td>
 </tr>
 <tr>
-<td>**Server Address**</td>
+<td><strong>Server Address</strong></td>
 <td>The address of the server with respect to the JAMS server, the LDAP is not required to be publicly accessible but should be accessible to JAMS. Either `ldap://` or `ldaps://` should precede the address.</td>
 </tr>
 <tr>
-<td>**Port**</td>
+<td><strong>Port</strong></td>
 <td>The port on which the LDAP server is listening for requests (usually 389 for PLAIN/STARTTLS and 636 for SSL/TLS).</td>
 </tr>
 <tr>
-<td>**Administrator Username**</td>
-<td>This is **NOT** the LDAP's administration account credentials but the credentials of the account that has *read* permissions to the LDAP database in order to look up users. The format is generally `cn=bot,ou=robots,dc=domain,dc=org`.</td>
+<td><strong>Administrator Username</strong></td>
+<td>This is <strong>NOT</strong> the LDAP's administration account credentials but the credentials of the account that has *read* permissions to the LDAP database in order to look up users. The format is generally `cn=bot,ou=robots,dc=domain,dc=org`.</td>
 </tr>
 <tr>
-<td>**Password**</td>
+<td><strong>Password</strong></td>
 <td>The password used by the account above.</td>
 </tr>
 <tr>
-<td>**BaseDN**</td>
+<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>
 </tr>
 </tbody>
@@ -264,28 +264,28 @@ The admin should provide most of the required information; however, below is a d
 </thead>
 <tbody>
 <tr>
-<td>**Port**</td>
+<td><strong>Port</strong></td>
 <td>The port on which Active Directory (AD) is listening (generally it is either 389 or 636).</td>
 </tr>
 <tr>
-<td>**Host**</td>
+<td><strong>Host</strong></td>
 <td>The address of the server with respect to the JAMS server, the Active Directory (AD).
   It not required to be publicly accessible but should be accessible to JAMS.</td>
 </tr>
 <tr>
-<td>**Administrator Username**</td>
-<td>This is **NOT** the Active Directory's administration account credentials but the credentials of the account that has *read* permissions to the Active Directory database in order to look up users. The format is generally `cn=bot,ou=robots,dc=domain,dc=net`.</td>
+<td><strong>Administrator Username</strong></td>
+<td>This is <strong>NOT</strong> the Active Directory's administration account credentials but the credentials of the account that has *read* permissions to the Active Directory database in order to look up users. The format is generally `cn=bot,ou=robots,dc=domain,dc=net`.</td>
 </tr>
 <tr>
-<td>**Password**</td>
+<td><strong>Password</strong></td>
 <td>The password used by the account above.</td>
 </tr>
 <tr>
-<td>**Use SSL**</td>
+<td><strong>Use SSL</strong></td>
 <td>Whether the server uses SSL for data transmission.</td>
 </tr>
 <tr>
-<td>**Domain Name**</td>
+<td><strong>Domain Name</strong></td>
 <td>This is the legacy-formatted Windows Domain Name (i.e., `WINDOMAIN`).</td>
 </tr>
 </tbody>
@@ -318,19 +318,19 @@ Enable this option to allow JAMS users in the organization to also search for ex
 </thead>
 <tbody>
 <tr>
-<td>**CORS Domain Name**</td>
+<td><strong>CORS Domain Name</strong></td>
 <td>The domain on which the JAMS client and administration UI will be running.</td>
 </tr>
 <tr>
-<td>**Certificate Revocation List Lifetime**</td>
+<td><strong>Certificate Revocation List Lifetime</strong></td>
 <td>The frequency at which the CRL is updated in memory.</td>
 </tr>
 <tr>
-<td>**Device Lifetime**</td>
+<td><strong>Device Lifetime</strong></td>
 <td>How long a device's certificate is valid before being considered stale and requiring re-enrollment.</td>
 </tr>
 <tr>
-<td>**User Account Lifetime**</td>
+<td><strong>User Account Lifetime</strong></td>
 <td>How long a user account is valid before being considered stale and requiring re-enrollment.</td>
 </tr>
 </tbody>