docs: Update sphinx, requirements, support markdown tables

[vpp.git] / docs / gettingstarted / developers / infrastructure.md

diff --git a/docs/gettingstarted/developers/infrastructure.md b/docs/gettingstarted/developers/infrastructure.md
index b994607..9dde982 100644 (file)
--- a/docs/gettingstarted/developers/infrastructure.md
+++ b/docs/gettingstarted/developers/infrastructure.md
@@ -48,7 +48,7 @@ macro! It's smart about NULL pointers.\]
 
 Typically, the user header is not present. User headers allow for other
 data structures to be built atop vppinfra vectors. Users may specify the
 
 Typically, the user header is not present. User headers allow for other
 data structures to be built atop vppinfra vectors. Users may specify the

-alignment for first data element of a vector via the [vec]()\*\_aligned
+alignment for first data element of a vector via the \[vec\]()\*\_aligned

 macros. 
 
 Vector elements can be any C type e.g. (int, double, struct bar). This
 macros. 
 
 Vector elements can be any C type e.g. (int, double, struct bar). This


@@ -57,7 +57,7 @@ Many macros have \_a variants supporting alignment of vector elements
 and \_h variants supporting non-zero-length vector headers. The \_ha
 variants support both.  Additionally cacheline alignment within a
 vector element structure can be specified using the
 and \_h variants supporting non-zero-length vector headers. The \_ha
 variants support both.  Additionally cacheline alignment within a
 vector element structure can be specified using the

-[CLIB_CACHE_LINE_ALIGN_MARK]() macro.
+\[CLIB_CACHE_LINE_ALIGN_MARK\]() macro.

 
 Inconsistent usage of header and/or alignment related macro variants
 will cause delayed, confusing failures.
 
 Inconsistent usage of header and/or alignment related macro variants
 will cause delayed, confusing failures.