diff --git a/data-propagation.md b/data-propagation.md
index d2a80a910..f36aabba6 100644
--- a/data-propagation.md
+++ b/data-propagation.md
@@ -31,10 +31,10 @@ Every `BlockMsg` received must be validated [through the syntactical check](./va
 
 ## Message Propagation
 
-Messages are propagated over the libp2p pubsub channel `/fil/messages`. On this channel, every [serialised `Message`](data-structures.md#messages) ist announced.
+Messages are propagated over the libp2p pubsub channel `/fil/messages`. On this channel, every [serialised `Message`](data-structures.md#messages) is announced.
 
 Upon receiving the message, its validity must be checked: the signature must be valid, and the account in question must have enough funds to cover the actions specified. If the message is not valid it should be dropped and must not be forwarded.
 
 {{% notice todo %}}
 discuss checking signatures and account balances, some tricky bits that need consideration. Does the fund check cause improper dropping? E.g. I have a message sending funds then use the newly constructed account to send funds, as long as the previous wasn't executed the second will be considered "invalid" ... though it won't be at the time of execution.
-{{% /notice %}}
\ No newline at end of file
+{{% /notice %}}