From 979145cbaef36e98ad6d4e9cee1a334c9152f005 Mon Sep 17 00:00:00 2001 From: Pavel Cahyna Date: Thu, 4 Oct 2018 15:51:05 +0200 Subject: [PATCH] More doc improvements --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 3cf269a..32d8b37 100644 --- a/README.md +++ b/README.md @@ -142,7 +142,7 @@ Note that if the `state` option is unset, the connection profile’s runtime sta ### `persistent_state` -The `persistent_state` option identifies if a connection profile is in a persistent state. The `persistent_state` option can be set to the following values: +The `persistent_state` option identifies if a connection profile is persistent (saved on disk). The `persistent_state` option can be set to the following values: #### `persistent_state: present` (default) @@ -152,6 +152,10 @@ incomplete (no `type` option), the behavior is undefined. Also, the `present` va does not directly result in a change in the network configuration. If the `state` option is not set to `up`, the profile is only created or modified, not activated. +For NetworkManager, the new connection profile is created with the `autoconnect` +option enabled by default. Therefore, NetworkManager can activate the new +profile on a currently disconnected device. ([rh#1401515](https://bugzilla.redhat.com/show_bug.cgi?id=1401515)). + #### `persistent_state: absent` The `absent` value ensures that the profile is not present on the @@ -228,10 +232,6 @@ role. ### `autoconnect` -For NetworkManager, the new connection profile is created when the `autoconnect` -option is enabled by default. Therefore, NetworkManager can activate the new -profile on a currently disconnected device. ([rh#1401515](https://bugzilla.redhat.com/show_bug.cgi?id=1401515)). - By default, profiles are created with autoconnect enabled. - For `NetworkManager`, this corresponds to the `connection.autoconnect` property.