--- loncom/html/adm/help/tex/Domain_Configuration_LangTZAuth.tex	2022/02/27 01:43:14	1.13
+++ loncom/html/adm/help/tex/Domain_Configuration_LangTZAuth.tex	2022/02/27 03:47:25	1.14
@@ -72,14 +72,14 @@ authentication would fail for: userID@ex
 did exist, and the password supplied matched what was expected.
 
 To enable this functionality requires customizing two routines in /home/httpd/lib/perl/localenroll.pm:
-&unamemap_rules() and &unamemap_check(). There are stubs for both of them (with documentation) in the
+&unamemap\_rules() and &unamemap\_check(). There are stubs for both of them (with documentation) in the
 uncustomized template file: /home/httpd/lib/perl/localenroll-std.pm.  Restart of loncontrol is required
 after making changes to localenroll.pm.
 
-Once &unamemap_rules() contains at least one rule, then the ``Default authentication/language/timezone/portal/types''
+Once &unamemap\_rules() contains at least one rule, then the ``Default authentication/language/timezone/portal/types''
 domain configuration will include a checkbox for at least one rule in ``Available conversions'' listed in the
 ``Mapping for missing usernames via standard log-in'' section. Checking the checkbox and pushing ``Save Changes''
-will make the corresponding conversion for that rule, as coded in &unamemap_check(), available to create
+will make the corresponding conversion for that rule, as coded in &unamemap\_check(), available to create
 a derived username for a second authentication attempt, if the original username did not exist, but matched
 the required format for the conversion.