diff --git a/docs/concepts/privacy-and-encryption.md b/docs/concepts/privacy-and-encryption.md
index d66586e5b..d169b93ce 100644
--- a/docs/concepts/privacy-and-encryption.md
+++ b/docs/concepts/privacy-and-encryption.md
@@ -35,7 +35,7 @@ The other half of the equation when considering the prospect of IPFS traffic mon
 While a long string of letters and numbers may not be a "Johnny Appleseed" level of human-readable specificity, your PeerID is still a long-lived, unique identifier for your node. Keep in mind that it's possible to do a DHT lookup on your PeerID and, particularly if your node is regularly running from the same location (like your home), find your IP address. (It's possible to [reset your PeerID](../reference/kubo/cli.md#ipfs-key-rotate) if necessary, but similarly to changing your user ID on legacy web apps and services, is likely to involve extra effort.) Additionally, longer-term monitoring of the public IPFS network could yield information about what CIDs your node is requesting and/or reproviding and when.
 
 
-### Encryption
+## Encryption
 
 There are two types of encryption in a network: _transport-encryption_ and _content-encryption_.
 
@@ -57,4 +57,4 @@ IPFS uses transport-encryption but not content encryption. This means that your
 - [Lit Protocol](https://litprotocol.com/)
 - [OrbitDB](https://github.com/orbitdb)
 - [Peergos](https://peergos.org/)
-- [Textile](https://www.textile.io/)
\ No newline at end of file
+- [Textile](https://www.textile.io/)