cleanup

Author: zspitzer

docs/03.reference/02.tags/application/_attributes/mappings.md

@@ -2,4 +2,4 @@ A structure that contains mappings. Each element in the structure consists of a
 
 The logical path is the key and the absolute path is the value.
 
-[[cookbook-filesystem-mapping-define-mapping]]
+[[mappings-how-to-define-a-reg-mapping]]

docs/04.guides/03.updating-lucee/chapter.md

@@ -10,8 +10,6 @@ Here you can find guides on how to update Lucee:
 
 [[updating-lucee-migrate-from-railo]]
 
-[[updating-lucee-update-from-railo]]
-
 [[updating-lucee-migrate-from-acf]]
 
 [[lucee-5-upgrading-lucee-45]]

docs/04.guides/04.cookbooks/chapter.md

@@ -7,7 +7,7 @@ id: cookbook
 
 Some basic examples
 
-* [[basic-date]]
+* [[cookbook-basic-date]]
 
 ## Application.cfc / Tag <cfapplication> ##
 
@@ -22,7 +22,7 @@ Lucee comes with a simple framework that let's you control the flow of your appl
 Lucee supports a lot of different cache systems, for example EhCache, Memcached, Infinispan, etc.. and you can use these caches in various scenarios:
 
 * [[caches-defined-in-application-cfc]]
-* [[cached-within-request]]
+* [[cache-a-query-for-the-curr-context]]
 * [[session-handling]]
 * [[list-existing-cache-conn]]
 
@@ -36,7 +36,7 @@ Lucee supports a lot of different cache systems, for example EhCache, Memcached,
 Some examples related to Datasources/Queries:
 
 * [[datasource-how-to-define-them]]
-* [[cached-within-request]]
+* [[cache-a-query-for-the-curr-context]]
 * Add a new Datasource driver (TODO)
 
 ## File System ##

docs/recipes/loop-through-files.md

@@ -1,15 +1,24 @@
----
-title: Looping Through Files
-id: loop_through_files
-related:
-- tag-loop
-categories:
-- files
-description: This document explains how to handle large files in Lucee more efficiently.
-keywords: Looping through files,cffile,fileRead,fileReadBinary,Memory optimization,Lucee
----
-
-
+<!--
+{
+	"title": "Looping Through Files",
+	"id": "loop_through_files",
+	"related": [
+		"tag-loop"
+	],
+	"categories": [
+		"files"
+	],
+	"description": "This document explains how to handle large files in Lucee more efficiently.",
+	"keywords": [
+		"Looping through files",
+		"cffile",
+		"fileRead",
+		"fileReadBinary",
+		"Memory optimization",
+		"Lucee"
+	]
+}
+-->
 
 # Looping Through File
 

docs/recipes/monitoring-enable-for-your-session.md

@@ -1,16 +1,20 @@
----
-title: Monitoring - Enable for your session
-id: monitoring-enable-for-your-session
-categories:
-- debugging
-- monitoring
-- session
-since: '6.1'
-description: Shows you a way to enable Monitoring for your session
-keywords: monitoring,session
----
-
-
+<!--
+{
+	"title": "Monitoring - Enable for your session",
+	"id": "monitoring-enable-for-your-session",
+	"categories": [
+		"debugging",
+		"monitoring",
+		"session"
+	],
+	"since": "6.1",
+	"description": "Shows you a way to enable Monitoring for your session",
+	"keywords": [
+		"monitoring",
+		"session"
+	]
+}
+-->
 
 # Monitoring - Enable for your session
 

docs/recipes/scheduler-quartz-clustering.md

@@ -1,17 +1,25 @@
----
-title: Quartz Scheduler Clustering
-id: clustering-quartz-scheduler
-related:
-- scheduler-quartz
-- tag-schedule
-categories:
-- extensions
-- recipes
-description: How to set up and configure clustering with the Quartz Scheduler extension
-keywords: scheduler,quartz,clustering,database,redis
----
-
-
+<!--
+{
+	"title": "Quartz Scheduler Clustering",
+	"id": "clustering-quartz-scheduler",
+	"related": [
+		"scheduler-quartz",
+		"tag-schedule"
+	],
+	"categories": [
+		"extensions",
+		"recipes"
+	],
+	"description": "How to set up and configure clustering with the Quartz Scheduler extension",
+	"keywords": [
+		"scheduler",
+		"quartz",
+		"clustering",
+		"database",
+		"redis"
+	]
+}
+-->
 
 # Clustering with Quartz Scheduler
 

docs/recipes/sql-types.md

@@ -208,4 +208,4 @@ LUCEE_QUERY_ALLOWEMPTYASNULL=true
 
 However, it's recommended to explicitly handle NULL values in your code for better clarity and to match Adobe ColdFusion behavior.
 
-See [[breaking-changes-6-0]] and [[lucee-5-to-6-migration-guide]] for more details.
+See [[breaking-changes-5-4-to-6-0]] and [[lucee-5-to-6-migration-guide]] for more details.

docs/recipes/tag-syntax.md

@@ -21,7 +21,7 @@
   "related": [
     "developing-with-lucee-server",
     "tag-script",
-    "tag"
+    "tags"
   ]
 }
 -->

docs/recipes/thread-usage.md

@@ -1,3 +1,26 @@
+<!--
+{
+  "title": "Complete Guide to Threading in Lucee",
+  "id": "thread-usage",
+  "categories": ["thread", "performance", "core"],
+  "description": "Complete guide to using threads and parallel execution in Lucee",
+  "keywords": [
+    "threads",
+    "parallel",
+    "async",
+    "concurrent",
+    "performance",
+    "cfthread"
+  ],
+  "related": [
+    "tag-thread",
+    "function-arrayeach",
+    "function-arraymap",
+    "function-arrayreduce"
+  ]
+}
+-->
+
 # Complete Guide to Threading in Lucee
 
 This document explains all the ways to use threads and parallel execution in Lucee. Threads allow you to execute code in parallel, improving performance for tasks like database queries, HTTP requests, or any long-running operations.

docs/recipes/websocket-extension.md

@@ -250,7 +250,7 @@ Function `getDataFromSomewhere()` is responsible for obtaining the data that nee
 
 ### Using webSocketInfo() to Send Message to Client
 
-[[function-websocketInfo]] also has an array of instances, one for each client call to a WebSocket Component. So, looping through the array gives you access to the component, and then you can call any of its functions.
+[[function-websocketinfo]] also has an array of instances, one for each client call to a WebSocket Component. So, looping through the array gives you access to the component, and then you can call any of its functions.
 
 For Example (_excluding role management functions_):