Fix spelling.

Pointed out by Faidon Liambotis.

radsecproxy.conf.5.xml

@@ -2,7 +2,7 @@
 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
 <refentry>
   <refentryinfo>
-    <date>2016-03-14</date>
+    <date>2016-03-23</date>
   </refentryinfo>
   <refmeta>
     <refentrytitle>
@@ -122,7 +122,7 @@ blocktype name {
       blocks are discussed later. Note that none of these options are
       required, and indeed in many cases they are not needed.  Note
       that you should specify each at most once. The behaviour with
-      multiple occurences is undefined.
+      multiple occurrences is undefined.
     </para>
     <variablelist>
       <varlistentry>
@@ -456,7 +456,7 @@ blocktype name {
       required if at least one TLS/DTLS client or server is
       configured. Note that there can be multiple blocks for each
       type.  For each type, the block names should be unique. The
-      behaviour with multiple occurences of the same name for the same
+      behaviour with multiple occurrences of the same name for the same
       block type is undefined. Also note that some block option values
       may reference a block by name, in which case the block name must
       be previously defined. Hence the order of the blocks may be
@@ -798,7 +798,7 @@ blocktype name {
 	trailing <literal>/</literal> after the regexp. So as an
 	example, if you want to use regexp matching the domain
 	<literal>example.com</literal> you could have a realm block
-	named <literal>/@example\\.com$</literal>. Optinally this can
+	named <literal>/@example\\.com$</literal>. Optionally this can
 	also be written <literal>/@example\\.com$/</literal>. If you
 	want to match all domains under the <literal>.com</literal>
 	top domain, you could do <literal>/@.*\\.com$</literal>. Note