From 9c686dc54dfdad4e517d601fa25270fe0ecd2772 Mon Sep 17 00:00:00 2001
From: Duane Edwards <mail@duaneedwards.net>
Date: Fri, 13 Feb 2015 08:45:52 +1000
Subject: [PATCH] Correct typo for 'underyling'

---
 src/doc/intro.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/doc/intro.md b/src/doc/intro.md
index 1e343b593df..90a018c2ddd 100644
--- a/src/doc/intro.md
+++ b/src/doc/intro.md
@@ -224,7 +224,7 @@ segfault when we allocate more memory?
 
 The answer is that in the C++ version, `x` is a *reference* to the memory
 location where the first element of the array is stored. But in Ruby, `x` is a
-standalone value, not connected to the underyling array at all. Let's dig into
+standalone value, not connected to the underlying array at all. Let's dig into
 the details for a moment. Your program has access to memory, provided to it by
 the operating system. Each location in memory has an address.  So when we make
 our vector, `v`, it's stored in a memory location somewhere: