Various issues with riak-admin changes and search files fixed (#235)

* Fixes broken links as a result of riak-admin/riak admin changes

Fixes broken links as a result of riak-admin/riak admin changes

* leveled_ko/so context

leveled_ko/so context, closes #234

* Removes errant search files

Pesky search references that got missed previously have been eliminated. This fixes  #225

Author: JMercerGit

content/riak/kv/3.0.1/configuring/basic.md

@@ -18,7 +18,7 @@ aliases:
 
 [config reference]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
 [use running cluster]: {{<baseurl>}}riak/kv/3.0.1/using/running-a-cluster
-[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#member-status
+[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#member-status
 [perf erlang]: {{<baseurl>}}riak/kv/3.0.1/using/performance/erlang
 [plan start]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/start
 [plan best practices]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/best-practices

content/riak/kv/3.0.1/configuring/strong-consistency.md

@@ -24,7 +24,7 @@ aliases:
 [glossary vnode]: {{<baseurl>}}riak/kv/3.0.1/learn/glossary/#vnode
 [concept buckets]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/buckets
 [cluster ops bucket types]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/bucket-types
-[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#ensemble-status
+[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#ensemble-status
 [use admin riak admin]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin
 [config reference#advanced]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/#advanced-configuration
 [plan cluster capacity]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/cluster-capacity

content/riak/kv/3.0.1/learn/dynamo.md

@@ -1120,7 +1120,7 @@ addressed, however, by the refined partitioning scheme described in Section 6.2.
 > Riak KV operators can trigger node management via the
 > [riak admin command-line tool].
 
-[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/
+[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/
 
 In Amazon’s environment node outages (due to failures and maintenance tasks) are
 often transient but may last for extended intervals. A node outage rarely

content/riak/kv/3.0.1/setup/downgrade.md

@@ -19,7 +19,7 @@ aliases:
 [rolling upgrade]: {{<baseurl>}}riak/kv/3.0.1/setup/upgrading/cluster
 [config ref]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
 [concept aae]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/active-anti-entropy/
-[aae status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#aae-status
+[aae status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#aae-status
 
 Downgrades of Riak KV are tested and supported for two feature release versions, with the general procedure being similar to that of a [rolling upgrade][rolling upgrade].
 

content/riak/kv/3.0.1/setup/planning/cluster-capacity.md

@@ -20,7 +20,7 @@ aliases:
 [plan bitcask capacity]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/bitcask-capacity-calc
 [plan index]: {{<baseurl>}}riak/kv/3.0.1/setup/planning
 [concept replication]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/replication
-[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster
+[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster
 [config reference]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
 [perf benchmark]: {{<baseurl>}}riak/kv/3.0.1/using/performance/benchmarking
 [LVM]: http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)

content/riak/kv/3.0.1/using/admin.md

@@ -18,7 +18,7 @@ aliases:
 
 [use admin commands]: ./commands/
 [use admin riak cli]: ./riak-cli/
-[use admin riak admin]: ./riak admin/
+[use admin riak admin]: ./riak-admin/
 [use admin riak control]: ./riak-control/
 
 ## In This Section

content/riak/kv/3.0.1/using/admin/commands.md

@@ -16,11 +16,11 @@ aliases:
 
 ---
 
-[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster
+[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster
 [concept clusters]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/clusters
 [cluster ops add remove node]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/adding-removing-nodes
-[use admin riak admin#cluster-plan]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-plan
-[use admin riak admin#cluster-commit]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-commit
+[use admin riak admin#cluster-plan]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-plan
+[use admin riak admin#cluster-commit]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-commit
 
 This document explains usage of the [`riak admin cluster`][use admin riak admin#cluster] interface, which enables you to perform a wide
 variety of cluster-level actions.

content/riak/kv/3.0.1/using/admin/riak-admin.md

@@ -36,7 +36,7 @@ aliases:
 [repair recover index]: {{<baseurl>}}riak/kv/3.0.1/using/repair-recovery
 [cluster ops strong consistency]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/strong-consistency
 [cluster ops handoff]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/handoff
-[use admin riak admin#stats]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#stats
+[use admin riak admin#stats]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#stats
 
 ## `riak admin`
 

content/riak/kv/3.0.1/using/admin/riak-cli.md

@@ -18,7 +18,7 @@ aliases:
 
 [configuration file]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/
 [escript]: http://www.erlang.org/doc/man/escript.html
-[`riak admin`]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#top
+[`riak admin`]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#top
 [configuration]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/
 
 ## riak

content/riak/kv/3.0.1/using/cluster-operations/backing-up.md

@@ -126,7 +126,7 @@ Strong consistency | `/opt/riak/data/ensembles`
 ## Performing Backups
 
 {{% note title="Deprecation notice" %}}
-In previous versions of Riak KV, there was a [`riak admin backup`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#backup) command commonly used for
+In previous versions of Riak KV, there was a [`riak admin backup`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#backup) command commonly used for
 backups. This functionality is now deprecated. We strongly recommend using the backup procedure documented below instead.
 {{% /note %}}
 
@@ -190,11 +190,11 @@ node that the restored backup was taken from, you will need to
 additionally:
 
 1. Mark the original instance down in the cluster using
-   [`riak admin down <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#down)
+   [`riak admin down <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#down)
 2. Join the restored node to the cluster using
-   [`riak admin cluster join <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-join)
+   [`riak admin cluster join <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-join)
 3. Replace the original instance with the renamed instance with
-   [`riak admin cluster force-replace <node1> <node2>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-force-replace)
+   [`riak admin cluster force-replace <node1> <node2>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-force-replace)
 4. Plan the changes to the cluster with `riak admin cluster plan`
 5. Finally, commit the cluster changes with `riak admin cluster commit`