From 31f6e6432485cfb880af0c8d98dc0cbdaec74383 Mon Sep 17 00:00:00 2001
From: Alex Crichton <alex@alexcrichton.com>
Date: Thu, 21 Mar 2013 15:57:33 -0400
Subject: [PATCH] doc: Remove mentions of oldmap::HashMap

---
 doc/rust.md     | 6 +++---
 doc/tutorial.md | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/rust.md b/doc/rust.md
index 3847b0b97558..287dcb950f77 100644
--- a/doc/rust.md
+++ b/doc/rust.md
@@ -441,11 +441,11 @@ expression context, the final namespace qualifier is omitted.
 Two examples of paths with type arguments:
 
 ~~~~
-# use std::oldmap;
+# use core::hashmap::linear::LinearMap;
 # fn f() {
 # fn id<T:Copy>(t: T) -> T { t }
-type t = oldmap::HashMap<int,~str>;  // Type arguments used in a type expression
-let x = id::<int>(10);           // Type arguments used in a call expression
+type t = LinearMap<int,~str>;  // Type arguments used in a type expression
+let x = id::<int>(10);         // Type arguments used in a call expression
 # }
 ~~~~
 
diff --git a/doc/tutorial.md b/doc/tutorial.md
index 30e230b67b0d..8c0f5f1ebdf6 100644
--- a/doc/tutorial.md
+++ b/doc/tutorial.md
@@ -1829,8 +1829,8 @@ illegal to copy and pass by value.
 Generic `type`, `struct`, and `enum` declarations follow the same pattern:
 
 ~~~~
-# use std::oldmap::HashMap;
-type Set<T> = HashMap<T, ()>;
+# use core::hashmap::linear::LinearMap;
+type Set<T> = LinearMap<T, ()>;
 
 struct Stack<T> {
     elements: ~[T]