fix: update redact option name from redactFields to redact in documentation

fix #650

Author: CahidArda

qstash/howto/redact-fields.mdx

@@ -7,7 +7,7 @@ QStash messages can contain private data that you don't want visible in the Upst
 
 QStash allows you to redact specific fields so they appear as `REDACTED:<SHA256>` in the dashboard and API. The original values are still used when delivering messages to your endpoint. The SHA256 hash lets you verify the two data without revealing the original data.
 
-To redact a field, pass the `redactFields` option when publishing a message.
+To redact a field, pass the `redact` option when publishing a message.
 
 Available options:
 | Option | Description |
@@ -29,7 +29,7 @@ const client = new Client({ token: "<QSTASH_TOKEN>" });
 const res = await client.publishJSON({
   url: "https://my-api...",
   body: { hello: "world" },
-  redactFields: {
+  redact: {
     body: true,
     header: ["Authorization"] // or `header: true` to redact all headers
   },
@@ -45,7 +45,7 @@ client.message.publish_json(
     body={
         "hello": "world",
     },
-    redact_fields={
+    redact={
       "body": True,
       "header": ["Authorization"] // or `header: True` to redact all headers
     },
@@ -73,7 +73,7 @@ However, when you retry a DLQ message, QStash delivers the original values to yo
 
 ## Schedules
 
-You can also redact fields in schedules. Pass the `redactFields` option when creating a schedule, and all messages produced by that schedule will have the specified fields redacted.
+You can also redact fields in schedules. Pass the `redact` option when creating a schedule, and all messages produced by that schedule will have the specified fields redacted.
 Schedule get and list endpoints also apply redaction, so private data won't appear in API responses or the dashboard.
 
 <CodeGroup>
@@ -86,7 +86,7 @@ const res = await client.schedule.create({
   cron: "0 * * * *",
   url: "https://my-api...",
   body: { hello: "world" },
-  redactFields: {
+  redact: {
     body: true,
     header: ["Authorization"]
   },
@@ -102,7 +102,7 @@ client.schedule.create(
     cron="0 * * * *",
     url="https://my-api...",
     body={"hello": "world"},
-    redact_fields={
+    redact={
       "body": True,
       "header": ["Authorization"]
     },

workflow/howto/redact-fields.mdx

@@ -7,7 +7,7 @@ Workflow runs can contain private data that you don't want visible in the Upstas
 
 Upstash Workflow allows you to redact specific fields so they appear as `REDACTED:<SHA256>` in the dashboard and API. The original values are still used when delivering requests to your workflow endpoint. The SHA256 hash lets you verify the data without revealing the original values.
 
-To redact fields, pass the `redactFields` option when triggering a workflow run.
+To redact fields, pass the `redact` option when triggering a workflow run.
 
 Available options:
 | Option | Description |
@@ -29,7 +29,7 @@ const client = new Client({ token: "<QSTASH_TOKEN>" });
 const { workflowRunId } = await client.trigger({
   url: "https://my-app.com/api/workflow",
   body: { hello: "world" },
-  redactFields: {
+  redact: {
     body: true,
     header: ["Authorization"] // or `header: true` to redact all headers
   },
@@ -45,7 +45,7 @@ client.trigger(
     body={
         "hello": "world",
     },
-    redact_fields={
+    redact={
         "body": True,
         "header": ["Authorization"] // or `header: True` to redact all headers
     },