remove '&' from sql

diff --git a/doc/antora/modules/reference/pages/raddb/mods-available/sql.adoc b/doc/antora/modules/reference/pages/raddb/mods-available/sql.adoc
index 90d01e60fe394f58150a14ab39e499ea6ce2eafd..be1d5d6ca0a4d2d6b2af4a6185086c6d229823ab 100644 (file)
--- a/doc/antora/modules/reference/pages/raddb/mods-available/sql.adoc
+++ b/doc/antora/modules/reference/pages/raddb/mods-available/sql.adoc
@@ -274,11 +274,11 @@ The module loops over all groups, and places the group name into the "group_attr
 The group attribute is used in the "authorize_group_check_query" and "authorize_group_check_query"
 to select entries which match that particular group.
 
-After all groups in SQL have been run, the module looks for `&control.User-Profile`, and runs
+After all groups in SQL have been run, the module looks for `control.User-Profile`, and runs
 those profiles for "authorize_group_check_query" and "authorize_group_check_query".  i.e. a user
 profile is essentially a group.
 
-These group queries can also update `&control.User-Profile`, which lets you have a group
+These group queries can also update `control.User-Profile`, which lets you have a group
 create a "fall through" to a DEFAULT group.  However, these groups are _not_ cross-checked against
 each other.  So it is possible to create loops, which is highly not recommended.
 
@@ -301,7 +301,7 @@ group attribute is `SQL1-Group`.
 cache_groups:: whether or not we cache the list of SQL groups
 
 The groups are cached in the `control` list.  So any comparisons must be done as
-`&control.SQL-Group = ...`
+`control.SQL-Group = ...`
 
 Default is `no`.
 

diff --git a/raddb/mods-available/sql b/raddb/mods-available/sql
index 80475c6d2efe906618bceaa08f0ef521ce9af1c2..9216fe818d8cfafe47d3351e07528d0a2d0baeab 100644 (file)
--- a/raddb/mods-available/sql
+++ b/raddb/mods-available/sql
@@ -315,11 +315,11 @@ sql {
        #  The group attribute is used in the "authorize_group_check_query" and "authorize_group_check_query"
        #  to select entries which match that particular group.
        #
-       #  After all groups in SQL have been run, the module looks for `&control.User-Profile`, and runs
+       #  After all groups in SQL have been run, the module looks for `control.User-Profile`, and runs
        #  those profiles for "authorize_group_check_query" and "authorize_group_check_query".  i.e. a user
        #  profile is essentially a group.
        #
-       #  These group queries can also update `&control.User-Profile`, which lets you have a group
+       #  These group queries can also update `control.User-Profile`, which lets you have a group
        #  create a "fall through" to a DEFAULT group.  However, these groups are _not_ cross-checked against
        #  each other.  So it is possible to create loops, which is highly not recommended.
        #
@@ -343,7 +343,7 @@ sql {
        #  cache_groups:: whether or not we cache the list of SQL groups
        #
        #  The groups are cached in the `control` list.  So any comparisons must be done as
-       #  `&control.SQL-Group = ...`
+       #  `control.SQL-Group = ...`
        #
        #  Default is `no`.
        #