Rename to MoChi

docs/architecture.dot

@@ -1,36 +0,0 @@
-digraph G {
-  subgraph cluster_0 {
-    label = "chihaya";
-    style = "line";
-    color = "blue";
-
-    "Storage";
-
-    subgraph cluster_1 {
-      label = "frontend";
-      style = "line";
-      color = "hotpink";
-
-      "Parser";
-      "Writer";
-    }
-
-    subgraph cluster_2 {
-      label = "logic";
-      style = "line";
-      color = "purple";
-
-      "PreHook Middleware";
-      "PostHook Middleware";
-      "Response Generator";
-    }
-  }
-
-  "BitTorrent Client" -> "Parser";
-  "Parser" -> "PreHook Middleware";
-  "PreHook Middleware" -> "Response Generator";
-  "PostHook Middleware" -> "Storage";
-  "Storage" -> "Response Generator";
-  "Response Generator" -> "Writer";
-  "Writer" -> "BitTorrent Client";
-}

docs/architecture.md

@@ -11,6 +11,3 @@ the configured implementation of the _Storage_ interface. PostHooks are asynchro
 has been delivered to the client. Because they are unnecessary to for generating a response, updates to the Storage for
 a particular request are done asynchronously in a PostHook.
 
-### Diagram
-
-![](https://user-images.githubusercontent.com/343539/52676700-05c45c80-2ef9-11e9-9887-8366008b4e7e.png)

docs/middleware/interval_variation.md

@@ -27,7 +27,7 @@ This middleware provides the following parameters for configuration:
 An example config might look like this:
 
 ```yaml
-chihaya:
+mochi:
   prehooks:
     - name: interval variation
       config:

docs/storage/redis.md

@@ -16,7 +16,7 @@ When one instance of Chihaya is down, other instances can continue serving peers
 ## Configuration
 
 ```yaml
-chihaya:
+mochi:
   storage:
     name: redis
     config: