From 746820feae2366916e4221c1a65c4d2892c08698 Mon Sep 17 00:00:00 2001
From: Charlie <64078329+zacharlie@users.noreply.github.com>
Date: Wed, 7 Oct 2020 22:51:13 +0200
Subject: [PATCH] Updated Changelog Workflows (markdown)

---
 Changelog-Workflows.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Changelog-Workflows.md b/Changelog-Workflows.md
index 329cd88..37452f4 100644
--- a/Changelog-Workflows.md
+++ b/Changelog-Workflows.md
@@ -73,7 +73,7 @@ The entries will therefore need to comply with the associated stylesheets and co
 
 The following list outlines some basic guidelines for ensuring the entry content is of the required standards:
 
-- The feature title should be unique. Pull requests often use "tags" to automatically manage elements in the workflow such as adding the [Feature] label to the element title. All such elements should be removed, and the title should properly convey the new functionality introduced.
+- The feature title should be unique. Pull requests often use "tags" to automatically manage elements in the workflow such as adding the **[Feature]** label to the element title. All such elements should be removed, and the title should properly convey the new functionality introduced.
 - Each entry should be categorised appropriately. By default, all newly imported entries will be included in the "General" category, however only entries that truly belong in the general category should be categorised as general by the time of publication.
 - Content should be articulate and concise. Details from the pull request relating to developer specific content or items specifically for the documentation team can be removed. Some information on the feature utilisation is suitable, however it should not be verbose.
 - Git/ GitHub specific references such as 'This PR adds' introductions should be modified to 'Functionality was introduced to' or 'We have added'.