---

yaml
---
r: 12820
b: refs/heads/master
c: 5cd6bb1
h: refs/heads/master
v: v3

Author: nikomatsakis

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 7512284a94b3c06a8c27466aa0d142b7b27f5a8b
+refs/heads/master: 5cd6bb1ed34f759ae7222684967668e185b0e12c
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 4a81779abd786ff22d71434c6d9a5917ea4cdfff
 refs/heads/try: 2898dcc5d97da9427ac367542382b6239d9c0bbf

trunk/src/libcore/core.rc

@@ -13,11 +13,11 @@ built-in types and runtime services, or that is used in nearly every
 non-trivial program.
 
 `core` includes modules corresponding to each of the integer types, each of
-the floating point types, the `bool` type, tuples, characters, strings, vectors
-(`vec`), shared boxes (`box`), and unsafe pointers (`ptr`).  Additionally,
-`core` provides very commonly used built-in types and operations, concurrency
-primitives, platform abstractions, I/O, and complete bindings to the C
-standard library.
+the floating point types, the `bool` type, tuples, characters, strings,
+vectors (`vec`), shared boxes (`box`), and unsafe pointers (`ptr`).
+Additionally, `core` provides very commonly used built-in types and
+operations, concurrency primitives, platform abstractions, I/O, and complete
+bindings to the C standard library.
 
 `core` is linked by default to all crates and the contents imported.
 Implicitly, all crates behave as if they included the following prologue: