Comment updates

getlantern · Nov 25, 2014 · 4c3c85b · 4c3c85b
1 parent 54aca1e
commit 4c3c85b
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 10 deletions.
diff --git a/README.md b/README.md
@@ -1,11 +1,11 @@
 serveme [![Travis CI Status](https://travis-ci.org/getlantern/serveme.svg?branch=master)](https://travis-ci.org/getlantern/serveme)&nbsp;[![Coverage Status](https://coveralls.io/repos/getlantern/serveme/badge.png)](https://coveralls.io/r/getlantern/serveme)&nbsp;[![GoDoc](https://godoc.org/github.com/getlantern/serveme?status.png)](http://godoc.org/github.com/getlantern/serveme)
 ==========
 ```golang
-// package serveme implements a dial function and a net.Listener that allow
-// a client and server to communicate by having the server contact the client
-// rather than the other way around. This is handy in situations where the
-// client is reachable using an IP and port, but the server isn't (for example
-// if the server is behind an impenetrable NAT).
+// package serveme implements a Dialer and a net.Listener that allow a client
+// and server to communicate by having the server contact the client rather than
+// the other way around. This is handy in situations where the client is
+// reachable using an IP and port, but the server isn't (for example if the
+// server is behind an impenetrable NAT).
 //
 // For this to work, the client and server must be able to communicate with each
 // other via a signaling channel. When the client wants to connect to the

diff --git a/serveme.go b/serveme.go
@@ -1,8 +1,8 @@
-// package serveme implements a dial function and a net.Listener that allow
-// a client and server to communicate by having the server contact the client
-// rather than the other way around. This is handy in situations where the
-// client is reachable using an IP and port, but the server isn't (for example
-// if the server is behind an impenetrable NAT).
+// package serveme implements a Dialer and a net.Listener that allow a client
+// and server to communicate by having the server contact the client rather than
+// the other way around. This is handy in situations where the client is
+// reachable using an IP and port, but the server isn't (for example if the
+// server is behind an impenetrable NAT).
 //
 // For this to work, the client and server must be able to communicate with each
 // other via a signaling channel. When the client wants to connect to the