krb5 commit: Fix literal blocks in gssapi.rst

[Tom Yu]

https://github.com/krb5/krb5/commit/66b141745fc56bbdb7b738582ba7e1cce1e503c8
commit 66b141745fc56bbdb7b738582ba7e1cce1e503c8
Author: Tom Yu <tlyu at mit.edu>
Date:   Fri Sep 20 15:20:01 2013 -0400

    Fix literal blocks in gssapi.rst
    
    Some literal blocks in the new AEAD and IOV documentation in
    gssapi.rst started with ":" instead of "::", causing documentation
    build errors.

 doc/appdev/gssapi.rst |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/appdev/gssapi.rst b/doc/appdev/gssapi.rst
index 8e01ac0..d79f87d 100644
--- a/doc/appdev/gssapi.rst
+++ b/doc/appdev/gssapi.rst
@@ -350,7 +350,7 @@ gss_wrap_iov, it should first call gss_wrap_iov_length to query the
 lengths of the HEADER, PADDING, and TRAILER buffers.  DATA buffers
 must be provided in the iov list so that padding length can be
 computed correctly, but the output buffers need not be initialized.
-Here is an example of using gss_wrap_iov_length and gss_wrap_iov:
+Here is an example of using gss_wrap_iov_length and gss_wrap_iov::
 
     OM_uint32 major, minor;
     gss_iov_buffer_desc iov[4];
@@ -488,7 +488,7 @@ gss_ctx_id_t)::
 If the caller does not choose to request buffer allocation by
 gss_get_mic_iov, it should first call gss_get_mic_iov_length to query
 the length of the MIC_TOKEN buffer.  Here is an example of using
-gss_get_mic_iov_length and gss_get_mic_iov:
+gss_get_mic_iov_length and gss_get_mic_iov::
 
     OM_uint32 major, minor;
     gss_iov_buffer_desc iov[2];