Auto-fixed docs

zhangxiaoyu-zidif · Jul 10, 2015 · 581e4f7 · 581e4f7
1 parent ce319d4
commit 581e4f7
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/developer-guides/vagrant.md b/developer-guides/vagrant.md
@@ -9,7 +9,7 @@ Running kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/deve
    2. [VMWare Fusion](https://www.vmware.com/products/fusion/) version 5 or greater as well as the appropriate [Vagrant VMWare Fusion provider](https://www.vagrantup.com/vmware)
    3. [VMWare Workstation](https://www.vmware.com/products/workstation/) version 9 or greater as well as the [Vagrant VMWare Workstation provider](https://www.vagrantup.com/vmware)
    4. [Parallels Desktop](https://www.parallels.com/products/desktop/) version 9 or greater as well as the [Vagrant Parallels provider](https://parallels.github.io/vagrant-parallels/)
-3. Get or build a [binary release](/docs/getting-started-guides/binary_release.md)
+3. Get or build a [binary release](../../../docs/getting-started-guides/binary_release.md)
 
 ### Setup
 
@@ -244,7 +244,7 @@ my-nginx    nginx             run=my-nginx   3
 ```
 
 We did not start any services, hence there are none listed. But we see three replicas displayed properly.
-Check the [guestbook](/examples/guestbook/README.md) application to learn how to create a service.
+Check the [guestbook](../../../examples/guestbook/README.md) application to learn how to create a service.
 You can already play with scaling the replicas with:
 
 ```sh

diff --git a/releasing.md b/releasing.md
@@ -97,7 +97,7 @@ others around it will either have `v0.4-dev` or `v0.5-dev`.
 
 The diagram below illustrates it.
 
-![Diagram of git commits involved in the release](./releasing.png)
+![Diagram of git commits involved in the release](releasing.png)
 
 After working on `v0.4-dev` and merging PR 99 we decide it is time to release
 `v0.5`. So we start a new branch, create one commit to update

diff --git a/scheduler.md b/scheduler.md
@@ -37,7 +37,7 @@ can be overridden by passing the command-line flag `--policy-config-file` to the
 file specifying which scheduling policies to use. See
 [examples/scheduler-policy-config.json](../../examples/scheduler-policy-config.json) for an example
 config file. (Note that the config file format is versioned; the API is defined in
-[plugin/pkg/scheduler/api/](../../plugin/pkg/scheduler/api/)).
+[plugin/pkg/scheduler/api](../../plugin/pkg/scheduler/api/)).
 Thus to add a new scheduling policy, you should modify predicates.go or priorities.go,
 and either register the policy in `defaultPredicates()` or `defaultPriorities()`, or use a policy config file.