diff --git a/docs/concepts/lifecycle.md b/docs/concepts/lifecycle.md
index 2abbcf05c..cc90ccced 100644
--- a/docs/concepts/lifecycle.md
+++ b/docs/concepts/lifecycle.md
@@ -22,7 +22,7 @@ For example, merkleizing a static web application into a UnixFS DAG looks like t
 
 ## 2. Providing
 
-Once the input data has been merkleized and addressed by a CID, the node announces itself as a provider of the CID(s) to the IPFS network, thereby creating a public mapping between the CID and the node. This is typically known as **providing**, other names for this step are **publishing** **advertising**. On routing systems with built-in expiration/TTL like the Amino DHT, this is also known as **reproviding** to emphasize the continuous nature of the process in which a node advertises provider records.
+Once the input data has been merkleized and addressed by a CID, the node announces itself as a provider of the CID(s) to the IPFS network, thereby creating a public mapping between the CID and the node. This is typically known as **providing**, other names for this step are **publishing** **advertising**. On routing systems with built-in expiration/TTL like the <VueCustomTooltip label="The standard Distributed Hash Table (DHT) used in the public IPFS network. It helps nodes locate content and peers without a central server by mapping content identifiers (CIDs) to the providers who have the data." underlined multiline is-medium>Amino DHT</VueCustomTooltip>, this is also known as **reproviding** to emphasize the continuous nature of the process in which a node advertises provider records.
 
 IPFS nodes announce CID(s) to either the [DHT](./dht.md) or the [IPNI](./ipni.md) — the two content routing systems supported by [IPFS Mainnet](./glossary.md#mainnet).