Fix docs link to point at md files

argoproj · Oct 29, 2019 · 1486519 · 1486519
1 parent 53282a5
commit 1486519
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/features/index.md b/docs/features/index.md
@@ -2,8 +2,8 @@
 
 The Rollout object has two available strategies: Canary and BlueGreen. Below are the links to the documenation for each strategy:
 
-1. [Blue Green](/features/bluegreen/)
-1. [Canary](/features/canary/)
+1. [Blue Green](bluegreen.md)
+1. [Canary](canary.md)
 
 The following describes all the available fields of a rollout:
 
@@ -15,7 +15,7 @@ metadata:
 spec:
   # Number of desired pods. Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.
   replicas: 5
-  #Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this rollout. It must match the pod template's labels.
+  #Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this rollout. It must match the pod template's labels.`
   selector:
     matchLabels:
       app: guestbook

diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -90,4 +90,4 @@ $ kubectl patch rollout example-rollout --type merge -p '{"spec": {"paused": fal
 At this point, the Rollout has executed all the steps to transition to a new version. As a result, the new ReplicaSet is considered the new stable ReplicaSet, and the previous ReplicaSet will be scaled down. The Rollout will repeat this behavior if the Pod Spec Template is changed again.
 
 ## Going forward
-Check out the [feature documentation](/features/) for more configuration options for a rollout.
+Check out the [features page](features/index.md) for more configuration options for a rollout.