Merge pull request #88 from allipatev/life-cycle-tables-fix

Life cycle tables fix
exasol · Mar 19, 2024 · 542f87f · 542f87f
2 parents 79cdb9c + 26dc730
commit 542f87f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -41,6 +41,7 @@ Please keep in mind the following limitations when creating or modifying KB arti
 2. Do not include the < or > symbol in your Markdown. If you need to use the symbols, use "\&lt;" or "\%gt;" instead to represent those characters
 3. Use \<br /> instead of \<br>
 4. Article should contain only one level 1 header (starting from a single hash sign #). The content starting from the second hash sign will not be rendered in Salesforce Knowledgebase.
+5. Tables need to be separated from the surrounding text by at least one blank line from above and below.
 
 ## Exasol Styles
 

diff --git a/Support-and-Services/Lifecycle.md b/Support-and-Services/Lifecycle.md
@@ -69,6 +69,7 @@ The ODBC (Open Database Connectivity) driver is fully supported until the end of
 
 ## ADO.NET driver support for Visual Studio, SQL Server and .NET versions.
 ADO.Net is fully supported until the end of life of the Visual Studio version it is associated with. If there is an explicitly stated end-of-life date for ADO.Net within a particular Visual Studio version, that takes precedence over the support provided by Visual Studio.
+
 |Product	| Version | Exasol Client Version | End of Exasol Support|	Remarks|
 |---|---|---|---|---|
 |Visual Studio 2022| 17.0 | 24.0 | 	|	|