Fixed invalid 'warning' markdown tags in the documentation:

Old: '{: .notice--warning}'
New: ':::: warning'

Author: Nusiq

docs/docs/guide/getting-started.md

@@ -131,11 +131,13 @@ Now, you can re-run `regolith run`.
 
 Check `com.mojang`, and open the new `texture_list.json` file in `RP/textures/texture_list.json`. Every time you run regolith, this file will be re-created, based on your current textures. No need to manually edit it ever again!
 
-{: .notice--warning}
+:::: warning
 `Warning:` If your resource pack already contains `texture_list.json`, you should delete it. You don't need to manually worry about it anymore - Regolith will handle it!
+::::
 
-{: .notice--warning}
+:::: warning
 `Warning:` If your project doesn't have any textures, than `texture_list.json` will simply create a blank file `[]`. Consider adding some textures to see the filter at work!
+::::
 
 ## Whats Next
 

docs/docs/guide/installing-filters.md

@@ -65,15 +65,17 @@ Regolith is intended to be used with git version control, and by default the `.r
 
 You may use the command `regolith install-all`, which will check `config.json`, and install every filter in the `filterDefinitions`.
 
-{: .notice--warning}
+:::: warning
 This is only intended to be used with existing projects. To install new filters, use `regolith install`.
+::::
 
 ## Filter Versioning
 
 Filters in Regolith are optionally versioned with a [semantic version](https://semver.org/). As filters get updated, new versions will be released, and you can optionally update.
 
-{: .notice--warning}
+:::: warning
 If you don't specify a version, the `install` command will pick a sensible default. First, it will search for the latest release. If that doesn't exist (such as a filter that has no versions), it will select the latest commit in the repository. In both cases, the installed version will be `pinned`.
+::::
 
 ### Installing a Specific Version