docs: fix link and trim (oxia-db#319)

Signed-off-by: tison <[email protected]>

Author: tisonkun

README.md

@@ -2,37 +2,37 @@
 
 [![Build](https://github.com/streamnative/oxia/actions/workflows/pr_build_and_test.yaml/badge.svg)](https://github.com/streamnative/oxia/actions/workflows/pr_build_and_test.yaml)
 
-
 Oxia is a scalable metadata store and coordination system that can be used as the core infrastructure to build
 large scale distributed systems.
 
 ## Why Oxia?
 
- * Design optimized for Kubernetes environment
- * Transparent horizontal scalability
- * Linearizable per-key operations
- * Able to sustain millions of read/write per second
- * Able to store 100s of GBs
+* Design optimized for Kubernetes environment
+* Transparent horizontal scalability
+* Linearizable per-key operations
+* Able to sustain millions of read/write per second
+* Able to store 100s of GBs
 
 ## Features
 
- * Key-Value interface
- * Notification mechanism
- * Ephemeral records
- * Automated session management
+* Key-Value interface
+* Notification mechanism
+* Ephemeral records
+* Automated session management
 
 ## Documentation
- * [Design goals](docs/design-goals.md)
- * [Architecture](docs/architecture.md)
- * [Getting started with Oxia](docs/getting-started.md)
- * [Go client API](docs/go-api.md)
- * [Deploy using K8S operator](docs/ks8-operator.md)
- * Developer docs 
-   * [Replication protocol](docs/replication-protocol.md)
-     - [Coordinator](docs/replication-coordinator.md)
-     - [Storage](docs/replication-storage.md)
-   * [Verifying correctness](docs/correctness.md) 
-   * [Oxia's K8S resources](docs/kubernetes-oxia-cluster.md)
+
+* [Design goals](docs/design-goals.md)
+* [Architecture](docs/architecture.md)
+* [Getting started with Oxia](docs/getting-started.md)
+* [Go client API](docs/go-api.md)
+* [Deploy using K8S operator](docs/ks8-operator.md)
+* Developer docs 
+  * [Replication protocol](docs/replication-protocol.md)
+    * [Coordinator](docs/replication-coordinator.md)
+    * [Storage](docs/replication-storage.md)
+  * [Verifying correctness](docs/correctness.md) 
+  * [Oxia's K8S resources](docs/kubernetes-oxia-cluster.md)
 
 ## License
 

docs/ks8-operator.md

@@ -1,6 +1,4 @@
-
-# Deploying in Kubernetes with Oxia operator 
-
+# Deploying in Kubernetes with Oxia operator
 
 ## Monitoring Oxia
 
@@ -12,8 +10,8 @@ The Helm chart for the controller and the Oxia operator both use a `monitoringEn
 install the service monitor. If you don't have Prometheus installed and don't want to install it, you can set
 `monitoringEnabled: false` to skip this part.
 
-Grafana's dashboards are available at [../deploy/dashboards](). These can just be imported in your existing Grafana
-instance.
+Grafana's dashboards are available at [deploy/dashboards](/deploy/dashboards).
+These can just be imported in your existing Grafana instance.
 
 ### Deploying Prometheus Stack
 
@@ -33,7 +31,6 @@ $ helm repo update
 This installs the stock Prometheus & Grafana, without the Oxia dashboards, which you will be able to manually 
 import later.
 
-
 ```shell
 $ helm install monitoring prometheus-community/kube-prometheus-stack \
           --namespace monitoring \
@@ -82,9 +79,9 @@ $ helm upgrade --install oxia-controller \
 
 Now that the Oxia controller is running, we can create K8S resources of type `OxiaCluster`, by submitting a CRD.
 
-An example of CRD can be found at [example-oxia-cluster.yaml](../deploy/examples/example-oxia-cluster.yaml).
+An example of CRD can be found at [example-oxia-cluster.yaml](/deploy/examples/example-oxia-cluster.yaml).
 
-The full specification of the CRD is at [oxiaclusters.yaml](../deploy/crds/oxiaclusters.yaml).
+The full specification of the CRD is at [oxiaclusters.yaml](/deploy/crds/oxiaclusters.yaml).
 
 A minimal example of CRD is: