From e12676304540fa9e160bf4cc28b954574f9ff944 Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@golang.org>
Date: Wed, 21 Nov 2012 14:40:50 -0800
Subject: [PATCH] spec: be clearer about the scope of a package name

We have the notion of a PackageName, not package identifier.
As is, it could construed that imports that rename a package
don't have an "imported package identifier" but a local one.

R=r, rsc, iant, ken, dsymonds
CC=golang-dev
https://golang.org/cl/6858049
---
 doc/go_spec.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/go_spec.html b/doc/go_spec.html
index 73b65f5311b..6115fae67b8 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Version of November 17, 2012",
+	"Subtitle": "Version of November 21, 2012",
 	"Path": "/ref/spec"
 }-->
 
@@ -1529,7 +1529,7 @@ Go is lexically scoped using blocks:
 	    or function (but not method) declared at top level (outside any
 	    function) is the package block.</li>
 
-	<li>The scope of an imported package identifier is the file block
+	<li>The scope of the package name of an imported package is the file block
 	    of the file containing the import declaration.</li>
 
 	<li>The scope of an identifier denoting a function parameter or