Update docs/blog/20230801-Daeraxa-AugustUpdate.md

Co-authored-by: Andrew Dupont <[email protected]>

docs/blog/20230801-Daeraxa-AugustUpdate.md

@@ -37,7 +37,7 @@ or 
 
 The issue was that this list of identifiers had not been updated for a long time, and people used to other tools and applications with this same functionality (for example, within GitHub and various static site generators) were finding that identifiers they commonly used were not being correctly identified.
 
-This change adds some significant improvements to this system, not content with *only* updating the existing list of languages to match GitHub's [Liguist](https://github.com/github-linguist/linguist/blob/master/lib/linguist/languages.yml) libary but massively extending the system to allow users to tailor the behaviour to suit their own needs. In addition to the "Linguist" (GitHub) mode, it adds in lists for other tools such as "Chroma" (Codeberg, Gitea, Hugo), "Rouge" (GitLab, Jekyll) and "HighlightJS" (Markdown-IT). In many cases, these will be identical and users can leave it on the existing default mode (Liguist). However, for those who rely on Pulsar and the `markdown-preview` package to correctly display code as it will be used on the platform of their choice, this allows them to not have to modify the identifier between their editor and their production files.
+This change adds some significant improvements to this system, not content with *only* updating the existing list of languages to match GitHub's [Linguist](https://github.com/github-linguist/linguist/blob/master/lib/linguist/languages.yml) library but massively extending the system to allow users to tailor the behaviour to suit their own needs. In addition to the "Linguist" (GitHub) mode, it adds in lists for other tools such as "Chroma" (Codeberg, Gitea, Hugo), "Rouge" (GitLab, Jekyll) and "HighlightJS" (Markdown-IT). In many cases, these will be identical and users can leave it on the existing default mode (Linguist). However, for those who rely on Pulsar and the `markdown-preview` package to correctly display code as it will be used on the platform of their choice, this allows them to not have to modify the identifier between their editor and their production files.
 
 As if that wasn't enough, it also features a new feature that allows you to freely add and customise your own options in order to include non-default languages and to override your own options by way of a new setting within the package:  `Custom Syntax Highlighting Language Identifiers`. For example, if I wanted to have [PON](https://web.pulsar-edit.dev/packages/language-pon) support or wanted to add `j` as an identifier for "javascript", I could add the following to that setting: `pon: source.pon, j: source.js`.