diff --git a/posts/distributed-press-social-inbox.md b/posts/distributed-press-social-inbox.md
index b916b79..6d277a1 100644
--- a/posts/distributed-press-social-inbox.md
+++ b/posts/distributed-press-social-inbox.md
@@ -13,7 +13,7 @@ At the core of this are the ActivityPub and ActivityStreams standards that dicta
 
 ## How does that work with P2P Publishing?
 
-Given how many people are already using these standards, they were very appealing as a target for websites and blogs published using Distributed Press. Thanks to a generous grant from the [Filecoin Foundation for the Decentralized Web](https://www.ffdweb.org/) we made it easier for folks publishing their websites via Distributed Press to receive comments and to make their posts available to anybody that's already on the federated web powered by ActivityPub (AKA The Fediverse).
+Given how many people are already using these standards, they were very appealing as a target for websites and blogs published using Distributed Press. Thanks to a our partnership with from the [Filecoin Foundation for the Decentralized Web](https://www.ffdweb.org/) we made it easier for folks publishing their websites via Distributed Press to receive comments and to make their posts available to anybody that's already on the federated web powered by ActivityPub (AKA The Fediverse).
 
 A key focus was to put as much "authority" into the published website and as little as possible into any sort of centralized server and what's cool is that ActivityPub is actually well set for this use case.
 Most of the data that servers access is representable as static JSON files, so our first goal was to create an example of a repository of static files published via Distributed Press that could be loaded from software such as Mastodon without needing any extra servers.