[elpa] externals/denote 4b3ba57386: Add missing underscore from examples in exporting section

[ELPA Syncer]

branch: externals/denote
commit 4b3ba573869ed3806c61d6fcdb5c55abad09e3c1
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Add missing underscore from examples in exporting section
    
    Thanks to Peter Prevos for bringing this matter to my attention:
    
<https://lists.sr.ht/~protesilaos/denote/%3C87fs8b85tq.fsf%40prevos.net%3E#%3C87lehiuxfo.fsf@protesilaos.com%3E>.
---
 README.org | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.org b/README.org
index f1b9b68bc2..7828c9c76f 100644
--- a/README.org
+++ b/README.org
@@ -2875,8 +2875,8 @@ conventions of Denote's file-naming scheme."
 When exporting Denote notes to, for example, an HTML or PDF file,
 there is a high probability that the same file name is used with a new
 extension.  This is problematic because it creates files with
-duplicate identifiers.  The =20230515T085612--example_keyword.org=
-produces a =20230515T085612--example_keyword.pdf=.  Any link to the
+duplicate identifiers.  The =20230515T085612--example__keyword.org=
+produces a =20230515T085612--example__keyword.pdf=.  Any link to the
 =20230515T085612= will thus break: it does not honor Denote's
 expectation of finding unique identifiers.  This is not the fault of
 Denote: exporting is done by the user without Denote's involvement.
@@ -2905,7 +2905,7 @@ Insert =#+export_file_name: FILENAME= in the front matter 
before
 exporting to force a filename called whatever the value of =FILENAME=
 is.  The =FILENAME= does not specify the file type extension, such as
 =.pdf=.  This is up to the export engine.  For example, a Denote note
-with a complete file name of =20230515T085612--example_keyword.org=
+with a complete file name of =20230515T085612--example__keyword.org=
 and a front matter entry of =#+export_file_name: hello= will be
 exported as =hello.pdf=.