Update all repository links to point at sandstorm-io org.

doc/_includes/buttons.html

 <div style="float: right">
 <a class="github_link" style="color: #fff"
-href="https://github.com/kentonv/capnproto">Develop</a>
+href="https://github.com/sandstorm-io/capnproto">Develop</a>
 <a class="groups_link" style="color: #fff"
 href="https://groups.google.com/group/capnproto">Discuss</a>
 <a class="groups_link" style="color: #fff"

doc/_includes/header.html

@@ -24,7 +24,7 @@
         </div>
       </header>
       <a id="discuss_banner" href="https://groups.google.com/group/capnproto">Discuss on Groups</a>
-      <a id="forkme_banner" href="https://github.com/kentonv/capnproto">View on GitHub</a>
+      <a id="forkme_banner" href="https://github.com/sandstorm-io/capnproto">View on GitHub</a>
     </div>
 
     {% if site.is_next %}

doc/cxxrpc.md

@@ -16,7 +16,7 @@ not yet implemented.
 
 ## Sample Code
 
-The [Calculator example](https://github.com/kentonv/capnproto/tree/master/c++/samples) implements
+The [Calculator example](https://github.com/sandstorm-io/capnproto/tree/master/c++/samples) implements
 a fully-functional Cap'n Proto client and server.
 
 ## KJ Concurrency Framework
@@ -374,7 +374,7 @@ Note that for the connect address, Cap'n Proto supports DNS host names as well a
 addresses.  Additionally, a Unix domain socket can be specified as `unix:` followed by a path name.
 
 For a more complete example, see the
-[calculator client sample](https://github.com/kentonv/capnproto/tree/master/c++/samples/calculator-client.c++).
+[calculator client sample](https://github.com/sandstorm-io/capnproto/tree/master/c++/samples/calculator-client.c++).
 
 ### Starting a server
 
@@ -416,7 +416,7 @@ IPv6 interfaces.  Additionally, a Unix domain socket can be specified as `unix:`
 path name.
 
 For a more complete example, see the
-[calculator server sample](https://github.com/kentonv/capnproto/tree/master/c++/samples/calculator-server.c++).
+[calculator server sample](https://github.com/sandstorm-io/capnproto/tree/master/c++/samples/calculator-server.c++).
 
 ## Debugging
 

doc/encoding.md

@@ -245,7 +245,7 @@ A capability pointer, then, simply contains an index into the separate capabilit
     C (32 bits) = Index of the capability in the message's capability
         table.
 
-In [rpc.capnp](https://github.com/kentonv/capnproto/blob/master/c++/src/capnp/rpc.capnp), the
+In [rpc.capnp](https://github.com/sandstorm-io/capnproto/blob/master/c++/src/capnp/rpc.capnp), the
 capability table is encoded as a list of `CapDescriptors`, appearing along-side the message content
 in the `Payload` struct.  However, some use cases may call for different approaches.  A message
 that is built and consumed within the same process need not encode the capability table at all

doc/install.md

@@ -100,7 +100,7 @@ If you download directly from Git, you will need to have the GNU autotools --
 installed (in addition to Git) in order to fetch the Google Test sources (done by
 `setup-autotools.sh`).
 
-    git clone https://github.com/kentonv/capnproto.git
+    git clone https://github.com/sandstorm-io/capnproto.git
     cd capnproto/c++
     ./setup-autotools.sh
     autoreconf -i

doc/otherlang.md

@@ -66,7 +66,7 @@ then hands the parse tree off to another binary -- known as a "plugin" -- which
 Plugins are independent executables (written in any language) which read a description of the
 schema from standard input and then generate the necessary code.  The description is itself a
 Cap'n Proto message, defined by
-[schema.capnp](https://github.com/kentonv/capnproto/blob/master/c%2B%2B/src/capnp/schema.capnp).
+[schema.capnp](https://github.com/sandstorm-io/capnproto/blob/master/c%2B%2B/src/capnp/schema.capnp).
 Specifically, the plugin receives a `CodeGeneratorRequest`, using
 [standard serialization](encoding.html#serialization-over-a-stream)
 (not packed).  (Note that installing the C++ runtime causes schema.capnp to be placed in
@@ -94,8 +94,8 @@ If the user specifies an output directory, the compiler will run the plugin with
 as the working directory, so you do not need to worry about this.
 
 For examples of plugins, take a look at
-[capnpc-capnp](https://github.com/kentonv/capnproto/blob/master/c%2B%2B/src/capnp/compiler/capnpc-capnp.c%2B%2B)
-or [capnpc-c++](https://github.com/kentonv/capnproto/blob/master/c%2B%2B/src/capnp/compiler/capnpc-c%2B%2B.c%2B%2B).
+[capnpc-capnp](https://github.com/sandstorm-io/capnproto/blob/master/c%2B%2B/src/capnp/compiler/capnpc-capnp.c%2B%2B)
+or [capnpc-c++](https://github.com/sandstorm-io/capnproto/blob/master/c%2B%2B/src/capnp/compiler/capnpc-c%2B%2B.c%2B%2B).
 
 ### Supporting Dynamic Languages
 

doc/rpc.md

@@ -142,7 +142,7 @@ performs as well as we can possibly hope for.
 
 #### Example code
 
-[The calculator example](https://github.com/kentonv/capnproto/blob/master/c++/samples/calculator-client.c++)
+[The calculator example](https://github.com/sandstorm-io/capnproto/blob/master/c++/samples/calculator-client.c++)
 uses promise pipelining.  Take a look at the client side in particular.
 
 ### Distributed Objects
@@ -244,7 +244,7 @@ stream protocol, it can easily be layered on top of SSL/TLS or other such protoc
 
 The Cap'n Proto RPC protocol is defined in terms of Cap'n Proto serialization schemas.  The
 documentation is inline.  See
-[rpc.capnp](https://github.com/kentonv/capnproto/blob/master/c++/src/capnp/rpc.capnp).
+[rpc.capnp](https://github.com/sandstorm-io/capnproto/blob/master/c++/src/capnp/rpc.capnp).
 
 Cap'n Proto's RPC protocol is based heavily on
 [CapTP](http://www.erights.org/elib/distrib/captp/index.html), the distributed capability protocol