From 3626b7358e0027cb8ac227c6aea8ce1f27335133 Mon Sep 17 00:00:00 2001
From: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
Date: Sun, 13 Nov 2022 13:30:17 -0600
Subject: [PATCH] Updated content based on feedback

Signed-off-by: Andre Wanlin <67169551+awanlin@users.noreply.github.com>
---
 docs/features/software-catalog/external-integrations.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/features/software-catalog/external-integrations.md b/docs/features/software-catalog/external-integrations.md
index f3387d31f0..66813cc4d2 100644
--- a/docs/features/software-catalog/external-integrations.md
+++ b/docs/features/software-catalog/external-integrations.md
@@ -159,10 +159,10 @@ Check out the numbered markings - let's go through them one by one.
    the outcome of that. This example issues a `fetch` to the right service and
    issues a full refresh of its entity bucket based on that.
 5. The method translates the foreign data model to the native `Entity` form, as
-   expected by the catalog. Make sure that in this method you include the
-   `backstage.io/managed-by-location` and `backstage.io/managed-by-origin-location`
-   annotations on your `Entity`. If these are not present they will not show up
-   in the Catalog and you will see warnings in your logs. The
+   expected by the catalog. The `Entity` must include the
+   `backstage.io/managed-by-location` and
+   `backstage.io/managed-by-origin-location annotations`; otherwise, it will not
+   appear in the Catalog and will generate warning logs. The
    [Well-known Annotations](./well-known-annotations.md#backstageiomanaged-by-location)
    documentation has guidance on what values to use for these.
 6. Finally, we issue a "mutation" to the catalog. This persists the entities in