From 3c946d6609a7cbc78a3d8967a2babc587a2651bb Mon Sep 17 00:00:00 2001 From: Lianghua Date: Mon, 13 Jan 2025 11:05:36 +0800 Subject: [PATCH] Update http-events-api.mdx Fix error markdown table syntax --- src/content/docs/zaraz/http-events-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/zaraz/http-events-api.mdx b/src/content/docs/zaraz/http-events-api.mdx index 1cf68e7a57ca34a..96c19f606b7f56f 100644 --- a/src/content/docs/zaraz/http-events-api.mdx +++ b/src/content/docs/zaraz/http-events-api.mdx @@ -107,7 +107,7 @@ For each Event Object in your payload, Zaraz will respond with a Result Object. Depending on what tools you are loading using Zaraz, the body of the response coming from the API might include information you will want to process. This is because some tools do not have a complete server-side implementation and still depend on cookies, client-side JavaScript or similar mechanisms. Each Result Object can include the following information: | Result key | Description | -| --- | --- | --- | +| --- | --- | | `fetch` | Fetch requests that tools want to send from the user browser. | | `execute` | JavaScript code that tools want to execute in the user browser. | | `return` | Information that tools return. |