20250828 cleanup (#2639)

* Cleanup

* Refactor artifact management

site/content/apis/dmf_api.md

@@ -376,8 +376,8 @@ Example header and payload:
             "HTTPS":"https://download-from-url.com"
             },
         "hashes":{
-            "md5":"md5hash",
-            "sha1":"sha1hash"
+            "md5":"<md5 hash>",
+            "sha1":"<sha1 hash>"
             },
         "size":512
         }],
@@ -508,8 +508,8 @@ Example header and payload:
               "HTTPS":"https://download-from-url.com"
               },
           "hashes":{
-              "md5":"md5hash",
-              "sha1":"sha1hash"
+              "md5":"<md5 hash>",
+              "sha1":"<sha1 hash>"
               },
           "size":512
           }],
@@ -541,8 +541,8 @@ Example header and payload:
               "HTTPS":"https://download-from-url.com"
               },
           "hashes":{
-              "md5":"md5hash",
-              "sha1":"sha1hash"
+              "md5":"<md5 hash>",
+              "sha1":"<sha1 hash>" 
               },
           "size":512
           }],

site/content/guides/clustering.md

@@ -80,7 +80,7 @@ Add to your `pom.xml` :
 Every node is maintaining its own caches independent from other nodes. So there is no globally shared/synchronized cache
 instance within the cluster. In order to keep nodes in sync a TTL (time to live) can be set for all caches to ensure
 that after some time the cache is refreshed from the database. To enable the TTL just set the property "
-hawkbit.cache.global.ttl" (value in milliseconds). Of course you can implement a shared cache, e.g. Redis.
+hawkbit.cache.ttl" (value in milliseconds). Of course you can implement a shared cache, e.g. Redis.
 See [CacheAutoConfiguration](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-autoconfigure/src/main/java/org/eclipse/hawkbit/autoconfigure/cache/CacheAutoConfiguration.java)
 
 ## Schedulers