From af9d82566c915b254a8d2e82717ad9d703b46a83 Mon Sep 17 00:00:00 2001
From: nailuj29gaming <54189157+nailuj29gaming@users.noreply.github.com>
Date: Thu, 9 Dec 2021 12:45:25 -0500
Subject: [PATCH] Fix the example mangling

---
 active-rfcs/0000-name-mangling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/active-rfcs/0000-name-mangling.md b/active-rfcs/0000-name-mangling.md
index 6e1040a..79fdc39 100644
--- a/active-rfcs/0000-name-mangling.md
+++ b/active-rfcs/0000-name-mangling.md
@@ -11,7 +11,7 @@ Defines how name mangling will work.
 
 ## Basic example
 
-A method of the class `foo` with the signature `method(data: int) -> string` in the module `bar.baz` would be mangled to `boad2m3barm3bazc3fooi6methodp2t3i32t3i32r5string`
+A method of the class `foo` with the signature `method(data: int) -> string` in the module `bar.baz` would be mangled to `boad2m3barm3bazc3fooi6methodp1t3i32r5string`
 ## Motivation
 
 Most languages "mangle" names of symbols, in order to allow for things like namespacing, overloading, and class/struct methods. This RFC defines how Boa can mangle names