Deployed 0eaebc6 with MkDocs version: 1.6.1

api_and_sdks/api/index.html

@@ -2242,7 +2242,7 @@ <h1 id="api">API</h1>
 </ul>
 <p>The Philter <a href="../sdks/">SDKs</a> provide convenient methods for using Philter's API methods for various programming languages.</p>
 <h2 id="securing-philters-api">Securing Philter's API</h2>
-<p>Philter's API supports one-way and two-way SSL/TLS authentication. See the <a href="../../settings/">settings</a> for more information.</p>
+<p>Philter's API supports one-way and two-way SSL/TLS authentication. See Philter's <a href="../../settings/">Settings</a> for more information.</p>
 
 
 

other_features/consistent_anonymization/index.html

@@ -2240,7 +2240,7 @@ <h2 id="consistent-anonymization_1">Consistent Anonymization</h2>
 <p>Consistent anonymization refers to the process of always anonymizing the same sensitive information with the same replacement values. For example, if the name "John Smith" is randomly replaced with "Pete Baker", all other occurrences of "John Smith" will also be replaced by "Pete Baker."</p>
 <p>Consistent anonymization can be done on the document level or on the context level. When enabled on the document level, "John Smith" will only be replaced by "Pete Baker" in the same document. If "John Smith" occurs in a separate document it will be anonymized with a different random name. When enabled on the context level, "John Smith" will be replaced by "Pete Baker" whenever "John Smith" is found in all documents in the same context.</p>
 <p>Enabling consistent anonymization on the context level requires a cache to store the sensitive information and the corresponding replacement values. If a single instance of Philter is running, its internal cache service (enabled by default) is the best choice and no additional configuration is required.</p>
-<p>If multiple instances of Philter are deployed together, Philter requires access to a Redis cache service as shown below. See Philter' <a href="../../settings/">Settings</a> on how to configure the cache.</p>
+<p>If multiple instances of Philter are deployed together, Philter requires access to a Redis cache service as shown below. See Philter's <a href="../../settings/">Settings</a> on how to configure the cache.</p>
 <p><strong>When Philter is deployed in a cluster, a Redis cache is required to enable consistent anonymization.</strong></p>
 <p>The anonymization cache will contain PHI. It is important that you take the necessary precautions to secure the cache and all communication to and from the cache.</p>
 

policies/filters/common_filters/iban-codes/index.html

@@ -2409,7 +2409,7 @@ <h3 id="filter-strategies">Filter Strategies</h3>
 </tr>
 <tr>
 <td><code>FPE_ENCRYPT_REPLACE</code></td>
-<td>Replace the sensitive text with a value generated by <a href="filter-strategies.md#fpe">format-preserving encryption</a> (FPE)</td>
+<td>Replace the sensitive text with a value generated by <a href="../../../filter_strategies/">format-preserving encryption</a> (FPE)</td>
 </tr>
 <tr>
 <td><code>LAST_4</code></td>