diff options
| author | Linus Nordberg <linus@nordu.net> | 2016-03-23 10:55:42 +0100 |
|---|---|---|
| committer | Linus Nordberg <linus@nordu.net> | 2016-03-23 10:57:57 +0100 |
| commit | cc68bc85464a1e6587210e1becf1e8d54b1b6482 (patch) | |
| tree | 84616aa459ad225ed215ce4dcb66b551db225c01 /radsecproxy.conf.5.xml | |
| parent | c10288993c67bda9d0c4b966e1aebf076dc766bb (diff) | |
Fix spelling.
Pointed out by Faidon Liambotis.
Diffstat (limited to 'radsecproxy.conf.5.xml')
| -rw-r--r-- | radsecproxy.conf.5.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/radsecproxy.conf.5.xml b/radsecproxy.conf.5.xml index 120666f..ff579c4 100644 --- a/radsecproxy.conf.5.xml +++ b/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 |