docs: explain why not to fetch lazy loaded data server side

Author: mateuszo

docs/content/guides/6.best-practices/2.data-fetching.md

@@ -29,11 +29,11 @@ Animation below visualizes the difference between server and client side fetchin
 
 The rule of thumb is: _always use server-side fetching except for_:
 
-- **lazy loaded data** - data that is not visible immediately on page load. For example:
+- **lazy loaded data** - data that is not visible immediately on page load and can be removed from server-side rendered html to reduce its size. For example:
   - product reviews should appear only when user clicks expand on the “reviews accordion”
   - content below the fold is fetched on scroll
 
-- **personalized data** - data that is different for each user or group. Fetching such data server side would not only cause flickering but also might cause problem with caching (read more about caching). For example:
+- **personalized data** - data that is different for each user or group. Fetching such data server side would not only cause flickering but also might cause problem with caching ([read more about caching](/storefront/features/cdn/making-ssr-cacheable)). For example:
   - pricing data might be different for each customer group
   - product recommendations are based on individual user’s journey
   - cart content is specific for each user