Last-minute doc fixes.

doc/_posts/2014-12-15-capnproto-0.5-generics-msvc-java-csharp.md

@@ -11,7 +11,7 @@ Today we're releasing Cap'n Proto 0.5. We've added lots of goodies!
 Microsoft Visual Studio 2015 (currently in "preview") finally supports enough C++11 to get Cap'n
 Proto working, and we've duly added official support for it!
 
-Not all features are support yet. The core serialization functionality sufficient for 90% of users
+Not all features are supported yet. The core serialization functionality sufficient for 90% of users
 is available, but reflection and RPC APIs are not. We will turn on these APIs as soon as Visual C++
 is ready (the main blocker is incomplete `constexpr` support).
 
@@ -39,7 +39,7 @@ for Cap'n Proto:
 
 ### Generics
 
-Cap'n Proto now supports [generics](http://localhost:4000/capnproto/language.html#generic-types),
+Cap'n Proto now supports [generics]({{site.baseurl}}language.html#generic-types),
 in the sense of Java generics or C++ templates. While working on
 [Sandstorm.io](https://sandstorm.io) we frequently found that we wanted this, and it turned out
 to be easy to support.
@@ -60,8 +60,8 @@ wrap the C++ reflection API are likely to work too.
 ### Canonicalization
 
 0.5 introduces a (backwards-compatible) change in
-[the way struct lists should be encoded](http://localhost:4000/capnproto/encoding.html#lists), in
-order to support [canonicalization](http://localhost:4000/capnproto/encoding.html#canonicalization).
+[the way struct lists should be encoded]({{site.baseurl}}encoding.html#lists), in
+order to support [canonicalization]({{site.baseurl}}encoding.html#canonicalization).
 We believe this will make Cap'n Proto more appropriate for use in cryptographic protocols. If
 you've implemented Cap'n Proto in another language, please update your code!
 
@@ -77,7 +77,7 @@ new object references, and the recipient implicitly gains permission to use any
 they receive. Essentially, Sandstorm allows the interfaces between two apps, or between and app
 and the platform, to be designed using the same vocabulary as interfaces between objects or
 libraries in an object-oriented programming language (but
-[without the mistakes of CORBA or DCOM](http://localhost:4000/capnproto/rpc.html#distributed-objects)).
+[without the mistakes of CORBA or DCOM]({{site.baseurl}}rpc.html#distributed-objects)).
 Cap'n Proto RPC is at the core of this.
 
 This has powerful implications: Consider the case of service discovery. On Sandstorm, all

doc/encoding.md

@@ -168,7 +168,7 @@ struct list where each struct has 2 bytes in their "data" section (and an empty
 list of pointer values (C = 6) can be decoded as a struct list where each sturct has a pointer
 section with one pointer (and an empty data section). The purpose of this rule is to make it
 possible to upgrade a list of primitives to a list of structs, as described under the
-[protocol evolution rules](http://localhost:4000/capnproto/language.html#evolving-your-protocol).
+[protocol evolution rules](language.html#evolving-your-protocol).
 (We make a special exception that boolean lists cannot be upgraded in this way due to the
 unreasonable implementation burden.) Note that even though struct lists can be decoded from any
 element size (except C = 1), it is NOT permitted to encode a struct list using any type other than

doc/push-site.sh

@@ -3,6 +3,11 @@
 set -eu
 shopt -s extglob
 
+if grep 'localhost:4000' *.md _posts/*.md; then
+  echo "ERROR: Your content has links to localhost:4000!" >&2
+  exit 1
+fi
+
 if [ "x$(git status --porcelain)" != "x" ]; then
   echo -n "git repo has uncommited changes.  Continue anyway? (y/N) " >&2
   read -n 1 YESNO