Browse code

topos: spelling fix in README for contact parameter

(cherry picked from commit 0a9b039f79de90a45e263325cb247f49a31d9f36)

Henning Westerholt authored on 04/10/2021 15:38:23
Showing 1 changed files
... ...
@@ -294,7 +294,7 @@ modparam("topos", "event_mode", 2)
294 294
 		<title><varname>contact_host</varname> (str)</title>
295 295
 		<para>
296 296
 			You may need to control the host part of the Contact header added
297
-			by topos. If the xavu_filed_contact_host parameter is set, this value is
297
+			by topos. If the xavu_field_contact_host parameter is set, this value is
298 298
 			ignored.
299 299
 
300 300
 			For example when using TLS with TOPOS the remote UAS must be able to open
... ...
@@ -397,7 +397,7 @@ modparam("topos", "cparam_name", "xyz")
397 397
 		<programlisting format="linespecific">
398 398
 ...
399 399
 modparam("topos", "xavu_cfg", "_tps_")
400
-modparam("topos", "xavu_filed_a_contact", "a_contact")
400
+modparam("topos", "xavu_field_a_contact", "a_contact")
401 401
 ...
402 402
     $xavu(_tps_=>a_contact) = "...";
403 403
 ...
... ...
@@ -405,7 +405,7 @@ modparam("topos", "xavu_filed_a_contact", "a_contact")
405 405
 		</example>
406 406
 	</section>
407 407
 	<section id="topos.p.xavu_field_a_contact">
408
-		<title><varname>xavu_filed_a_contact</varname> (str)</title>
408
+		<title><varname>xavu_field_a_contact</varname> (str)</title>
409 409
 		<para>
410 410
 			Name of the field inside root XAVU specifed by `xavu_cfg`
411 411
 			to evaluate for the A-side Contact Header user part. This parameter
... ...
@@ -417,11 +417,11 @@ modparam("topos", "xavu_filed_a_contact", "a_contact")
417 417
 		</emphasis>
418 418
 		</para>
419 419
 		<example>
420
-		<title>Set <varname>xavu_filed_a_contact</varname> parameter</title>
420
+		<title>Set <varname>xavu_field_a_contact</varname> parameter</title>
421 421
 		<programlisting format="linespecific">
422 422
 ...
423 423
 modparam("topos", "xavu_cfg", "_tps_")
424
-modparam("topos", "xavu_filed_a_contact", "a_contact")
424
+modparam("topos", "xavu_field_a_contact", "a_contact")
425 425
 ...
426 426
     $xavu(_tps_=>a_contact) = "...";
427 427
 ...
... ...
@@ -429,7 +429,7 @@ modparam("topos", "xavu_filed_a_contact", "a_contact")
429 429
 		</example>
430 430
 	</section>
431 431
 	<section id="topos.p.xavu_field_b_contact">
432
-		<title><varname>xavu_filed_b_contact</varname> (str)</title>
432
+		<title><varname>xavu_field_b_contact</varname> (str)</title>
433 433
 		<para>
434 434
 			Name of the field inside root XAVU specifed by `xavu_cfg`
435 435
 			to evaluate for the B-side Contact Header user part. This parameter
... ...
@@ -441,11 +441,11 @@ modparam("topos", "xavu_filed_a_contact", "a_contact")
441 441
 		</emphasis>
442 442
 		</para>
443 443
 		<example>
444
-		<title>Set <varname>xavu_filed_b_contact</varname> parameter</title>
444
+		<title>Set <varname>xavu_field_b_contact</varname> parameter</title>
445 445
 		<programlisting format="linespecific">
446 446
 ...
447 447
 modparam("topos", "xavu_cfg", "_tps_")
448
-modparam("topos", "xavu_filed_b_contact", "b_contact")
448
+modparam("topos", "xavu_field_b_contact", "b_contact")
449 449
 ...
450 450
     $xavu(_tps_=>b_contact) = "...";
451 451