fix(docs): restore source admonition blocks

- purpose: restore real admonition components in source storage docs that were flattened during the broader i18n structure cleanup
- before: short tip and caution sections in cache pool guidance and the XFS repair partial were rendered as plain bold paragraphs instead of Docusaurus admonitions
- problem: the change weakened visual emphasis and dropped important formatting like the explicit Maintenance Mode reference in the parity warning
- change: convert the example and use-case callouts in cache-pools back to :::tip blocks and restore the XFS parity warning to a :::caution block
- result: source docs keep the intended admonition styling while translation-side syntax repairs remain unchanged

Author: elibosley

docs/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx

@@ -273,7 +273,11 @@ Rebuilding can take some time, depending on the size of the disk and the current
 
 Setting a minimum free space for your %%cache pool|cache-pool%% can provide better control over file placement, especially when dealing with large files like high-resolution videos. This setting helps Unraid know when to stop writing to the pool and start writing directly to the larger storage %%array|array%%, avoiding interruptions or data corruption.
 
-**Example:** If you often download files around 10 GB, set the minimum free space to at least 10 GB, but ideally 20 GB to allow for adjustments.
+:::tip[Example]
+
+If you often download files around 10 GB, set the minimum free space to at least 10 GB, but ideally 20 GB to allow for adjustments.
+
+:::
 
 You can access Minimum free space by clicking on the pool name in the **Main** tab and going to **Individual Pool Settings**.
 
@@ -285,7 +289,11 @@ You can access Minimum free space by clicking on the pool name in the **Main** t
 - If set to use a %%cache pool|cache-pool%% exclusively (no **Secondary storage**), this setting is not applied.
 - If set to use only the %%array|array%% as **Primary storage**, files go straight to the %%array|array%%.
 
-**Use case example:** Media share has the floor set to 20GB, which is appropriate for the files in that share. However, if you also use the pool for a VM and want to leave a cushion in case the vdisk grows, you could set the pool floor to 50GB. This way, any transfer to the Media share after the pool has less than 50GB free would go directly to the array.
+:::tip[Use case example]
+
+Media share has the floor set to 20GB, which is appropriate for the files in that share. However, if you also use the pool for a VM and want to leave a cushion in case the vdisk grows, you could set the pool floor to 50GB. This way, any transfer to the Media share after the pool has less than 50GB free would go directly to the array.
+
+:::
 
 :::tip[Best practice]
 

docs/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdx

@@ -4,4 +4,8 @@
 - If you're prompted to use `-L`, re-run the command like this: `xfs_repair -L /dev/mdXp1`. This is usually safe and necessary to complete the repair.
 - For drives that are not part of the %%array|array%%: `xfs_repair /dev/sdX1`.
 
-**Caution:** Running this command on an %%array|array%% disk outside of maintenance mode will invalidate parity.
+:::caution
+
+Running this command on an %%array|array%% disk outside of **%%Maintenance Mode|maintenance-mode%%** will invalidate parity.
+
+:::