docs: Fix markdown

Resolve issues in the markdown files in this repo.

Fixes #435.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
This commit is contained in:
James O. D. Hunt
2019-04-18 16:00:17 +01:00
parent f758083836
commit 63776a197a
3 changed files with 5 additions and 5 deletions

View File

@@ -15,7 +15,7 @@
- [Kata deploy](#kata-deploy)
- [Kata cleanup](#kata-cleanup)
[kata-deploy](kata-deploy) provides a Dockerfile, which contains all of the binaries
[kata-deploy](.) provides a Dockerfile, which contains all of the binaries
and artifacts required to run Kata Containers, as well as reference daemonsets, which can
be utilized to install Kata Containers for both Docker and on a running Kubernetes cluster.
@@ -128,7 +128,7 @@ kubectl delete -f kata-rbac.yaml
### Dockerfile
The [Dockerfile](kata-deploy/Dockerfile) used to create the container image deployed in the DaemonSet is provided here.
The [Dockerfile](Dockerfile) used to create the container image deployed in the DaemonSet is provided here.
This image contains all the necessary artifacts for running Kata Containers, all of which are pulled
from the [Kata Containers release page](https://github.com/kata-containers/runtime/releases).

View File

@@ -1,7 +1,7 @@
# How to do a Kata Containers Release
* [Introduction](#Introduction)
* [Requirements](#Requirements)
* [Introduction](#introduction)
* [Requirements](#requirements)
* [Release process](#release-process)
# Introduction

View File

@@ -70,7 +70,7 @@ The [miniOS image][2] is not included in the snap image as it is not possible fo
QEMU to open a guest RAM backing store on a read-only filesystem. Fortunately,
you can start Kata Containers with a Linux initial RAM disk (initrd) that is
included in the snap image. If you want to use the miniOS image instead of initrd,
then a new configuration file can be [created](#configuring-kata-containers)
then a new configuration file can be [created](#configure-kata-containers)
and [configured][7].
[1]: https://docs.snapcraft.io/snaps/intro