From 4339af9f4228e7a77e0d52a40a79f20a84024a97 Mon Sep 17 00:00:00 2001
From: Andy Stark <30621568+therealandeeee@users.noreply.github.com>
Date: Fri, 5 Apr 2019 17:24:06 +0100
Subject: [PATCH] [ADF-4285] Removed incorrect example from content metadata
 docs (#4564)

---
 .../content-metadata-card.component.md        | 24 ++-----------------
 1 file changed, 2 insertions(+), 22 deletions(-)

diff --git a/docs/content-services/components/content-metadata-card.component.md b/docs/content-services/components/content-metadata-card.component.md
index 830900e10b..2b73654d7c 100644
--- a/docs/content-services/components/content-metadata-card.component.md
+++ b/docs/content-services/components/content-metadata-card.component.md
@@ -255,9 +255,9 @@ Futhermore, you can also exclude specific aspects by adding the `exclude` proper
 },
 ```
 
-When using this configuration you can still whitelist aspects and properties as you desire. Let's see more complex examples for each of the config layouts:
+When using this configuration you can still whitelist aspects and properties as you desire. The
+example below shows this with an aspect-oriented config:
 
-##### Aspect oriented config
 ```json
 "content-metadata": {
     "presets": {
@@ -270,26 +270,6 @@ When using this configuration you can still whitelist aspects and properties as
 },
 ```
 
-##### Layout oriented config
-```json
-"content-metadata": {
-    "presets": {
-        "robot-images": [
-            {
-                "includeAll": true,
-                "exclude": ["cm:content", "exif:exif"]
-            },
-            {
-                "title": "Robot Group",
-                "items": [
-                    { "aspect": "exif:exif", "properties": [ "exif:pixelXDimension", "exif:pixelYDimension"] }
-                ] 
-            }
-        ]
-    }
-},
-```
-
 ## What happens when there is a whitelisted aspect in the config but the given node doesn't relate to that aspect
 
 Nothing - since this aspect is not related to the node, it will simply be ignored and not