go/types: correct misspelling in function doc

The indirectType function comment uses the phrase 'layed out'. In the
context of that phrase, where something is being placed or sprawled,
the word should be 'laid'. 'Layed' is a misspelling of 'laid'.

Change-Id: I05ecb97637276e2252c47e92a0bd678130714889
GitHub-Last-Rev: 6ee67371b42c12ceaf4c6c245319748008ac7e7b
GitHub-Pull-Request: golang/go#27444
Reviewed-on: https://go-review.googlesource.com/132779
Reviewed-by: Ian Lance Taylor <iant@golang.org>

diff --git a/src/go/types/typexpr.go b/src/go/types/typexpr.go
index 2edd1f5bac31e89e6ca7af0c82b8a6a5ecaeec4a..83848099c2c2fe341f86a117665ea9ea42960ac3 100644 (file)
--- a/src/go/types/typexpr.go
+++ b/src/go/types/typexpr.go
@@ -132,7 +132,7 @@ func (check *Checker) definedType(e ast.Expr, def *Named) (T Type) {
 
 // indirectType is like typ but it also breaks the (otherwise) infinite size of recursive
 // types by introducing an indirection. It should be called for components of types that
-// are not layed out in place in memory, such as pointer base types, slice or map element
+// are not laid out in place in memory, such as pointer base types, slice or map element
 // types, function parameter types, etc.
 func (check *Checker) indirectType(e ast.Expr) Type {
        check.push(indir)