[Privoxy-commits] [privoxy] 01/03: faq.sgml: Fix markup

[User Git]

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch master
in repository privoxy.

commit df5d1d0f3eb6ab63917fba03f51a9e8a46c9df82
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Tue Jun 30 20:56:31 2026 +0200

    faq.sgml: Fix markup
---
 doc/source/faq.sgml | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index b5ab5345..b5f7004c 100644
--- a/doc/source/faq.sgml
+++ b/doc/source/faq.sgml
@@ -612,13 +612,19 @@ warranty? Registration?</title>
 <title>How can I confirm the Privoxy installer is genuine?</title>
 <para>
  Each binary installation package is GPG signed by the relevant packager, using
- detached .asc signature files, as follows:<br>
- <br><literal>gpg --armor --output installer.sig --detach-sig installer</literal><br>
- <br>
+ detached .asc signature files, as follows:
+</para>
+<para>
+ <literal>gpg --armor --output installer.sig --detach-sig installer</literal>
+</para>
+<para>
  To verify that the installer file has not been modified since it was built,
- use GPG to check that it cryptographically matches the signature, as follows:<br>
- <br><literal>gpg --verify installer.sig installer</literal><br>
- <br>
+ use GPG to check that it cryptographically matches the signature, as follows:
+</para>
+<para>
+ <literal>gpg --verify installer.sig installer</literal>
+</para>
+<para>
  The output of this command will identify the email address of the packager,
  alongside the fingerprint of their public GPG key. The current packagers are as
  follows:

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.