Fix typos and broken links in docs

Signed-off-by: Yu-Ju Hong <yjhong@google.com>
This commit is contained in:
Yu-Ju Hong 2018-01-04 18:28:14 -08:00
parent bc774a9108
commit 07a0685499
2 changed files with 4 additions and 4 deletions

View File

@ -52,7 +52,7 @@ specifications as appropriate.
1. Install development libraries: 1. Install development libraries:
* **libseccomp development library.** Required by cri-containerd and runc seccomp support. `libseccomp-dev` (Ubuntu, Debian) / `libseccomp-devel` * **libseccomp development library.** Required by cri-containerd and runc seccomp support. `libseccomp-dev` (Ubuntu, Debian) / `libseccomp-devel`
(Fedora, CentOS, RHEL). On releases of Ubuntu <=Trusty and Debian <=jessie a (Fedora, CentOS, RHEL). On releases of Ubuntu <=Trusty and Debian <=jessie a
backport version of `libsecomp-dev` is required. See [travis.yml](.travis.yml) for an example on trusty. backport version of `libseccomp-dev` is required. See [travis.yml](.travis.yml) for an example on trusty.
* **libapparmor development library.** Required by cri-containerd and runc apparmor support. To use apparmor on Debian, Ubuntu, and related distributions the installation of `libapparmor-dev` is required. * **libapparmor development library.** Required by cri-containerd and runc apparmor support. To use apparmor on Debian, Ubuntu, and related distributions the installation of `libapparmor-dev` is required.
* **btrfs development library.** Required by containerd btrfs support. `btrfs-tools`(Ubuntu, Debian) / `btrfs-progs-devel`(Fedora, CentOS, RHEL) * **btrfs development library.** Required by containerd btrfs support. `btrfs-tools`(Ubuntu, Debian) / `btrfs-progs-devel`(Fedora, CentOS, RHEL)
2. Install other dependencies: 2. Install other dependencies:

View File

@ -13,7 +13,7 @@ or `crictl` please make sure the issue has not already been submitted.
If you have not already installed crictl please install the version compatible If you have not already installed crictl please install the version compatible
with the `cri-containerd` you are using. If you are a user, your deployment with the `cri-containerd` you are using. If you are a user, your deployment
should have installed crictl for you. If not, get it from your release tarball. should have installed crictl for you. If not, get it from your release tarball.
If you are a developer the current version of crictl is specified [here](./hack/version). If you are a developer the current version of crictl is specified [here](../hack/versions).
A helper command has been included to install the dependencies at the right version: A helper command has been included to install the dependencies at the right version:
```console ```console
$ make install.deps $ make install.deps
@ -23,8 +23,8 @@ so you don't have to repeatedly specify the runtime sock used to connect crictl
to the container runtime: to the container runtime:
```console ```console
$ cat /etc/crictl.yaml $ cat /etc/crictl.yaml
runtime-endpoint: /run/containerd/containerd.sock runtime-endpoint: /var/run/cri-containerd.sock
image-endpoint: /run/containerd/containerd.sock image-endpoint: /var/run/cri-containerd.sock
timeout: 10 timeout: 10
debug: true debug: true
``` ```