From 9a6dcbf895f9da01768e64b73cec88c16157d91e Mon Sep 17 00:00:00 2001
From: Michael Biebl
in situations where it cannot be automatically determined that the secret is required (some VPNs and PPP -providers dont require all secrets) this flag indicates that the specific +providers don't require all secrets) this flag indicates that the specific secret is not required
out_pitem
on return, the permission item (formatted accoring to ptype
+
on return, the permission item (formatted according to ptype
, see
“permissions” for more detail
gboolean
nm_setting_connection_add_secondary (NMSettingConnection *setting,
const char *sec_uuid);
-Adds a new secondary connetion UUID to the setting.
+Adds a new secondary connection UUID to the setting.
Parameters
diff --git a/docs/libnm-util/html/NMSettingWirelessSecurity.html b/docs/libnm-util/html/NMSettingWirelessSecurity.html
index 83a4be08..76b0781b 100644
--- a/docs/libnm-util/html/NMSettingWirelessSecurity.html
+++ b/docs/libnm-util/html/NMSettingWirelessSecurity.html
@@ -938,7 +938,7 @@ algorithm list.
Returns
- TRUE if the encryption algorith was found and removed; FALSE if it was not.
+ TRUE if the encryption algorithm was found and removed; FALSE if it was not.
Since: 0.9.10
@@ -1560,9 +1560,9 @@ encryption protocol
enum NMWepKeyType
The NMWepKeyType values specify how any WEP keys present in the setting
-are intepreted. There are no standards governing how to hash the various WEP
+are interpreted. There are no standards governing how to hash the various WEP
key/passphrase formats into the actual WEP key. Unfortunately some WEP keys
-can be interpreted in multiple ways, requring the setting to specify how to
+can be interpreted in multiple ways, requiring the setting to specify how to
interpret the any WEP keys. For example, the key "732f2d712e4a394a375d366931"
is both a valid Hexadecimal WEP key and a WEP passphrase. Further, many
ASCII keys are also valid WEP passphrases, but since passphrases and ASCII
diff --git a/docs/libnm-util/html/index.html b/docs/libnm-util/html/index.html
index 77d7c18e..90af150c 100644
--- a/docs/libnm-util/html/index.html
+++ b/docs/libnm-util/html/index.html
@@ -15,7 +15,7 @@
libnm-util Reference Manual
- for libnm-util 1.14.6
+ for libnm-util 1.16.0
The latest version of this documentation can be found on-line at
https://developer.gnome.org/libnm-util/stable/.
diff --git a/docs/libnm-util/html/libnm-util-NetworkManager.html b/docs/libnm-util/html/libnm-util-NetworkManager.html
index aa7bd3a2..c5ab858e 100644
--- a/docs/libnm-util/html/libnm-util-NetworkManager.html
+++ b/docs/libnm-util/html/libnm-util-NetworkManager.html
@@ -671,7 +671,7 @@ an
-an 802.11 WiFi device
+an 802.11 Wi-Fi device
@@ -1294,7 +1294,7 @@ GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability
the device is connecting to the requested network.
- This may include operations like associating with the WiFi AP, dialing
+ This may include operations like associating with the Wi-Fi AP, dialing
the modem, connecting to the remote Bluetooth device, etc.
@@ -1751,7 +1751,7 @@ GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability
-The WiFi network could not be found
+The Wi-Fi network could not be found
diff --git a/docs/libnm-util/html/libnm-util-nm-utils.html b/docs/libnm-util/html/libnm-util-nm-utils.html
index 106d1c8f..c1b0ce0c 100644
--- a/docs/libnm-util/html/libnm-util-nm-utils.html
+++ b/docs/libnm-util/html/libnm-util-nm-utils.html
@@ -789,7 +789,7 @@ use type
-the security type to check AP flags and device capabilties against,
+
the security type to check AP flags and device capabilities against,
e.g. NMU_SEC_STATIC_WEP
@@ -819,13 +819,13 @@ arguments are valid
ap_wpa
-bitfield of AP capabilties derived from the AP's WPA beacon,
+
bitfield of AP capabilities derived from the AP's WPA beacon,
e.g. (NM_802_11_AP_SEC_PAIR_TKIP | NM_802_11_AP_SEC_KEY_MGMT_PSK)
ap_rsn
-bitfield of AP capabilties derived from the AP's RSN/WPA2 beacon,
+
bitfield of AP capabilities derived from the AP's RSN/WPA2 beacon,
e.g. (NM_802_11_AP_SEC_PAIR_CCMP | NM_802_11_AP_SEC_PAIR_TKIP)
@@ -834,7 +834,7 @@ e.g. (
Returns
- TRUE if the device capabilities and AP capabilties intersect and are
+
TRUE if the device capabilities and AP capabilities intersect and are
compatible with the desired type
, FALSE if they are not
@@ -859,7 +859,7 @@ desired security type are valid for AP/Hotspot connections.
type
-the security type to check device capabilties against,
+
the security type to check device capabilities against,
e.g. NMU_SEC_STATIC_WEP
@@ -1597,9 +1597,9 @@ and predicate
user_data
-(allow-none): user data for predicate
+
user data for predicate
function.
-[closure]
+[closure][allow-none]
error
--
cgit 1.3.0-6-gf8a5