From aa28d88e6c3311a692ef9dfacc3cac7dbae4ac2f Mon Sep 17 00:00:00 2001
From: "shopify-dev-bot[bot]"
 <95105344+shopify-dev-bot[bot]@users.noreply.github.com>
Date: Fri, 3 Jan 2025 19:00:08 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=A4=96=20Sync=20Liquid=20Docs=20Schema?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 data/objects.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/objects.json b/data/objects.json
index 8b707ce..d1f90d0 100644
--- a/data/objects.json
+++ b/data/objects.json
@@ -9880,7 +9880,7 @@
     "examples": [
       {
         "name": "Access metafields",
-        "description": "The access path for metafields consists of two layers:\n\n- namespace - A grouping of metafields to prevent conflicts.\n- key - The metafield name.\n\nGiven this, you can access the metafield object with the following syntax:\n\n```liquid\n{{ resource.metafields.namespace.key }}\n```\n",
+        "description": "The access path for metafields consists of two layers:\n\n- namespace - A grouping of metafields to prevent conflicts.\n- key - The metafield name.\n\nGiven this, you can access the metafield object with the following syntax:\n\n```liquid\n{{ resource.metafields.namespace.key }}\n```\n\n&gt; Note:\n&gt; The namespace and key values will always be `snake_case`, regardless of the casing used in the metafield definition.\n",
         "syntax": "",
         "path": "/products/health-potion",
         "raw_liquid": "Type: {{ product.metafields.information.directions.type }}\nValue: {{ product.metafields.information.directions.value }}",