Revert "Merge branch 'dev' of https://github.com/TI-Tokyo/riak-docs-fork into dev"

This reverts commit 130b136, reversing
changes made to 9ba3e81.

Author: JMercerGit

config.yaml

@@ -49,9 +49,8 @@ params:
   #        - ["<version>", "<version>", ...]
   #        - ["<version>", "<version>", ...]
   #      latest:        "<version>"             /* 5 */
-  #      lts:           ["<series>","<series>"] /* 6 */
-  #      archived_below:  "<version>"           /* 7 */
-  #      archived_url:  "<URI>"                 /* 8 */
+  #      lts:           "<series>"              /* 6 */
+  #      archived_url:  "<URI>"                 /* 7 */
   #
   # 1. The project descriptor must match some contents' `project:` front matter.
   #    This should be all lowercase with underscores for spaces---code, really.
@@ -79,14 +78,11 @@ params:
   # 5. `latest` is the current specific version that is currently att the head-
   #    of-development.  
   #    `latest` is required.
-  # 6. `lts` is the set of Release Series (ex; ["2.9"], or ["2.9","3.0"], ect.
-  #    -- it is expected to be the ["X.Y"] of a semantic "X.Y.Z" version string 
-  #    that is currently held as the Long Term Support series.  
+  # 6. `lts` is the Release Series (ex; "1.4", or "2.0", ect. -- it is expected
+  #    to be the "X.Y" of a semantic "X.Y.Z" version string) that is currently
+  #    held as the Long Term Support series.  
   #    `lts` is optional.
-  # 7. To make the versions menu smaller, set `archive_below` to a "X.Y" version
-  #    to place earlier versions under a collapsed "other" item.
-  #    `archive_below` is optional.
-  # 8. If the project was moved from the Middleman site to Hugo, the
+  # 7. If the project was moved from the Middleman site to Hugo, the
   #    `archived_url` is the URL to the newest of the deprecated pages.  
   #    `archived_url` is optional.
   project_descriptions:

content/riak/cs/2.0.0/cookbooks/configuration.md

@@ -16,8 +16,8 @@ aliases:
 In a Riak CS storage system, three components work in conjunction with one another, which means that you must configure each component to work with the others:
 
 * Riak --- The database system that acts as the backend storage
-* Riak CS --- The cloud storage layer over Riak which exposes the storage and billing APIs, storing files and metadata in Riak, and streaming them back to users
-* Stanchion --- Manages requests involving globally unique system entities, such as buckets and users sent to a Riak instance, for example, to create users or to create or delete buckets
+* Riak CS --- The cloud storage layer over Riak which exposes the storage and 
billing APIs, storing files and metadata in Riak, and streaming them back to 
users
+* Stanchion --- Manages requests involving globally unique system entities, such as 
buckets and users sent to a Riak instance, for example, to create users or to create or delete buckets
 
 In addition, you must also configure the S3 client you use to communicate with your Riak CS system.
 

content/riak/cs/2.1.2/index.md

@@ -11,6 +11,8 @@ project: "riak_cs"
 project_version: "2.1.2"
 aliases:
   - /riakcs/2.1.2/
+  - /riakcs/latest/
+  - /riak/cs/latest/
 ---
 
 Riak CS (Cloud Storage) is easy-to-use object storage software built on top of