Update Scaler.md

content/docs/2.14/operate/setupscaler.md

@@ -1,3 +1,6 @@
+Yes, you can use code blocks to display the output instead of images. This can make the documentation more readable and easier to maintain. Here's how you can update the guide to use code blocks:
+
+```markdown
 +++
 title = "Setupscaler"
 weight = 500
@@ -67,7 +70,10 @@ Once you have created the `ScaledObject` configuration file, apply it to your Ku
    kubectl apply -f scaledobject.yaml
    ```
 
-   ![alt text](/static/img/scalers/cron/image-4.png)
+   ```plaintext
+   scaledobject.keda.sh/<scaled-object-name> created
+   ```
+
 3. Verify that the `ScaledObject` has been created successfully by running:
 
    ```bash
@@ -76,7 +82,10 @@ Once you have created the `ScaledObject` configuration file, apply it to your Ku
 
    This should display the `ScaledObject` you just created.
 
-   ![ScaledObject Created](/static/img/scalers/cron/image-2.png)
+   ```plaintext
+   NAME              SCALETARGETKIND   SCALETARGETNAME   MIN   MAX   TRIGGERS   AUTHENTICATION   READY   ACTIVE   FALLBACK   AGE
+   <scaled-object-name>   Deployment        <deployment-name>   1     10    cpu                    <none>            True    False    <none>      10s
+   ```
 
 After applying the `ScaledObject` configuration, KEDA will start monitoring the specified event source and scale your application accordingly, based on the configurations you provided.
 
@@ -92,7 +101,10 @@ You can monitor the scaling events and logs generated by KEDA using the followin
 
    This will show you the current state of your `ScaledObject` and the number of replicas.
 
-   ![List of ScaledObjects](/static/img/scalers/cron/image-2.png)
+   ```plaintext
+   NAME              SCALETARGETKIND   SCALETARGETNAME   MIN   MAX   TRIGGERS   AUTHENTICATION   READY   ACTIVE   FALLBACK   AGE
+   <scaled-object-name>   Deployment        <deployment-name>   1     10    cpu                    <none>            True    False    <none>      10s
+   ```
 
 2. View the logs of the KEDA operator:
 
@@ -102,4 +114,6 @@ You can monitor the scaling events and logs generated by KEDA using the followin
 
    The KEDA operator logs will show you detailed information about scaling events, decisions made by KEDA based on the event source, and any errors or warnings.
 
-   ![KEDA Operator Logs](/static/img/scalers/cron/image-3.png)
+   ```plaintext
+   {"level":"info","ts":<timestamp>,"logger":"scalehandler","msg":"Successfully scaled deployment","scaledobject.Namespace":"<namespace>","scaledobject.Name":"<scaled-object-name>","scaler":<scaler-type>}
+   ```