taler-docs

commit 9711dc486f0b49b65226053f1cede8cba555fee3
parent 482fe22d407e5619014ad66c2c1adc0f2ec9d6fa
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed, 27 May 2026 23:11:52 +0200

edit as per Leon

Diffstat:
M
taler-paivana-manual.rst
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/taler-paivana-manual.rst b/taler-paivana-manual.rst
@@ -57,10 +57,10 @@ paywalls:
   for any HTTP-based service. By placing the Paivana reverse proxy
   before the existing HTTP service, clients can be required to pay before
   accessing the service, without requiring any changes to the service
-  itself. A disadvantage is that it can be difficult to make
-  the Paivana reverse proxy fit into the look-and-feel of the site,
-  and that the configuration of payment rules must be done separate
-  from the actual content of the site.
+  itself. One consideration is that integrating the Paivana reverse
+  proxy seamlessly into the site’s existing look-and-feel can require
+  additional customization, and payment rule configurations are managed
+  separately from the site’s core content.
 - Using the Drupal Paivana extension: This extension works basically
   for any Drupal site, making it easy to keep the overall look-and-feel
   of the site. Prices can be configured per article within the site