libvpx: Pull from upstream

source/libvpx/usage.dox

 /*!\page usage Usage
 
     The vpx multi-format codec SDK provides a unified interface amongst its
     supported codecs. This abstraction allows applications using this SDK to
     easily support multiple video formats with minimal code duplication or
     "special casing." This section describes the interface common to all codecs.
     For codec-specific details, see the \ref codecs page.
 
     The following sections are common to all codecs:
     - \ref usage_types
     - \ref usage_features
     - \ref usage_init
     - \ref usage_errors
 
-    Fore more information on decoder and encoder specific usage, see the
+    For more information on decoder and encoder specific usage, see the
     following pages:
     \if decoder
-    - \subpage usage_decode
+    \li \subpage usage_decode
     \endif
-    \if decoder
-    - \subpage usage_encode
+    \if encoder
+    \li \subpage usage_encode
     \endif
 
     \section usage_types Important Data Types
     There are two important data structures to consider in this interface.
 
     \subsection usage_ctxs Contexts
     A context is a storage area allocated by the calling application that the
     codec may write into to store details about a single instance of that codec.
     Most of the context is implementation specific, and thus opaque to the
     application. The context structure as seen by the application is of fixed
@@ skipping 42 matching lines @@
     initialization time to ensure the application is using a header file that
     matches the library. The current ABI version number is stored in the
     preprocessor macros #VPX_CODEC_ABI_VERSION, #VPX_ENCODER_ABI_VERSION, and
     #VPX_DECODER_ABI_VERSION. For convenience, each initialization function has
     a wrapper macro that inserts the correct version number. These macros are
     named like the initialization methods, but without the _ver suffix.
 
 
     The available initialization methods are:
     \if encoder
-     - #vpx_codec_enc_init (calls vpx_codec_enc_init_ver())
-     - #vpx_codec_enc_init_multi (calls vpx_codec_enc_init_multi_ver())
-     .
+    \li #vpx_codec_enc_init (calls vpx_codec_enc_init_ver())
+    \li #vpx_codec_enc_init_multi (calls vpx_codec_enc_init_multi_ver())
     \endif
-    \if decoder - #vpx_codec_dec_init (calls vpx_codec_dec_init_ver()) \endif
-
+    \if decoder
+    \li #vpx_codec_dec_init (calls vpx_codec_dec_init_ver())
+    \endif
 
 
     \section usage_errors Error Handling
     Almost all codec functions return an error status of type #vpx_codec_err_t.
     The semantics of how each error condition should be processed is clearly
     defined in the definitions of each enumerated value. Error values can be
     converted into ASCII strings with the vpx_codec_error() and
     vpx_codec_err_to_string() methods. The difference between these two methods is
     that vpx_codec_error() returns the error state from an initialized context,
     whereas vpx_codec_err_to_string() can be used in cases where an error occurs
@@ skipping 27 matching lines @@
     and the semantics of the call are preserved, as before.
 
     The special value <code>0</code> is reserved to represent an infinite
     deadline. In this case, the codec will perform as much processing as
     possible to yield the highest quality frame.
 
     By convention, the value <code>1</code> is used to mean "return as fast as
     possible."
 
 */