docs: deprecate cl-config in favor of Butane

Signed-off-by: Mathieu Tortuyaux <[email protected]>

Author: tormath1

content/docs/latest/provisioning/cl-config/_index.md

@@ -1,13 +1,14 @@
 ---
-title: Container Linux Config Transpiler
-linktitle: Container Linux Config Transpiler
+title: "[DEPRECATED / EOL] Container Linux Config Transpiler"
 description: YAML configuration format used to generate Ignition configs.
 weight: 20
 aliases:
     - ../os/provisioning
     - ../reference/migrating-to-clcs/provisioning
 ---
 
+:warning: TL; DR: Use [Butane](../config-transpiler). While Flatcar does support both Ignition spec version (2.x and 3.x), we encourage folks to use [Butane](../config-transpiler) first but we still maintain / document backward compatibility for users who still rely on Ignition 2.x. :warning:
+
 Flatcar Container Linux automates machine provisioning with a specialized system for applying initial configuration. This system implements a process of (trans)compilation and validation for machine configs, and an atomic service to apply validated configurations to machines.
 
 ## Container Linux Config

content/docs/latest/provisioning/config-transpiler/_index.md

@@ -19,7 +19,7 @@ The resulting Ignition config is very much not intended to be human-friendly. It
 [butane]: https://github.com/coreos/butane/
 [ignition]: https://github.com/coreos/ignition
 
-**Note:**: Butane is utilized to generate Ignition v3+ configurations. If you are still utilizing a version of Container Linux that requires Ignition v2, you can refer to the [Container Linux Config Transpiler][cl-config] documentation. This particularly applies to those using the current LTS releases.
+**Note:** Butane is utilized to generate Ignition v3+ configurations. If you are still utilizing a version of Container Linux that requires Ignition v2, you can refer to the [Container Linux Config Transpiler][cl-config] documentation.
 
 ## Why a two-step process?