doc: mention gnutls_session_ext_register and its supplemental data equivalent

diff --git a/doc/cha-internals.texi b/doc/cha-internals.texi
index 2fdf977a150a1be58d06dc42def0dc82bbfa1cc0..2f71ee2d96888035497d3ce09b09f5690353637c 100644 (file)
--- a/doc/cha-internals.texi
+++ b/doc/cha-internals.texi
@@ -124,8 +124,8 @@ the process to do so is not difficult.  Here are the steps you need to
 follow if you wish to do this yourself.  For sake of discussion, let's
 consider adding support for the hypothetical TLS extension
 @code{foobar}. The following section is about adding an extension to GnuTLS,
-for custom application extensions you should check the exported function
-@funcref{gnutls_ext_register}.
+for custom application extensions you should check the exported functions
+@funcref{gnutls_session_ext_register} or @funcref{gnutls_ext_register}.
 
 @subsubheading Add @code{configure} option like @code{--enable-foobar} or @code{--disable-foobar}.
 
@@ -425,8 +425,8 @@ _foobar_supp_send_params(gnutls_session_t session, gnutls_buffer_t buf)
 @}
 @end example
 
-Afterwards, register the new supplemental data using @funcref{gnutls_supplemental_register},
-at some point in your program.
+Afterwards, register the new supplemental data using @funcref{gnutls_session_supplemental_register},
+or @funcref{gnutls_supplemental_register} at some point in your program.
 
 @node Cryptographic Backend
 @section Cryptographic Backend