From eb109a765d1ac7b99568b3185594cd8430de0684 Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@golang.org>
Date: Mon, 28 Dec 2009 14:40:42 -0800
Subject: [PATCH] Clarify section on tokens. Fixes #457.

R=r
CC=golang-dev
https://golang.org/cl/181083
---
 doc/go_spec.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/go_spec.html b/doc/go_spec.html
index ed740187b9..8a11e49f9d 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -151,12 +151,13 @@ Comments do not nest.
 
 <p>
 Tokens form the vocabulary of the Go language.
-There are four classes: identifiers, keywords, operators
-and delimiters, and literals.  <i>White space</i>, formed from
+There are four classes: <i>identifiers</i>, <i>keywords</i>, <i>operators
+and delimiters</i>, and <i>literals</i>.  <i>White space</i>, formed from
 spaces (U+0020), horizontal tabs (U+0009),
 carriage returns (U+000D), and newlines (U+000A),
 is ignored except as it separates tokens
-that would otherwise combine into a single token.
+that would otherwise combine into a single token. Also, a newline
+may trigger the insertion of a <a href="#Semicolons">semicolon</a>.
 While breaking the input into tokens,
 the next token is the longest sequence of characters that form a
 valid token.
-- 
2.50.0