docs: add warning emojis to important notes across multiple documentation files

ui/v2.5/src/docs/en/Manual/AutoTagging.md

@@ -6,7 +6,7 @@ This task is part of the advanced settings mode.
 
 ## Rules
 
-> **Important:** Auto Tag only works for names that already exist in your Stash database. It does not create new Performers, Studios, or Tags.
+> **⚠️ Important:** Auto Tag only works for names that already exist in your Stash database. It does not create new Performers, Studios, or Tags.
 
  - Multi-word names are matched when words appear in order and are separated by any of these characters: `.`, `-`, `_`, or whitespace. These separators are treated as word boundaries.
  - Matching is case-insensitive but requires complete words within word boundaries. Partial words or misspelled words will not match.

ui/v2.5/src/docs/en/Manual/Captions.md

@@ -15,4 +15,4 @@ Where `{language_code}` is defined by the [ISO-6399-1](https://en.wikipedia.org/
 
 Scenes with captions can be filtered with the `captions` criterion.
 
-**Note:** If the caption file was added after the scene was initially added during scan, you will need to run a Selective Scan task for it to show up.
+> **⚠️ Note:** If the caption file was added after the scene was initially added during scan, you will need to run a Selective Scan task for it to show up.

ui/v2.5/src/docs/en/Manual/Configuration.md

@@ -31,7 +31,7 @@ Some examples:
 - `"^/stash/videos/exclude/"` will exclude all directories that match `/stash/videos/exclude/` pattern.
 - `"\\\\stash\\network\\share\\excl\\"` will exclude specific Windows network path `\\stash\network\share\excl\`.
 
-> **Note:** If a directory is excluded for images and videos, then the directory will be excluded from scans completely.
+> **⚠️ Note:** If a directory is excluded for images and videos, then the directory will be excluded from scans completely.
 
 _There is a useful [regex101](https://regex101.com/) site that can help test and experiment with regexps._
 
@@ -87,7 +87,7 @@ This setting can be used to increase/decrease overall CPU utilisation in two sce
 1. High performance 4+ core cpus.
 2. Media files stored on remote/cloud filesystem.
 
-Note: If this is set too high it will decrease overall performance and causes failures (out of memory).
+> **⚠️ Note:** If this is set too high it will decrease overall performance and causes failures (out of memory).
 
 ## Hardware accelerated live transcoding
 
@@ -117,7 +117,7 @@ Some scrapers require a Chrome instance to function correctly. If left empty, st
 
 `Chrome CDP path` can be set to a path to the chrome executable, or an http(s) address to remote chrome instance (for example: `http://localhost:9222/json/version`).
 
-> **Important**: As of Chrome 136 you need to specify `--user-data-dir` alongside `--remote-debugging-port`. Read more on their [official post](https://developer.chrome.com/blog/remote-debugging-port). 
+> **⚠️ Important:** As of Chrome 136 you need to specify `--user-data-dir` alongside `--remote-debugging-port`. Read more on their [official post](https://developer.chrome.com/blog/remote-debugging-port). 
 
 ## Authentication
 

ui/v2.5/src/docs/en/Manual/Deduplication.md

@@ -2,8 +2,10 @@
 
 [The dupe checker](/sceneDuplicateChecker) searches your collection for scenes that are perceptually similar. This means that the files don't need to be identical, and will be identified even with different bitrates, resolutions, and intros/outros.
 
-To achieve this stash needs to generate what's called a phash, or perceptual hash. Similar to sprite generation stash will generate a set of 25 images from fixed points in the scene. These images will be stitched together, and then hashed using the phash algorithm. The phash can then be used to find scenes that are the same or similar to others in the database. Phash generation can be run during scan, or as a separate task. Note that generation can take a while due to the work involved with extracting screenshots.
+To achieve this stash needs to generate what's called a phash, or perceptual hash. Similar to sprite generation stash will generate a set of 25 images from fixed points in the scene. These images will be stitched together, and then hashed using the phash algorithm. The phash can then be used to find scenes that are the same or similar to others in the database. Phash generation can be run during scan, or as a separate task. 
+
+> **⚠️ Note:** Generation can take a while due to the work involved with extracting screenshots.
 
 The dupe checker can be run with four different levels of accuracy. `Exact` looks for scenes that have exactly the same phash. This is a fast and accurate operation that should not yield any false positives except in very rare cases. The other accuracy levels look for duplicate files within a set distance of each other. This means the scenes don't have exactly the same phash, but are very similar. `High` and `Medium` should still yield very good results with few or no false positives. `Low` is likely to produce some false positives, but might still be useful for finding dupes.
 
-Note that to generate a phash stash requires an uncorrupted file. If any errors are encountered during sprite generation the phash will not be generated. This is to prevent false positives.
+> **⚠️ Note:** To generate a pHash Stash requires an uncorrupted file. If any errors are encountered during sprite generation the pHash will not be generated. This is to prevent false positives.

ui/v2.5/src/docs/en/Manual/EmbeddedPlugins.md

@@ -10,7 +10,9 @@ Stash currently supports Javascript embedded plugin tasks using [goja](https://g
 
 ### Plugin input
 
-The input is provided to Javascript plugin tasks using the `input` global variable, and is an object based on the structure provided in the `Plugin input` section of the [Plugins](/help/Plugins.md) page. Note that the `server_connection` field should not be necessary in most embedded plugins.
+The input is provided to Javascript plugin tasks using the `input` global variable, and is an object based on the structure provided in the `Plugin input` section of the [Plugins](/help/Plugins.md) page. 
+
+> **⚠️ Note:** `server_connection` field should not be necessary in most embedded plugins.
 
 ### Plugin output
 

ui/v2.5/src/docs/en/Manual/Images.md

@@ -11,7 +11,7 @@ You can add images to every gallery manually in the gallery detail page. Deletin
 
 For best results, images in zip file should be stored without compression (copy, store or no compression options depending on the software you use. Eg on linux: `zip -0 -r gallery.zip foldertozip/`). This impacts **heavily** on the zip read performance.
 
-> **:warning: Note:** AVIF files in ZIP archives are currently unsupported.
+> **⚠️ Note:** AVIF files in ZIP archives are currently unsupported.
 
 If a filename of an image in the gallery zip file ends with `cover.jpg`, it will be treated like a cover and presented first in the gallery view page and as a gallery cover in the gallery list view. If more than one images match the name the first one found in natural sort order is selected.
 

ui/v2.5/src/docs/en/Manual/Introduction.md

@@ -2,6 +2,8 @@
 
 Stash works by cataloging your media using the paths that you provide. Once you have [configured](/settings?tab=library) the locations where your media is stored, you can click the Scan button in [`Settings -> Tasks`](/settings?tab=tasks) and stash will begin scanning and importing your media into its library.
 
-For the best experience, it is recommended that after a scan is finished, that video previews and sprites are generated. You can do this in [`Settings -> Tasks`](/settings?tab=tasks). Note that currently it is only possible to perform one task at a time and but there is a task queue, so the generate tasks should be performed after scan is complete.
+For the best experience, it is recommended that after a scan is finished, that video previews and sprites are generated. You can do this in [`Settings -> Tasks`](/settings?tab=tasks). 
+
+> **⚠️ Note:** Currently it is only possible to perform one task at a time and but there is a task queue, so the generate tasks should be performed after scan is complete.
 
 Once your media is imported, you are ready to begin creating Performers, Studios and Tags, and curating your content!

ui/v2.5/src/docs/en/Manual/JSONSpec.md

@@ -24,7 +24,7 @@ When exported, files are named with different formats depending on the object ty
 | Studios | `<name>.json` |
 | Groups | `<name>.json` |
 
-Note that the file naming is not significant when importing. All json files will be read from the subdirectories.
+> **⚠️ Note:** The file naming is not significant when importing. All json files will be read from the subdirectories.
   
 ## Content of the json files
 

ui/v2.5/src/docs/en/Manual/Plugins.md

@@ -240,7 +240,7 @@ hooks:
       argKey: argValue
 ```
 
-**Note:** it is possible for hooks to trigger eachother or themselves if they perform mutations. For safety, hooks will not be triggered if they have already been triggered in the context of the operation. Stash uses cookies to track this context, so it's important for plugins to send cookies when performing operations.
+**⚠️ Note:** It is possible for hooks to trigger eachother or themselves if they perform mutations. For safety, hooks will not be triggered if they have already been triggered in the context of the operation. Stash uses cookies to track this context, so it's important for plugins to send cookies when performing operations.
 
 #### Trigger types
 

ui/v2.5/src/docs/en/Manual/ScraperDevelopment.md

@@ -375,7 +375,7 @@ scene:
     selector: //div[@data-host="{inputHostname}"]//span[@class="site-name"]
 ```
 
-> **Note:** These placeholders represent the actual URL used to fetch the content, after any URL replacements have been applied.
+> **⚠️ Note:** These placeholders represent the actual URL used to fetch the content, after any URL replacements have been applied.
 
 ### Common fragments
 
@@ -391,6 +391,7 @@ performer:
 The `Measurements` xpath string will replace `$infoPiece` with `//div[@class="infoPiece"]/span`, resulting in: `//div[@class="infoPiece"]/span[text() = 'Measurements:']/../span[@class="smallInfo"]`.
 
 > **⚠️ Note:** Recursive common fragments are **not** supported.  
+
 Referencing a common fragment within another common fragment will cause an error. For example:
 ```yaml
 common:
@@ -881,7 +882,7 @@ Title
 URLs
 ```
 
-> **Important**: `Title` field is required. 
+> **⚠️ Important:** `Title` field is required. 
 
 ### Group
 
@@ -900,7 +901,7 @@ Tags (see Tag fields)
 URLs
 ```
 
-> **Important**: `Name` field is required. 
+> **⚠️ Important:** `Name` field is required. 
 
 ### Image
 
@@ -944,9 +945,9 @@ URLs
 Weight
 ```
 
-> **Important**: `Name` field is required. 
+> **⚠️ Important:** `Name` field is required. 
 
-> **Note:**  - `Gender` must be one of `male`, `female`, `transgender_male`, `transgender_female`, `intersex`, `non_binary` (case insensitive).
+> **⚠️ Note:** `Gender` must be one of `male`, `female`, `transgender_male`, `transgender_female`, `intersex`, `non_binary` (case insensitive).
 
 ### Scene
 
@@ -964,7 +965,7 @@ Title
 URLs
 ```
 
-> **Important**: `Title` field is required only if fileless.
+> **⚠️ Important:** `Title` field is required only if fileless.
 
 ### Studio
 
@@ -976,7 +977,7 @@ Tags (see Tag fields)
 URL
 ```
 
-> **Important**: `Name` field is required. 
+> **⚠️ Important:** `Name` field is required. 
 
 ### Tag
 
@@ -984,4 +985,4 @@ URL
 Name
 ```
 
-> **Important**: `Name` field is required. 
+> **⚠️ Important:** `Name` field is required. 

ui/v2.5/src/docs/en/Manual/Tagger.md

@@ -4,9 +4,9 @@ Stash can be integrated with stash-box which acts as a centralized metadata data
 
 ## Searching 
 
-The fingerprint search matches your current selection of files against the remote stash-box instance. Any scenes with a matching fingerprint will be returned, although there is currently no validation of fingerprints so it’s recommended to double-check the validity before saving.
+The fingerprint search matches your current selection of files against the remote stash-box instance. Any scenes with a matching fingerprint will be returned, although there is currently no validation of fingerprints so it's recommended to double-check the validity before saving.
 
-If no fingerprint match is found it’s possible to search by keywords. The search works by matching the query against a scene’s _title_, _release date_, _studio name_, and _performer names_. By default the tagger uses metadata set on the file, or parses the filename, this can be changed in the config.
+If no fingerprint match is found it's possible to search by keywords. The search works by matching the query against a scene's _title_, _release date_, _studio name_, and _performer names_. By default the tagger uses metadata set on the file, or parses the filename, this can be changed in the config.
 
 An important thing to note is that it only returns a match *if all query terms are a match*. As an example, if a scene is titled `"A Trip to the Mall"` with the performer `"Jane Doe"`, a search for `"Trip to the Mall 1080p"` will *not* match, however `"trip mall doe"` would. Usually a few pieces of info is enough, for instance performer name + release date or studio name. To avoid common non-related keywords you can add them to the blacklist in the tagger config. Any items in the blacklist are stripped out of the query.