Markdown table not well rendered #73

AutoLinkTypes docs theme setting is slightly confusing #74

build.cake

@@ -25,7 +25,7 @@
 #addin "nuget:https://api.nuget.org/v3/index.json?package=Octokit&version=0.50.0"
 //#addin "nuget:https://api.nuget.org/v3/index.json?package=System.Text.RegularExpressions&version=4.3.1"
 #addin "nuget:https://api.nuget.org/v3/index.json?package=Cake.Incubator&version=6.0.0"
-#addin "nuget:https://api.nuget.org/v3/index.json?package=Cake.Git&version=1.0.1"
+#addin "nuget:https://api.nuget.org/v3/index.json?package=Cake.Git&version=1.1.0"
 #addin "nuget:https://api.nuget.org/v3/index.json?package=Cake.Sonar&version=1.1.25"
 #addin "nuget:https://api.nuget.org/v3/index.json?package=Microsoft.Extensions.FileSystemGlobbing&version=2.2.0.0"
 #addin "nuget:https://api.nuget.org/v3/index.json?package=Cake.FileSet&version=2.0.0"

src/extensions/Wyam.Tables/CsvToMarkdown.cs

@@ -17,12 +17,13 @@ namespace Wyam.Tables
     /// This module reads the content of each input document as CSV and outputs an Markdown table
     /// containing the CSV content. The input CSV content must use <c>,</c> as separator and enclose
     /// every value in <c>"</c>. The output table has the format
-    ///
+    /// <code language="md">
     /// +--------------+-------------+
     /// | Test value 1 | TestValue 2 |
     /// +--------------+-------------+
     /// | Test value 2 | TestValue 3 |
     /// +--------------+-------------+
+    /// </code>
     /// </remarks>
     /// <category>Content</category>
     public class CsvToMarkdown : IModule

src/recipes/Wyam.Docs/DocsKeys.cs

@@ -72,8 +72,9 @@ public static class DocsKeys
         public const string IncludeGlobalNamespace = nameof(IncludeGlobalNamespace);
 
         /// <summary>
-        /// Controls whether type names from the API enclosed in code fences in either
-        /// blog posts or content pages should be automatically linked to the
+        /// Controls whether type names from the API enclosed in code fences 
+        /// (simple class name between back-ticks or full code fence (three ticks before and after) without any language specification)
+        /// in either blog posts or content pages should be automatically linked to the
         /// corresponding API documentation page (the default is <c>true</c>).
         /// </summary>
         /// <type><see cref="bool"/></type>