Fix README links

Author: brohitbrose

README.md

@@ -6,6 +6,6 @@ Swim is a completely integrated solution for building scalable, end-to-end strea
 
 - A **user interface** that uses Swim's streaming UI frameworks to visualize data from Swim servers in real-time
 
-Visit [server](https://github.com/swimos/swim-tutorial/blob/master/server) to learn how to stand up your data in a Swim server.
+Visit [server](https://github.com/swimos/tutorial/blob/master/server) to learn how to stand up your data in a Swim server.
 
-Then, visit [ui](https://github.com/swimos/swim-tutorial/blob/master/ui) to see this data like never before.
+Then, visit [ui](https://github.com/swimos/tutorial/blob/master/ui) to see this data like never before.

server/README.md

@@ -6,7 +6,7 @@ Swim unifies the traditionally disparate roles of database, message broker, job
 
 Swim implements a general purpose distributed object model. The "objects" in this model are **Web Agents**.
 
-[Creating a class](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L13) that extends `swim.api.agent.AbstractAgent` defines a *template* for Web Agents (though not a useful one until we add some [lanes](#lanes)).
+[Creating a class](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L13) that extends `swim.api.agent.AbstractAgent` defines a *template* for Web Agents (though not a useful one until we add some [lanes](#lanes)).
 
 Visit the [documentation](https://developer.swim.ai/concepts/agents/) for further details about Web Agents.
 
@@ -16,28 +16,28 @@ If Web Agents are objects, then **lanes** serve as the "fields" of those objects
 
 Continuing our analogy, *lane callback* functions serve as the "methods" of Web Agents.
 
-Each lane type defines a set of overridable (default no-op) lifecycle callbacks. For example, [sending a command message](#sending-data-do-swim) to any command lane will trigger its [`onCommand` callback](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L51-L54). On the other hand, [setting a value lane](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L53) will trigger its `willSet` callback, then update its value, then trigger its [`didSet` callback](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L40-L47).
+Each lane type defines a set of overridable (default no-op) lifecycle callbacks. For example, [sending a command message](#sending-data-do-swim) to any command lane will trigger its [`onCommand` callback](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L51-L54). On the other hand, [setting a value lane](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L53) will trigger its `willSet` callback, then update its value, then trigger its [`didSet` callback](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/UnitAgent.java#L40-L47).
 
 Visit the [documentation](https://developer.swim.ai/concepts/lanes/) for further details about lanes.
 
 ## Standing a Swim Server
 
 A Swim server is loaded with a **plane**, which provides the runtime for Web Agents and routes messages to the correct lanes.
 
-A plane must [declare an `AgentType` field](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L13-L14) for each Web Agent type.
+A plane must [declare an `AgentType` field](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L13-L14) for each Web Agent type.
 
-Use the `ServerLoader` utility class to [load a plane into a Swim server](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L18). Note that your module must [`provide` `swim.api.plane.Plane` with your custom plane class](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/module-info.java#L8).
+Use the `ServerLoader` utility class to [load a plane into a Swim server](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L18). Note that your module must [`provide` `swim.api.plane.Plane` with your custom plane class](http://github.com/swimos/tutorial/tree/master/server/src/main/java/module-info.java#L8).
 
 Visit the [documentation](https://developer.swim.ai/concepts) for further details about these concepts.
 
 ## Populating a Swim Server With Your Data
 
-Every Swim server can be written to and read from by external processes using the Swim API. The simplest way to utilize this API is to use a **Swim client** instance to [send commands to command lanes](http://github.com/swimos/swim-tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L40).
+Every Swim server can be written to and read from by external processes using the Swim API. The simplest way to utilize this API is to use a **Swim client** instance to [send commands to command lanes](http://github.com/swimos/tutorial/tree/master/server/src/main/java/swim/tutorial/TutorialPlane.java#L40).
 
 Visit the [documentation](https://developer.swim.ai/concepts) for further details about these concepts.
 
 ## Subscribing to Swim Server Data
 
-Swim client instances use Swim **links** to pull data from a Swim lanes. Like their corresponding lanes, links have overridable callback functions that can be used to [populate UIs](http://github.com/swimos/swim-tutorial/tree/master/ui/index.html#L111-L133).
+Swim client instances use Swim **links** to pull data from a Swim lanes. Like their corresponding lanes, links have overridable callback functions that can be used to [populate UIs](http://github.com/swimos/tutorial/tree/master/ui/index.html#L111-L133).
 
 Visit the [documentation](https://developer.swim.ai/concepts/links/) for further details about links.