Remove & from &reply attribute

perl -p -i -e 's/\&reply/reply/g' $(git grep -lE '&[a-zA-Z0-9]' doc/antora | egrep -v 'raddb|developers|interpreter|assets')

diff --git a/doc/antora/modules/ROOT/pages/debugging/processing.adoc b/doc/antora/modules/ROOT/pages/debugging/processing.adoc
index 28e6922c519cfc2f3851042f6faf007542c73783..87a1fa674b8fdfd0d3ed85416c3eb47fd05c887f 100644 (file)
--- a/doc/antora/modules/ROOT/pages/debugging/processing.adoc
+++ b/doc/antora/modules/ROOT/pages/debugging/processing.adoc
@@ -71,8 +71,8 @@ Here, the `attr_filter` module is removing attributes which are forbidden from a
     (0)     [attr_filter.access_reject] = updated
     (0)     [eap] = noop
     (0)     policy remove_reply_message_if_eap {
-    (0)       if (&reply:EAP-Message && &reply:Reply-Message) {
-    (0)       if (&reply:EAP-Message && &reply:Reply-Message)  -> FALSE
+    (0)       if (reply:EAP-Message && reply:Reply-Message) {
+    (0)       if (reply:EAP-Message && reply:Reply-Message)  -> FALSE
     (0)       else {
     (0)         [noop] = noop
     (0)       } # else = noop
@@ -222,7 +222,7 @@ It now runs the normal `post-auth` section
     (2)     if (0)  -> FALSE
     (2)   } # post-auth = noop
     (2) Finished internally proxied request.
-    (2) Clearing existing &reply: attributes
+    (2) Clearing existing reply: attributes
 ====
 
 Because this is a proxied request, it now runs the `post-proxy` section of the `default` virtual server.
@@ -258,8 +258,8 @@ It then runs the `post-auth` section from the `default` virtual server.
     (2)       } # update = noop
     (2)       [exec] = noop
     (2)       policy remove_reply_message_if_eap {
-    (2)         if (&reply:EAP-Message && &reply:Reply-Message) {
-    (2)         if (&reply:EAP-Message && &reply:Reply-Message)  -> FALSE
+    (2)         if (reply:EAP-Message && reply:Reply-Message) {
+    (2)         if (reply:EAP-Message && reply:Reply-Message)  -> FALSE
     (2)         else {
     (2)           [noop] = noop
     (2)         } # else = noop

diff --git a/doc/antora/modules/howto/pages/installation/upgrade.adoc b/doc/antora/modules/howto/pages/installation/upgrade.adoc
index fee1c01d11edd7838b860595f22439adc31b56cc..9ab02f2978c7ef09c70c62b8f77cf0cbcabe1277 100644 (file)
--- a/doc/antora/modules/howto/pages/installation/upgrade.adoc
+++ b/doc/antora/modules/howto/pages/installation/upgrade.adoc
@@ -992,7 +992,7 @@ In v4 they must now be specified as::
 ```
 counter_name    = &control.Daily-Session-Time
 check_name      = &control.Max-Daily-Session
-reply_name      = &reply.Session-Timeout
+reply_name      = reply.Session-Timeout
 key             = "%{Stripped-User-Name || &User-Name}"
 ```
 

diff --git a/doc/antora/modules/reference/pages/type/string/double.adoc b/doc/antora/modules/reference/pages/type/string/double.adoc
index 9616d42511e8e85ad965f3a36b2a14c319dac140..88fd01d93a85267d951ff033b8bf74b386692716 100644 (file)
--- a/doc/antora/modules/reference/pages/type/string/double.adoc
+++ b/doc/antora/modules/reference/pages/type/string/double.adoc
@@ -86,7 +86,7 @@ resulting string can be quite different, depending on the inputs.
 [source,unlang]
 ----
 "User-Name is " + &User-Name
-"IP Address is " + (string) &reply.Framed-IP-Address
+"IP Address is " + (string) reply.Framed-IP-Address
 ----
 
 The output strings here (with casting) are the same as for the
@@ -97,7 +97,7 @@ because it is already a string.
 [source,unlang]
 ----
 "User-Name is " + (octets) &User-Name
-"IP Address is " + (octets) &reply.Framed-IP-Address
+"IP Address is " + (octets) reply.Framed-IP-Address
 ----
 
 The output strings here are completely different than for the previous

diff --git a/doc/antora/modules/reference/pages/unlang/call.adoc b/doc/antora/modules/reference/pages/unlang/call.adoc
index 117b0c3b7b5de2c5b8b20f2ca0be5b039acfb2eb..9e9d251e4bfe8e6c8b5513e7dd719ea04e8834d6 100644 (file)
--- a/doc/antora/modules/reference/pages/unlang/call.adoc
+++ b/doc/antora/modules/reference/pages/unlang/call.adoc
@@ -35,7 +35,7 @@ Processing the contents of a DHCPv6 relay-message by using a
 subrequest and recursively calling the DHCPv6 virtual server.
 [source,unlang]
 ----
-subrequest &Packet-Type &Relay-Message &reply.Relay-Message {
+subrequest &Packet-Type &Relay-Message reply.Relay-Message {
     call dhcpv6 {}
 }
 ----