diff --git a/guide/getting-started.html b/guide/getting-started.html
index 5b7117c..2618636 100644
--- a/guide/getting-started.html
+++ b/guide/getting-started.html
@@ -171,7 +171,9 @@ Here's an example for the client credentials grant, used in machine-to-machi
     // to replace the default OpenIddict entities.
     options.UseOpenIddict();
 });
-</code></pre><p>-&gt; [!WARNING]
+</code></pre></li>
+</ul>
+<p>-&gt; [!WARNING]
 -&gt; Important: if you change the default entity primary key (e.g. to <code>int</code> or <code>Guid</code> instead of <code>string</code>), make sure you use the <code>options.ReplaceDefaultEntities&lt;TKey&gt;()</code>
 -&gt; core extension accepting a <code>TKey</code> generic argument and use the generic <code>options.UseOpenIddict&lt;TKey&gt;()</code> overload to configure EF Core to use the specified type:
 -&gt;
@@ -193,7 +195,7 @@ Here&#39;s an example for the client credentials grant, used in machine-to-machi
 -&gt;        options.UseOpenIddict&lt;Guid&gt;();
 -&gt;    });
 -&gt;</code></p>
-</li>
+<ul>
 <li><p><strong>Create your own authorization controller:</strong>
 Implementing a custom authorization controller is required to allow OpenIddict to create tokens based on the identities and claims you provide.
 Here&#39;s an example for the client credentials grant:</p>
diff --git a/manifest.json b/manifest.json
index 7e26c7a..0cdd8b1 100644
--- a/manifest.json
+++ b/manifest.json
@@ -45,7 +45,7 @@
       "output": {
         ".html": {
           "relative_path": "guide/getting-started.html",
-          "hash": "x2y3JmMShZP8OKbVIkktGw=="
+          "hash": "PAK5Gf5at4cqxIPy5Io9pg=="
         }
       },
       "is_incremental": false,