Correct "hexidecimal" typos.

Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>

4 files changed, 6 insertions, 6 deletions

diff --git a/docs-xml/using_samba/ch01.xml b/docs-xml/using_samba/ch01.xml
index 01d7791d637..3c6594bf8bd 100644
--- a/docs-xml/using_samba/ch01.xml
+++ b/docs-xml/using_samba/ch01.xml
@@ -660,7 +660,7 @@ HYDRA          <20>  UNIQUE      Registered
 </table>
 
 
-<para>Note that because <indexterm id="ch01-idx-951737-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary> resource types and</tertiary></indexterm>DNS names don't have resource types, the designers intentionally made hexidecimal value 20 (an ASCII space) default to the type for a file server.</para>
+<para>Note that because <indexterm id="ch01-idx-951737-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary> resource types and</tertiary></indexterm>DNS names don't have resource types, the designers intentionally made hexadecimal value 20 (an ASCII space) default to the type for a file server.</para>
 </sect3>
 
 
diff --git a/docs-xml/using_samba/ch04.xml b/docs-xml/using_samba/ch04.xml
index f8b45093aef..b394baba2a4 100644
--- a/docs-xml/using_samba/ch04.xml
+++ b/docs-xml/using_samba/ch04.xml
@@ -593,7 +593,7 @@ netbios aliases = sales accounting payroll</programlisting>
 
 <varlistentry><term>Numerical</term>
 <listitem><para>
-<indexterm id="ch04-idx-967220-0"><primary>numerical type</primary></indexterm>An integer, hexidecimal, or octal number. The standard <literal>0x</literal><emphasis>nn</emphasis> syntax is used for hexadecimal and <literal>0</literal><emphasis>nnn</emphasis> for octal.</para></listitem>
+<indexterm id="ch04-idx-967220-0"><primary>numerical type</primary></indexterm>An integer, hexadecimal, or octal number. The standard <literal>0x</literal><emphasis>nn</emphasis> syntax is used for hexadecimal and <literal>0</literal><emphasis>nnn</emphasis> for octal.</para></listitem>
 </varlistentry>
 
 
diff --git a/docs-xml/using_samba/ch06.xml b/docs-xml/using_samba/ch06.xml
index 8e8740b8b6c..14fe238ddab 100644
--- a/docs-xml/using_samba/ch06.xml
+++ b/docs-xml/using_samba/ch06.xml
@@ -1210,7 +1210,7 @@ username</title>
 
 
 <varlistentry><term>Last Change Time</term>
-<listitem><para>This code consists of the characters <literal>LCT-</literal> followed by a hexidecimal representation of the amount of seconds since the epoch (midnight on January 1, 1970) that the entry was last changed.</para></listitem>
+<listitem><para>This code consists of the characters <literal>LCT-</literal> followed by a hexadecimal representation of the amount of seconds since the epoch (midnight on January 1, 1970) that the entry was last changed.</para></listitem>
 </varlistentry>
 </variablelist>
 
diff --git a/docs-xml/using_samba/ch08.xml b/docs-xml/using_samba/ch08.xml
index 7465b8a67b2..84cb87cc823 100644
--- a/docs-xml/using_samba/ch08.xml
+++ b/docs-xml/using_samba/ch08.xml
@@ -860,7 +860,7 @@ client code page</title>
 
 <entry colname="col1"><para><literal>HEX</literal></para></entry>
 
-<entry colname="col2"><para>Three-byte hexidecimal code</para></entry>
+<entry colname="col2"><para>Three-byte hexadecimal code</para></entry>
 
 </row>
 
@@ -868,7 +868,7 @@ client code page</title>
 
 <entry colname="col1"><para><literal>CAP</literal></para></entry>
 
-<entry colname="col2"><para>Three-byte hexidecimal code (Columbia Appletalk Program)</para></entry>
+<entry colname="col2"><para>Three-byte hexadecimal code (Columbia Appletalk Program)</para></entry>
 
 </row>
 
@@ -894,7 +894,7 @@ valid chars = 0450:0420 0x0A20:0x0A00
 valid chars = A:a</programlisting>
 
 
-<para>Each of the characters in the list specified should be separated by spaces. If there is a colon between two characters or their numerical equivalents, the data to the left of the colon is considered an uppercase character, while the data to the right is considered the lowercase character. You can represent characters both by literals (if you can type them) and by octal, hexidecimal, or decimal Unicode equivalents.</para>
+<para>Each of the characters in the list specified should be separated by spaces. If there is a colon between two characters or their numerical equivalents, the data to the left of the colon is considered an uppercase character, while the data to the right is considered the lowercase character. You can represent characters both by literals (if you can type them) and by octal, hexadecimal, or decimal Unicode equivalents.</para>
 
 
 <para>We recommend against using this option. Instead, go with one of the standard code pages listed earlier in this section. If you do use this option, however, it must be listed after the <literal>client</literal> <literal>code</literal> <literal>page</literal> to which you wish to add the character. Otherwise, the characters will not be added.<indexterm id="ch08-idx-965533-0" class="endofrange" startref="ch08-idx-965219-0"/>