fix: Reference base path (change category/api to reference/api) (#52)

Author: KillEdgier

docs/reference/api/_category_.json

@@ -0,0 +1,3 @@
+---
+title: "API"
+---

docs/reference/api/api.md

@@ -0,0 +1,3 @@
+---
+title: "CLI"
+---

docs/reference/cli/_category_.json

@@ -0,0 +1,3 @@
+---
+title: "Installation"
+---

docs/reference/cli/cli.md

@@ -0,0 +1,3 @@
+---
+title: "Examples"
+---

docs/reference/installation/_category_.json

@@ -3,10 +3,6 @@
   "position": 2,
   "link": {
     "type": "generated-index",
-    "description": "A Vela cluster is deployed as a self-hosted solution and consists of two core services, the server and the worker. The relationship between these services is considered many-to-many meaning many workers can connect to many servers.
-
-The server is considered the brains of the application while the worker is considered the brawn of the application.
-
-An optional third service, the UI, can also be deployed but is not required for the Vela platform to operate as intended. This service provides a means for utilizing and interacting with the Vela platform."
+    "description":  "An example of these tutorials exist in our go-vela/vela-tutorials repository. We recommend reviewing Docker's best practices before attempting to create a custom plugin. We recommend that all plugins be placed inside a scratch image."
   }
 }