aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Pike <r@golang.org>2012-03-22 19:20:03 +1100
committerRob Pike <r@golang.org>2012-03-22 19:20:03 +1100
commit2795a15c0c460fac9a760557a8c18d79a857faab (patch)
tree1cd06e60b53bd186baa319b9612f85b902234269
parent289a357104854d5f58102b05b40154c727657408 (diff)
downloadgo-2795a15c0c460fac9a760557a8c18d79a857faab.tar.gz
go-2795a15c0c460fac9a760557a8c18d79a857faab.zip
doc/articles/gobs_of_data.html: delete extra word
Putt putt putt our way towards felicity. R=golang-dev, bsiegert CC=golang-dev https://golang.org/cl/5874048
-rw-r--r--doc/articles/gobs_of_data.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/articles/gobs_of_data.html b/doc/articles/gobs_of_data.html
index a8670db45e..6b836b2c36 100644
--- a/doc/articles/gobs_of_data.html
+++ b/doc/articles/gobs_of_data.html
@@ -86,7 +86,7 @@ used to encode a protocol buffer, you might not be able to parse it.)
First, protocol buffers only work on the data type we call a struct in Go. You
can't encode an integer or array at the top level, only a struct with fields
inside it. That seems a pointless restriction, at least in Go. If all you want
-to send is an array of integers, why should you have to put put it into a
+to send is an array of integers, why should you have to put it into a
struct first?
</p>