diff --git a/src/_blog/2023-ipfs-companion-MV3-update.md b/src/_blog/2023-ipfs-companion-MV3-update.md
index 887a3e3a..5485da41 100644
--- a/src/_blog/2023-ipfs-companion-MV3-update.md
+++ b/src/_blog/2023-ipfs-companion-MV3-update.md
@@ -76,7 +76,7 @@ MV3 changes went live towards the end of September when the collector-branch was
 
 ## What's next?
 
-The next step will be to implement the [new Brave APIs](https://github.com/ipfs/ipfs-companion/issues/1281) which allows for finer control of the IPFS node provided in the Brave Browser. This will provide a much polished experience for the users of Brave Browser. There are also plans to implement a [Helia based gateway](https://github.com/ipfs/ipfs-companion/issues/1284) on which some progress has already been made as proof-of-concepts in [helia-service-worker-gateway](https://github.com/ipfs-shipyard/helia-service-worker-gateway) and [helia-http-gateway](https://github.com/ipfs/helia-http-gateway). The learnings from these projects will be used to implement a gateway that can be used by IPFS-Companion to host an IPFS node in the browser, which will allow users to access IPFS resources when not running a local node.
+The next step will be to implement the [new Brave APIs](https://github.com/ipfs/ipfs-companion/issues/1281) to allow for finer control of the IPFS node provided in the Brave Browser. This will provide a much polished experience for the users of Brave Browser that also want to enable IPFS Companion extension for additional UI and more file-grained control over redirects. There also are plans to experiment with a [Helia based built-in gateway](https://github.com/ipfs/ipfs-companion/issues/1284) on which some progress has already been made as proof-of-concepts in [helia-service-worker-gateway](https://github.com/ipfs-shipyard/helia-service-worker-gateway) and [helia-http-gateway](https://github.com/ipfs/helia-http-gateway). The learnings from these projects will be used to work with browser vendors to close API gaps and eventually implement a gateway that can be used by IPFS Companion to host an IPFS node in the browser extension itself, which will allow users to access IPFS resources when not running a local node.
 
 ## Conclusion