fixes #34 Update warnings about release

CONTRIBUTING

@@ -22,7 +22,7 @@ If you're thinking of contributing, here's what you should know.
 
  # The remaining items below are consequences of the items above.
 
- 4. All code must pass go vet, and be go fmt compliant.
+ 4. All code must pass `go vet`, and be `go fmt` compliant.
 
  5. New features should have tests, and the existing tests must continue
     to pass.  We use the go test framework.
@@ -46,8 +46,8 @@ If you're thinking of contributing, here's what you should know.
     end of the AUTHORS file.  (Please do this, particularly for non-trivial
     changes!)
 
-10. Submit a github pull request.  Ideally just one bug per PR if possible,
-    and based upon the latest commit in the github master branch.
+10. Submit a GitHub pull request.  Ideally just one bug per PR if possible,
+    and based upon the latest commit in the GitHub master branch.
 
 11. We may rebase your changes, including squashing multiple commits,
     or ask you to do so, if you have not followed the procedure above, or

README.adoc

@@ -22,10 +22,9 @@ These are colloquially  known as a "`nanomsg`".
 a|image::mangos.jpg[float="right"]
 |===
 
-WARNING:  THIS IS A WORK-IN-PROGRESS AND NOT READY FOR GENERAL USE YET.
-This represents version 2 of _mangos_, and contains breaking changes and
-rather different API.  To use the the original version of _mangos_ please
-see https://github.com/nanomsg/mangos
+NOTE: This is version 2 of _mangos_, and contains breaking changes and
+rather different API in some circumstances relative to version 1.  To use the
+original version of _mangos_ please see https://github.com/nanomsg/mangos
 
 The modern C implemenation of the SP protocols is available as
 https://github.com/nanomsg/nng[__NNG™__].