From 9600e0db98fb3ae3783b973bf5fb8499e8d65bf0 Mon Sep 17 00:00:00 2001 From: Krisztian Olah Date: Tue, 9 Apr 2024 09:18:52 +0200 Subject: [PATCH] Update DocumentationBlock.md Fixed typos --- .../Conceptual/DocumentationBlock.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/articles/units/Inxton.vortex.compiler.console/Conceptual/DocumentationBlock.md b/articles/units/Inxton.vortex.compiler.console/Conceptual/DocumentationBlock.md index 10776297..10386daa 100644 --- a/articles/units/Inxton.vortex.compiler.console/Conceptual/DocumentationBlock.md +++ b/articles/units/Inxton.vortex.compiler.console/Conceptual/DocumentationBlock.md @@ -1,8 +1,8 @@ # Documentation blocks (implementation pending) -Types (FB, PRG, ENUMS, etc) and their members can be documented at PLC side and Ixnton helps you to transfer documentation content to the emitted code. +Types (FB, PRG, ENUMS, etc) and their members can be documented at PLC side and Inxton helps you to transfer documentation content to the emitted code. -Transferable documentations comments must be enclosed with syntax as indicated in the following example. In addition to that the documentation content mus be placed between documentation tags. Content placed within the documentation tags will then be placed as documentation comments to the emitted code. +Transferable documentations comments must be enclosed with syntax as indicated in the following example. In addition to that the documentation content must be placed between documentation tags. Content placed within the documentation tags will then be placed as documentation comments to the emitted code. >NOTE: There is no syntax checking and the content is transferred 'as is'. @@ -37,4 +37,4 @@ public class fbDocumentedBlock /// this is a member that is documented. /// this is note to documented member ...boolean documentedMember {get; set;} -} \ No newline at end of file +}