From 4a9338cedd10b4dafea196ba142a1f16a8b46281 Mon Sep 17 00:00:00 2001
From: Su <112690947+sushmangupta@users.noreply.github.com>
Date: Wed, 24 Jan 2024 10:25:45 +0100
Subject: [PATCH] Update
 guides/integrations-api/general-concepts/partial-data-loading.md

---
 .../integrations-api/general-concepts/partial-data-loading.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guides/integrations-api/general-concepts/partial-data-loading.md b/guides/integrations-api/general-concepts/partial-data-loading.md
index 3184ce7dc..4194f3334 100644
--- a/guides/integrations-api/general-concepts/partial-data-loading.md
+++ b/guides/integrations-api/general-concepts/partial-data-loading.md
@@ -123,4 +123,4 @@ protected function defineFields(): FieldCollection
 
 ## Limitations
 
-The current limitation of the Partial Data loading is that it only works on the Entity level. Any custom responses like a product detail page or CMS in the Store API can't be used with this feature, as the Store API needs the whole entity to generate the response. If you need a small response, we recommend to use the [includes](./search-criteria.md#includes-apialias) feature of the Search API.
+The current limitation of the `partial data loading` is that it only works on the Entity level. Any custom responses like a product detail page or CMS in the Store API can't be used with this feature, as the Store API needs the whole entity to generate the response. If you need a small response, we recommend to use the [includes](./search-criteria.md#includes-apialias) feature of the Search API.