[elpa] externals-release/org d156399 1/3: Update example :publishing-function names in manual

[ELPA Syncer]

branch: externals-release/org
commit d156399445f7d537a7aa667e8703b1e944bdcce0
Author: Greg Minshall <minshall@umich.edu>
Commit: Kyle Meyer <kyle@kyleam.com>

    Update example :publishing-function names in manual
    
    * doc/org-manual.org (Publishing action): Fix references to
    org-latex-publish-to-pdf and org-org-publish-to-org.
---
 doc/org-manual.org | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 6ff731f..a23b286 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -15771,12 +15771,12 @@ and possibly transformed in the process.  The default 
transformation
 is to export Org files as HTML files, and this is done by the function
 ~org-html-publish-to-html~ which calls the HTML exporter (see [[*HTML
 Export]]).  But you can also publish your content as PDF files using
-~org-publish-org-to-pdf~, or as ASCII, Texinfo, etc., using the
+~org-latex-publish-to-pdf~, or as ASCII, Texinfo, etc., using the
 corresponding functions.
 
 If you want to publish the Org file as an =.org= file but with
 /archived/, /commented/, and /tag-excluded/ trees removed, use
-~org-publish-org-to-org~.  This produces =file.org= and put it in the
+~org-org-publish-to-org~.  This produces =file.org= and put it in the
 publishing directory.  If you want a htmlized version of this file,
 set the parameter ~:htmlized-source~ to ~t~.  It produces
 =file.org.html= in the publishing directory[fn:140].