[lxc-devel] [linuxcontainers.org/master] Fix key name in English LXC 3.1 announcement

[lxc-jp on Github]

A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 370 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20190326/c728e79c/attachment.bin>
-------------- next part --------------
From ed6f7f5580d342d93ad423d9a81625048297d7a1 Mon Sep 17 00:00:00 2001
From: KATOH Yasufumi <karma at jazz.email.ne.jp>
Date: Wed, 27 Mar 2019 15:33:55 +0900
Subject: [PATCH] Fix key name in English LXC 3.1 announcement

Signed-off-by: KATOH Yasufumi <karma at jazz.email.ne.jp>
---
 content/lxc/news/lxc-3.1.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/lxc/news/lxc-3.1.yaml b/content/lxc/news/lxc-3.1.yaml
index 8b24473..87b7b82 100644
--- a/content/lxc/news/lxc-3.1.yaml
+++ b/content/lxc/news/lxc-3.1.yaml
@@ -29,7 +29,7 @@ content: |-
   Going forward each new API addition will be given a unique name that can be passed to `lxc_has_api_extension()`. This is modeled after LXD's API extension checks. This allows API users to query the given LXC instance whether a given API extension is supported.
 
   #### add `lxc.cgroup.relative` configuration key
-  This adds the new `lxc.cgroup.keep` config key. The key can be used to instruct LXC to never escape to the root cgroup. This makes it easy for users to adhere to restrictions enforced by `cgroup2` and `systemd`. Specifically, this makes it possible to run LXC containers as systemd services.
+  This adds the new `lxc.cgroup.relative` config key. The key can be used to instruct LXC to never escape to the root cgroup. This makes it easy for users to adhere to restrictions enforced by `cgroup2` and `systemd`. Specifically, this makes it possible to run LXC containers as systemd services.
 
   #### allocate new network namespace identifier on startup
   Each container will now have a unique network namespace identifier assigned on startup. This can be used by LXC to siginficantly speed up operations performed on network namespaces (e.g. network device configuration and retrieval).