From c995aa42dadd1fa33c603bb025fd950e87471e6b Mon Sep 17 00:00:00 2001 From: Henrik Helgesen Date: Wed, 23 Feb 2022 01:09:10 -0800 Subject: [PATCH] MD Lint Cleanup / Added Discussion Links --- content/docs/BestPractices/begin-as-an-afterword/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/BestPractices/begin-as-an-afterword/index.md b/content/docs/BestPractices/begin-as-an-afterword/index.md index 190bae4f..6a48008c 100644 --- a/content/docs/BestPractices/begin-as-an-afterword/index.md +++ b/content/docs/BestPractices/begin-as-an-afterword/index.md @@ -8,7 +8,7 @@ _Created by Microsoft, Described by waldo_ ## Description -When `begin` follows `then`, `else`, `do`, it should be on the same line, preceded by one space character. +When `begin` follows `then`, `else`, `do`, it should be on the same line, preceded by one space character. ## Bad code @@ -27,8 +27,8 @@ When `begin` follows `then`, `else`, `do`, it should be on the same line, preced end; ``` -## [Discussions](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices?discussions_q=begin+as+an+After+Word+category%3A%22BC+Best+Practices%22) +## Discussion + +Discuss this Best Practice [here](https://github.com/microsoft/alguidelines/discussions/123) You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). - -If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file