From 7da313b7c600f26a2b8caba79467e35328a8f949 Mon Sep 17 00:00:00 2001 From: Henrik Helgesen Date: Tue, 16 Nov 2021 09:44:12 -0800 Subject: [PATCH] Corrected code fencing --- content/Contributing/FormattingTips/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/Contributing/FormattingTips/index.md b/content/Contributing/FormattingTips/index.md index 1f51c906..4f4e525e 100644 --- a/content/Contributing/FormattingTips/index.md +++ b/content/Contributing/FormattingTips/index.md @@ -14,7 +14,7 @@ Here you can find a rather interesting Cheat Sheet regarding markdown: [https:// The syntax to use codefences is with backticks. If you provide the language after the first block of backticks, github will automatically put that in decent syntax highlighting. So, A simple code fence with AL code, can simply be done by: ```` -```al +```AL procedure ALGuidelinesRock() var Customer: Record Customer; @@ -27,7 +27,7 @@ The syntax to use codefences is with backticks. If you provide the language aft ```` Results in: -```al +```AL procedure ALGuidelinesRock() var Customer: Record Customer; @@ -63,4 +63,4 @@ makes: {{}} ``` makes: -{{< figure src="http://www.waldo.be/wp-content/uploads/2021/11/business-central-logo.png" title="Business Central" >}} \ No newline at end of file +{{< figure src="http://www.waldo.be/wp-content/uploads/2021/11/business-central-logo.png" title="Business Central" >}}