From 99dbb1d51f3f08d1cd94179687cbe69c3218ef87 Mon Sep 17 00:00:00 2001
From: Lindsey Kuper <lindsey@composition.al>
Date: Wed, 1 Jan 2014 23:00:06 -0500
Subject: [PATCH] Fix comment that's been wrong since ancient times (thanks,
 @jvns).

---
 src/librustc/middle/trans/base.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/librustc/middle/trans/base.rs b/src/librustc/middle/trans/base.rs
index 4f075c79dc879..ad95344031643 100644
--- a/src/librustc/middle/trans/base.rs
+++ b/src/librustc/middle/trans/base.rs
@@ -20,7 +20,7 @@
 //   * There's no way to find out the ty::t type of a ValueRef.  Doing so
 //     would be "trying to get the eggs out of an omelette" (credit:
 //     pcwalton).  You can, instead, find out its TypeRef by calling val_ty,
-//     but many TypeRefs correspond to one ty::t; for instance, tup(int, int,
+//     but one TypeRef corresponds to many `ty::t`s; for instance, tup(int, int,
 //     int) and rec(x=int, y=int, z=int) will have the same TypeRef.