diff --git a/docs/build/drink/index.md b/docs/build/drink/index.md
index a453f81..9e85328 100644
--- a/docs/build/drink/index.md
+++ b/docs/build/drink/index.md
@@ -41,7 +41,7 @@ Before DRink!, you could have used ink!'s native test framework to execute eithe
 
 This paradigm is a peculiar compromise between the two other strategies. We give up the node layer (including networking, block production etc.), but we still have a fully functional runtime with attached storage. In other words, we keep bare blockchain state in-memory, and we can interact with it directly however we want.
 
-This way, we gain full control over the runtime, sacrificing real simulation of the blockchain environment. However, usually, this is higly beneficial for the development process, as it allows for a much faster feedback loop, assisted with better insights into execution externalities.
+This way, we gain full control over the runtime, sacrificing real simulation of the blockchain environment. However, usually, this is highly beneficial for the development process, as it allows for a much faster feedback loop, assisted with better insights into execution externalities.
 
 ---