From bd07122f9245cb7c31f5e9443c581f36606863a8 Mon Sep 17 00:00:00 2001
From: Jason Knight <00jknight@gmail.com>
Date: Sun, 16 Feb 2025 12:54:34 -0600
Subject: [PATCH] Fix a typo (#1192)

---
 doc/site/embedding/calling-wren-from-c.markdown | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/site/embedding/calling-wren-from-c.markdown b/doc/site/embedding/calling-wren-from-c.markdown
index a780f48e..4b0cc7b4 100644
--- a/doc/site/embedding/calling-wren-from-c.markdown
+++ b/doc/site/embedding/calling-wren-from-c.markdown
@@ -48,9 +48,9 @@ method is called. That's how many dynamic languages work.
 
 But, as you can imagine, that's pretty slow. So, instead, Wren does as much of
 that work at compile time as it can. When it's compiling the above code to
-bytecode, it takes that method signature a converts it to a *method symbol*, a
-number that uniquely identifes that method. That's the only part of the process
-that requires treating a signature as a string.
+bytecode, it takes that method signature and converts it to a *method symbol*,
+a number that uniquely identifes that method. That's the only part of the
+process that requires treating a signature as a string.
 
 At runtime, the VM just looks for the method *symbol* in the receiver's class's
 method table. In fact, the way it's implemented today, the symbol is simply the