From 4d4d3ee69fd9301c36c06bae50a6621b23cd44ec Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Wed, 13 May 2015 10:31:31 -0700 Subject: [PATCH 1/3] docs: fix link formatting --- Documentation/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/networking.md b/Documentation/networking.md index 80c605a..31a9da6 100644 --- a/Documentation/networking.md +++ b/Documentation/networking.md @@ -78,7 +78,7 @@ Since macvlan interface has its own MAC and is located on the same link segment With the IP address allocated by the real network infrastructure, this makes the pod IP routable in the same way as the host IP. `macvlan` specific configuration fields are: - **master** (string): the name of host interface to "clone". This field is required. -- **mode** (string): One of "bridge", "private", "vepa", or "passthru". This controls how traffic is handled between different macvlan interfaces on the same host. See (this guide)[http://www.pocketnix.org/posts/Linux%20Networking:%20MAC%20VLANs%20and%20Virtual%20Ethernets] for discussion of modes. Defaults to "bridge". +- **mode** (string): One of "bridge", "private", "vepa", or "passthru". This controls how traffic is handled between different macvlan interfaces on the same host. See [this guide](http://www.pocketnix.org/posts/Linux%20Networking:%20MAC%20VLANs%20and%20Virtual%20Ethernets) for discussion of modes. Defaults to "bridge". - **mtu** (integer): the size of the MTU in bytes for bridge and veths. Defaults to MTU of the master device. - **ipMasq** (boolean): whether to setup IP masquerading on the host. Defaults to false. From e607295d462e84ed3e319c40132de1256132ce8b Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Wed, 13 May 2015 10:32:19 -0700 Subject: [PATCH 2/3] docs: fix broken link --- Documentation/signing-and-verification-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/signing-and-verification-guide.md b/Documentation/signing-and-verification-guide.md index aa81b3d..51b0488 100644 --- a/Documentation/signing-and-verification-guide.md +++ b/Documentation/signing-and-verification-guide.md @@ -14,7 +14,7 @@ hello-0.0.1-linux-amd64.aci ## Signing ACIs -By default rkt requires ACIs to be signed using a gpg detached signature. The following steps will walk you through the creation of a gpg keypair suitable for signing an ACI. If you have an existing gpg signing key skip to the [Signing the ACI](signing-the-aci) step. +By default rkt requires ACIs to be signed using a gpg detached signature. The following steps will walk you through the creation of a gpg keypair suitable for signing an ACI. If you have an existing gpg signing key skip to the [Signing the ACI](#signing-acis) step. ### Generate a gpg signing key From 516851409a4c07fde58ecf0044080d6f5adc9403 Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Fri, 15 May 2015 10:34:29 -0700 Subject: [PATCH 3/3] docs: fix in-page link --- Documentation/signing-and-verification-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/signing-and-verification-guide.md b/Documentation/signing-and-verification-guide.md index 51b0488..cec1465 100644 --- a/Documentation/signing-and-verification-guide.md +++ b/Documentation/signing-and-verification-guide.md @@ -14,7 +14,7 @@ hello-0.0.1-linux-amd64.aci ## Signing ACIs -By default rkt requires ACIs to be signed using a gpg detached signature. The following steps will walk you through the creation of a gpg keypair suitable for signing an ACI. If you have an existing gpg signing key skip to the [Signing the ACI](#signing-acis) step. +By default rkt requires ACIs to be signed using a gpg detached signature. The following steps will walk you through the creation of a gpg keypair suitable for signing an ACI. If you have an existing gpg signing key skip to the [Signing the ACI](#signing-the-aci) step. ### Generate a gpg signing key