move from code blocks to comments to be prettier compliant

hdbjeff · hdbjeff · commit 0dbc93694bdb · 2025-11-26T19:21:27.000-08:00
diff --git a/docs/developers/applications/caching.md b/docs/developers/applications/caching.md
@@ -38,28 +38,24 @@ You can provide a single expiration and it defines the behavior for all three. Y
 
 `expiration` = 1 hour with default `scanInterval` (15 minutes, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-00:15  
-00:30  
-00:45  
-01:00  
-... continuing every 15 minutes ...
-```
+> 00:00  
+> 00:15  
+> 00:30  
+> 00:45  
+> 01:00  
+> ... continuing every 15 minutes ...
 
 If the server starts at 12:05 it does not run eviction at 12:20 or “15 minutes after startup.” Instead, the next scheduled anchor is 12:15, then 12:30, 12:45, 13:00, etc. The schedule is clock-aligned, not startup-aligned.
 
 #### Example: 1-Day Expiration
 
 `expiration` = 1 day with default `scanInterval` (6 hours, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-06:00  
-12:00  
-18:00
-... continuing every 6 hours ...
-```
+> 00:00  
+> 06:00  
+> 12:00  
+> 18:00  
+> ... continuing every 6 hours ...
 
 If the server starts at 12:05 the next matching eviction time is 18:00 the same day, then 00:00, 06:00, 12:00, 18:00, etc. If the server starts at 19:30 the schedule does not shift. Instead, the next anchor time is 00:00, and the regular 6-hour cycle continues.
 
diff --git a/versioned_docs/version-4.5/developers/applications/caching.md b/versioned_docs/version-4.5/developers/applications/caching.md
@@ -38,28 +38,24 @@ You can provide a single expiration and it defines the behavior for all three. Y
 
 `expiration` = 1 hour with default `scanInterval` (15 minutes, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-00:15  
-00:30  
-00:45  
-01:00  
-... continuing every 15 minutes ...
-```
+> 00:00  
+> 00:15  
+> 00:30  
+> 00:45  
+> 01:00  
+> ... continuing every 15 minutes ...
 
 If the server starts at 12:05 it does not run eviction at 12:20 or “15 minutes after startup.” Instead, the next scheduled anchor is 12:15, then 12:30, 12:45, 13:00, etc. The schedule is clock-aligned, not startup-aligned.
 
 #### Example: 1-Day Expiration
 
 `expiration` = 1 day with default `scanInterval` (6 hours, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-06:00  
-12:00  
-18:00
-... continuing every 6 hours ...
-```
+> 00:00  
+> 06:00  
+> 12:00  
+> 18:00  
+> ... continuing every 6 hours ...
 
 If the server starts at 12:05 the next matching eviction time is 18:00 the same day, then 00:00, 06:00, 12:00, 18:00, etc. If the server starts at 19:30 the schedule does not shift. Instead, the next anchor time is 00:00, and the regular 6-hour cycle continues.
 
diff --git a/versioned_docs/version-4.6/developers/applications/caching.md b/versioned_docs/version-4.6/developers/applications/caching.md
@@ -38,28 +38,24 @@ You can provide a single expiration and it defines the behavior for all three. Y
 
 `expiration` = 1 hour with default `scanInterval` (15 minutes, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-00:15  
-00:30  
-00:45  
-01:00  
-... continuing every 15 minutes ...
-```
+> 00:00  
+> 00:15  
+> 00:30  
+> 00:45  
+> 01:00  
+> ... continuing every 15 minutes ...
 
 If the server starts at 12:05 it does not run eviction at 12:20 or “15 minutes after startup.” Instead, the next scheduled anchor is 12:15, then 12:30, 12:45, 13:00, etc. The schedule is clock-aligned, not startup-aligned.
 
 #### Example: 1-Day Expiration
 
 `expiration` = 1 day with default `scanInterval` (6 hours, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-06:00  
-12:00  
-18:00
-... continuing every 6 hours ...
-```
+> 00:00  
+> 06:00  
+> 12:00  
+> 18:00  
+> ... continuing every 6 hours ...
 
 If the server starts at 12:05 the next matching eviction time is 18:00 the same day, then 00:00, 06:00, 12:00, 18:00, etc. If the server starts at 19:30 the schedule does not shift. Instead, the next anchor time is 00:00, and the regular 6-hour cycle continues.
 
diff --git a/versioned_docs/version-4.7/developers/applications/caching.md b/versioned_docs/version-4.7/developers/applications/caching.md
@@ -38,28 +38,24 @@ You can provide a single expiration and it defines the behavior for all three. Y
 
 `expiration` = 1 hour with default `scanInterval` (15 minutes, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-00:15  
-00:30  
-00:45  
-01:00  
-... continuing every 15 minutes ...
-```
+> 00:00  
+> 00:15  
+> 00:30  
+> 00:45  
+> 01:00  
+> ... continuing every 15 minutes ...
 
 If the server starts at 12:05 it does not run eviction at 12:20 or “15 minutes after startup.” Instead, the next scheduled anchor is 12:15, then 12:30, 12:45, 13:00, etc. The schedule is clock-aligned, not startup-aligned.
 
 #### Example: 1-Day Expiration
 
 `expiration` = 1 day with default `scanInterval` (6 hours, one quarter of `expiration`). This creates the following fixed eviction schedule:
 
-```
-00:00  
-06:00  
-12:00  
-18:00
-... continuing every 6 hours ...
-```
+> 00:00  
+> 06:00  
+> 12:00  
+> 18:00  
+> ... continuing every 6 hours ...
 
 If the server starts at 12:05 the next matching eviction time is 18:00 the same day, then 00:00, 06:00, 12:00, 18:00, etc. If the server starts at 19:30 the schedule does not shift. Instead, the next anchor time is 00:00, and the regular 6-hour cycle continues.
 
