about summary refs log tree commit diff
path: root/man/nmcli.xml
diff options
context:
space:
mode:
authorMichael Biebl <biebl@debian.org>2020-10-05 22:28:16 +0200
committerMichael Biebl <biebl@debian.org>2020-10-05 22:28:16 +0200
commit47a2114d6f697a31d84c8874c49e94dd04119d75 (patch)
treee3022686ff1956d7f17f1f7cdf7022ce980b7a5c /man/nmcli.xml
parent9d722f3d3492e31c0b3e4bcba603ffd65309c621 (diff)
parentaafc1dbe4712c86189bbc1d4d54ad8cb4c69be7e (diff)
Update upstream source from tag 'upstream/1.27.90'
Update to upstream version '1.27.90'
with Debian dir 72a0791efa5966be1724a82dfcac90f6cd22bd1b
Diffstat (limited to 'man/nmcli.xml')
-rw-r--r--man/nmcli.xml16
1 files changed, 8 insertions, 8 deletions
diff --git a/man/nmcli.xml b/man/nmcli.xml
index fdc79ad4..e1b2d81b 100644
--- a/man/nmcli.xml
+++ b/man/nmcli.xml
@@ -1506,7 +1506,7 @@
               <term><option>private</option></term>
               <listitem>
                 <para>if set to <literal>yes</literal>, the connection will only be visible
-                to the user who created it. Otherwise the connection is system-wide, which is
+                to the user who created it. Otherwise, the connection is system-wide, which is
                 the default.</para>
               </listitem>
             </varlistentry>
@@ -1514,7 +1514,7 @@
               <term><option>hidden</option></term>
               <listitem>
                 <para>set to <literal>yes</literal> when connecting for the first time to an
-                AP not broadcasting its SSID. Otherwise the SSID would not be found and the
+                AP not broadcasting its SSID. Otherwise, the SSID would not be found and the
                 connection attempt would fail.</para>
               </listitem>
             </varlistentry>
@@ -1671,7 +1671,7 @@
 
         <listitem>
           <para>Register <command>nmcli</command> as a NetworkManager secret agent and listen for secret
-          requests. You do usually not need this command, because <command>nmcli</command> can handle
+          requests. You usually do not need this command, because <command>nmcli</command> can handle
           secrets when connecting to networks. However, you may find the command useful
           when you use another tool for activating connections and you do not have a
           secret agent available (like nm-applet).</para>
@@ -1749,35 +1749,35 @@
       <varlistentry>
         <term><option>connectivity-full</option></term>
         <listitem>
-          <para>Conectivity state when Internet is reachable.</para>
+          <para>Connectivity state when Internet is reachable.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><option>connectivity-limited</option></term>
         <listitem>
-          <para>Conectivity state when only a local network reachable.</para>
+          <para>Connectivity state when only a local network reachable.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><option>connectivity-none</option></term>
         <listitem>
-          <para>Conectivity state when the network is disconnected.</para>
+          <para>Connectivity state when the network is disconnected.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><option>connectivity-portal</option></term>
         <listitem>
-          <para>Conectivity state when a captive portal hijacked the connection.</para>
+          <para>Connectivity state when a captive portal hijacked the connection.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><option>connectivity-unknown</option></term>
         <listitem>
-          <para>Conectivity state when a connectivity check didn't run.</para>
+          <para>Connectivity state when a connectivity check didn't run.</para>
         </listitem>
       </varlistentry>