Update releasing.md (#270)

Co-authored-by: shall0pass <20625555+shall0pass@users.noreply.github.com>

.github/workflows/spelling.yml

@@ -81,18 +81,20 @@ jobs:
         use_magic_file: 1
         experimental_apply_changes_via_bot: 1
         use_sarif: 1
-        extra_dictionary_limit: 10
+        extra_dictionary_limit: 12
+        check_extra_dictionaries: ''
         extra_dictionaries:
           cspell:cpp/src/cpp.txt
           cspell:software-terms/src/software-terms.txt
           cspell:python/src/python/python-lib.txt
-          cspell:php/php.txt
           cspell:node/node.txt
-          cspell:npm/npm.txt
-          cspell:typescript/typescript.txt
           cspell:filetypes/filetypes.txt
-          cspell:html/html.txt
           cspell:aws/aws.txt
+          cspell:typescript/dict/typescript.txt
+          cspell:npm/dict/npm.txt
+          cspell:fullstack/dict/fullstack.txt
+          cspell:html/dict/html.txt
+          cspell:css/dict/css.txt
 
   comment-push:
     name: Report (Push)

docs/contributing/releasing.md

@@ -56,7 +56,5 @@ This automation will also delete all the outdated release note files from the `u
 Once you’ve merged and tagged the release, go to the releases page and publish a new release. Use this as the body of the release note:
 
 ```markdown
-:link: [View release notes](https://actualbudget.github.io/docs/Release-Notes#2330)
+:link: [View release notes](https://actualbudget.org/blog/release-23.10.0)
 ```
-
-Replace `2330` with the version number of the release you’re releasing, with all the periods removed.