Minor rewording on dApp IDs generation

Author: acenolaza

docs/oev-searchers/in-depth/data-feeds/index.md

@@ -189,11 +189,11 @@ hardcoded in the OEV proxies of the dApp.
 The ID has no meaning other than to group proxies of the same dApp together.
 
 Searchers can derive the dApp ID from the information provided in the
-[OEV dApps catalog](/oev-searchers/in-depth/#oev-dapps).
+[OEV dApps catalog](/oev-searchers/in-depth/#oev-dapps) in two ways.
 
 #### Programmatically
 
-Searchers can use [`unsafeComputeDappId`](https://github.com/api3dao/contracts/blob/52109d0d285d3ac485a2f0ed68bd7799e75a9722/src/proxy.ts#L57) from the `@api3/contracts` package.
+Searchers can use [unsafeComputeDappId](https://github.com/api3dao/contracts/blob/52109d0d285d3ac485a2f0ed68bd7799e75a9722/src/proxy.ts#L57) from the `@api3/contracts` package available as an NPM package.
 
 ::: info ℹ️ Example