diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2015-02-15 18:22:32 +0530 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2015-02-15 18:22:32 +0530 |
| commit | d014548d5a90500d285686a8a70c2598bf2fd554 (patch) | |
| tree | 0f70dde599a0c92e04a6677811651b7c336ba5d0 /src | |
| parent | e6ad3848c63f4ab38e804b99296ad1b71924dcdf (diff) | |
| parent | 9c686dc54dfdad4e517d601fa25270fe0ecd2772 (diff) | |
| download | rust-d014548d5a90500d285686a8a70c2598bf2fd554.tar.gz rust-d014548d5a90500d285686a8a70c2598bf2fd554.zip | |
Rollup merge of #22248 - duaneedwards:patch-1, r=Gankro
Diffstat (limited to 'src')
| -rw-r--r-- | src/doc/intro.md | 2 |
1 files changed, 1 insertions, 1 deletions
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: |