From 26f8026a8ef2dc2914c12e85b536e1ae469e89c0 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Thu, 10 Aug 2017 11:29:39 +1000 Subject: content/contributor-workshop.article: fix a couple of typos One of them is a misformatting. Change-Id: I07fee028573865829c71f5124ec791cf286c65d2 Reviewed-on: https://go-review.googlesource.com/54510 Reviewed-by: Avelino Reviewed-by: Ian Lance Taylor --- content/contributor-workshop.article | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/contributor-workshop.article b/content/contributor-workshop.article index 92ca8e1..c0834ab 100644 --- a/content/contributor-workshop.article +++ b/content/contributor-workshop.article @@ -61,7 +61,7 @@ documentation. The [[https://blog.golang.org/survey2016-results][Go User survey] identified that our documentation was significantly lacking examples. In the presentation, we asked users to find a package they loved and to add an example. In the Go project, examples are written as code in Go files -(with specific naming) and the `go doc` tool displays them along side the documentation. +(with specific naming) and the `go`doc` tool displays them along side the documentation. This is a perfect first contribution as it's something that can be merged during a freeze, it's of critical importance to our users, and it's an addition that has a relatively narrow scope. @@ -150,7 +150,7 @@ score system. .image contributor-workshop/image7.png -Seeing your name pop up on the board and listening to everyone's excited was +Seeing your name pop up on the board and listening to everyone's excitement was intoxicating. It also invoked a sense of teamwork that lead to a feeling of inclusion and feeling like you were truly a part of the Go community. -- cgit v1.2.3