From 9bc5d2638e688f598e3e14844b31fd710335893a Mon Sep 17 00:00:00 2001
From: Mosh <1306020+mishmosh@users.noreply.github.com>
Date: Wed, 26 Apr 2023 13:58:49 -0400
Subject: [PATCH] Update 2023-content-blocking-for-the-ipfs-stack.md

---
 src/_blog/2023-content-blocking-for-the-ipfs-stack.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/_blog/2023-content-blocking-for-the-ipfs-stack.md b/src/_blog/2023-content-blocking-for-the-ipfs-stack.md
index 5e10098f..560e0b05 100644
--- a/src/_blog/2023-content-blocking-for-the-ipfs-stack.md
+++ b/src/_blog/2023-content-blocking-for-the-ipfs-stack.md
@@ -13,7 +13,7 @@ tags:
   - 'content-moderation'
 ---
 
-Bifrost (the NetOps team responsible for the IPFS.io HTTP gateways) is happy to announce that content blocking can now be enabled in Kubo and other tools in the IPFS stack.
+Bifrost (the Protocol Labs NetOps team responsible for the IPFS.io HTTP gateways) is happy to announce that content blocking can now be enabled in Kubo and other tools in the IPFS stack.
 
 Traditionally, content blocking has been performed only at the IPFS gateway level and directly in Nginx, using the original [Badbits denylist](https://badbits.dwebops.pub/denylist.json). This had a few issues: content on the denylist was not blocked on Kubo and was still available via Bitswap. Additionally, blocking affected concrete CID strings, but not equivalent ones (i.e. those with a different base encoding).