docs: fix markdown errors and update

project-docs/workflow/LICENSING.md

@@ -10,7 +10,7 @@ Copy the license from [projectmanagement](../../LICENSE) or the [official standa
 
 According to the GPLv3 guidelines for [adding the license to a new program](http://www.gnu.org/licenses/gpl-3.0-standalone.html#howto) a license note should be added at the beginning of each source file.
 
-```
+```typescript
 /*
  * Copyright (C) <year> StApps
  * This program is free software: you can redistribute it and/or modify it
@@ -30,14 +30,16 @@ According to the GPLv3 guidelines for [adding the license to a new program](http
 ### New Files
 
 The `<year>` should be inserted with the current year. E.g.:
-```
+
+```typescript
  * Copyright (C) 2019 StApps
 ```
 
 ### Updating Files
 
 If the file is updated in a new year after its creation, the `<year>` should be appended as a comma seperated list with spaces in between. E.g.:
-```
+
+```typescript
  * Copyright (C) 2018, 2019, 2021 StApps
 ```