[master] 550f76ddb doc: Polish identifiers / strings section

[Nils Goroll]

commit 550f76ddbd2c95bc5e795e329993df8f8ee36e0d
Author: Nils Goroll <nils.goroll at uplex.de>
Date:   Fri Nov 8 09:05:08 2024 +0100

    doc: Polish identifiers / strings section
    
    Follow-up 11f8d31592e8d3e52a92ab8ca6cd3d54d596c6ed

diff --git a/doc/sphinx/reference/vcl.rst b/doc/sphinx/reference/vcl.rst
index 90215b2af..295a55e79 100644
--- a/doc/sphinx/reference/vcl.rst
+++ b/doc/sphinx/reference/vcl.rst
@@ -54,13 +54,15 @@ Character Sets
 
 .. _VMODs: https://varnish-cache.org/docs/trunk/reference/vmod.html
 
-While identifiers are written in ASCII, strings can contain any character set
-as long as the *NUL* (zero, 0) byte is reserved. The Varnish Configuration
-Language itself is not concerned with the character encoding of strings, VCL
-code handling strings in different character sets needs to track encodings
-itself. `VMODs`_ exist to help with such tasks.
-
-To illustrate, ``"��"`` is a valid UTF-8 *string* in UTF-8, but ``��`` is not a
+While identifiers can only consist of this subset of ASCII, **strings** can
+contain any bytes except *NUL* (zero, 0), which marks the end of the string. The
+Varnish Configuration Language itself is not concerned with the character
+encoding of strings. VCL code handling strings in different character sets needs
+to track encodings itself. `VMODs`_ exist to help with such tasks (e.g.
+``iconv``).
+
+To illustrate, ``"��"`` is a valid **string** which, when interpreted as UTF-8,
+happens to represent code point ``U+1F96C`` (Leafy Green) but ``��`` is not a
 valid *identifier*.
 
 Character Sets in HTTP