Update Blog “integrating-hpe-greenlake-webhooks-with-splunk”

Author: Didier-Lalli

content/blog/integrating-hpe-greenlake-webhooks-with-splunk.md

@@ -46,7 +46,7 @@ The [HTTP Event Collector (HEC)](https://dev.splunk.com/enterprise/docs/devtools
 
 HPE GreenLake implements robust security measures to ensure webhook authenticity:
 
-* Challenge Request Validation: After registering a webhook, a verification challenge is sent to the destination (the webhook URL). The event type is hpe.greenlake.events.v1beta1.webhooks.verification. The challenge request includes a unique, random string generated by the server that is sent in the body as a payload.
+* Challenge Request Validation: After registering a webhook, a verification challenge is sent to the destination (the webhook URL). The event type is `hpe.greenlake.events.v1beta1.webhooks.verification`. The challenge request includes a unique, random string generated by the server that is sent in the body as a payload.
 * HMAC SHA-256 Signature Verification: HPE GreenLake webhooks use a verification challenge process to ensure that webhook connections are legitimate and secure. HPE GreenLake secures webhook notifications through HMAC (Hash-based Message Authentication Code) with SHA-256, a cryptographic hashing algorithm.
 * Shared Secret Management: The platform supports dual secret rotation for zero-downtime security updates.
 
@@ -68,7 +68,7 @@ Challenge Request Example:
 
 ## Challenges and solutions
 
-The primary challenge in integrating HPE GreenLake webhooks with Splunk HEC lies in the webhook verification process. The destination must read the value from the challengeRequest field and create an HMAC SHA-256 hash, using the webhook secret as salt and the challengeRequest value as a string to hash. When successful, the destination responds with a JSON object with the format {"verification": "CREATED_HASH"} and a HTTP 200 OK status.
+The primary challenge in integrating HPE GreenLake webhooks with Splunk HEC lies in the webhook verification process. The destination must read the value from the challengeRequest field and create an HMAC SHA-256 hash, using the webhook secret as salt and the challengeRequest value as a string to hash. When successful, the destination responds with a JSON object with the format `{"verification": "CREATED_HASH"}` and a HTTP 200 OK status.
 
 ### A challenge
 
@@ -331,7 +331,6 @@ The complete integration flow works as follows:
 > Note: See [this blog](https://developer.hpe.com/blog/getting-started-with-the-hpe-greenlake-cloud-eventing-framework/) to learn how to register a new webhook handler in HPE GreenLake
 
 2. Webhook handler verification process
-
 3. Event processing flow
 
 * HPE GreenLake sends event data to the custom handler endpoint.