diff --git a/docs-xml/smbdotconf/locking/kerneloplocks.xml b/docs-xml/smbdotconf/locking/kerneloplocks.xml
index a22cdf2446d..ff237ec76e3 100644
--- a/docs-xml/smbdotconf/locking/kerneloplocks.xml
+++ b/docs-xml/smbdotconf/locking/kerneloplocks.xml
@@ -4,19 +4,18 @@
                  xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
 <description>
 	<para>For UNIXes that support kernel based <smbconfoption name="oplocks"/>
-	(currently only IRIX and the Linux 2.4 kernel), this parameter 
-	allows the use of them to be turned on or off. However, this disables
-	Level II oplocks for clients as the Linux and IRIX kernels do not
-	support them properly.</para>
+	(currently only Linux), this parameter allows the use of them to be
+	turned on or off. However, this disables Level II oplocks for clients as
+	the Linux kernel does not support them properly.</para>
 
 	<para>Kernel oplocks support allows Samba <parameter moreinfo="none">oplocks
-	</parameter> to be broken whenever a local UNIX process or NFS operation 
+	</parameter> to be broken whenever a local UNIX process or NFS operation
 	accesses a file that <citerefentry><refentrytitle>smbd</refentrytitle>
-	<manvolnum>8</manvolnum></citerefentry> has oplocked. This allows complete 
-	data consistency between SMB/CIFS, NFS and local file access (and is 
+	<manvolnum>8</manvolnum></citerefentry> has oplocked. This allows complete
+	data consistency between SMB/CIFS, NFS and local file access (and is
 	a <emphasis>very</emphasis> cool feature :-).</para>
 	<para>If you do not need this interaction, you should disable the
-	parameter on Linux and IRIX to get Level II oplocks and the associated
+	parameter on Linux to get Level II oplocks and the associated
 	performance benefit.</para>
 
 	<para>This parameter defaults to <constant>no</constant> and is translated