feat(cockpit-k8s): neda review fix typos & inconsistencies logs doc

Author: nerda-codes

observability/cockpit/how-to/send-log-from-k8s-to-cockpit.mdx

@@ -22,17 +22,17 @@ We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8
  - A Scaleway account logged into the [console](https://console.scaleway.com)
  - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
  - [Created](/observability/cockpit/how-to/create-external-data-sources/) a custom external data source of the [logs type](/observability/cockpit/concepts/#data-types)
- - [Created](/observability/cockpit/how-to/create-token/) a Cockpit token for the same region as the data source
+ - [Created](/observability/cockpit/how-to/create-token/) a Cockpit token in the same region as the logs data source
  - A running Kubernetes cluster containing your application deployed
  - [Created](/identity-and-access-management/iam/how-to/create-api-keys/) an API key and retrieved your API secret key
 
 <Message type="important">
-  - Sending logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+  - Sending logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) page for more information.
 </Message>
 
 ## Configure the Helm chart
 
-Create a `values.yml` file to configure your Helm chart, using the example below. Make sure that you replace `$SCW_CLUSTER_NAME` with the name of your Scaleway Kubernetes cluster, `$COCKPIT_CUSTOM_DATASOURCE_HOST` with the URL of your custom data source (you can find it under the "API URL" section in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console), and `$COCKPIT_TOKEN` with your Cockpit token.
+Create a `values.yml` file to configure your Helm chart, using the example below. Make sure that you replace `$SCW_CLUSTER_NAME` with the name of your Scaleway Kubernetes cluster, `COCKPIT_CUSTOM_LOGS_DATASOURCE_URL` with the URL of your custom logs data source (you can find it under the "API URL" section in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console), and `$COCKPIT_TOKEN` with your Cockpit token.
 
 ```yaml
 cluster:
@@ -100,7 +100,6 @@ Once you have configured your `values.yml` file, you can use Helm to deploy the
     ```
     helm list
     ```
-    You should see a list of all the Helm releases in your cluster, including `my-log-ingester`.
 
 ## Send Kubernetes logs using Helm chart with Terraform
 
@@ -113,7 +112,7 @@ You can also use Terraform to manage and deploy Helm charts, providing you with
       host = your_k8s_cluster_host # The URL of your Kubernetes API server.
       token = your_k8s_cluster_token # Authentication token to access the cluster.
       cluster_ca_certificate = base64decode(
-      your_k8s_cluster_ca_certificate # The cluster's CA certificate, base64 encoded.
+      your_k8s_cluster_ca_certificate # The cluster's CA certificate.
       )
     }
   }