summary refs log tree commit diff
path: root/docs/libnm-util/html/NMSettingWirelessSecurity.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/libnm-util/html/NMSettingWirelessSecurity.html')
-rw-r--r--docs/libnm-util/html/NMSettingWirelessSecurity.html6
1 files changed, 3 insertions, 3 deletions
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.</p>
 </div>
 <div class="refsect3">
 <a name="nm-setting-wireless-security-remove-pairwise-by-value.returns"></a><h4>Returns</h4>
-<p> <a href="https://developer.gnome.org/glib/unstable/glib-Standard-Macros.html#TRUE:CAPS"><code class="literal">TRUE</code></a> if the encryption algorith was found and removed; <a href="https://developer.gnome.org/glib/unstable/glib-Standard-Macros.html#FALSE:CAPS"><code class="literal">FALSE</code></a> if it was not.</p>
+<p> <a href="https://developer.gnome.org/glib/unstable/glib-Standard-Macros.html#TRUE:CAPS"><code class="literal">TRUE</code></a> if the encryption algorithm was found and removed; <a href="https://developer.gnome.org/glib/unstable/glib-Standard-Macros.html#FALSE:CAPS"><code class="literal">FALSE</code></a> if it was not.</p>
 </div>
 <p class="since">Since: 0.9.10</p>
 </div>
@@ -1560,9 +1560,9 @@ encryption protocol</p>
 <div class="refsect2">
 <a name="NMWepKeyType"></a><h3>enum NMWepKeyType</h3>
 <p>The <a class="link" href="NMSettingWirelessSecurity.html#NMWepKeyType" title="enum NMWepKeyType"><span class="type">NMWepKeyType</span></a> 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