From c710467ba2fa3c95cb322ed51d49506f7443ff26 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Mon, 31 Jan 2022 10:06:45 +0100 Subject: [PATCH] fix callouts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Fredrik Adelöw --- docs/features/software-catalog/api.md | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/docs/features/software-catalog/api.md b/docs/features/software-catalog/api.md index 74fdd55fca..71e229651a 100644 --- a/docs/features/software-catalog/api.md +++ b/docs/features/software-catalog/api.md @@ -12,12 +12,8 @@ by external systems. This page describes its shape and features. The API surface consists of a few distinct groups of functionality. Each has a dedicated section below. -{% note %} - -**Note:** This page only describes some of the most commonly used parts of the -API, and is a work in progress. - -{% endnote %} +> **Note:** This page only describes some of the most commonly used parts of the +> API, and is a work in progress. All of the URL paths in this article are assumed to be on top of some base URL pointing at your catalog installation. For example, if the path given in a @@ -199,13 +195,9 @@ error if there was no entity with that UID. Deletes an entity by its `metadata.uid` field value. -{% note %} - -**Note:** This method of deletion is appropriate for orphaned entities, but not -for removal of "live" entities that are actively being updated by a location. -Please read below. - -{% endnote %} +> **Note:** This method of deletion is appropriate for orphaned entities, but +> not for removal of "live" entities that are actively being updated by a +> location. Please read below. The most common user flow is that you register a location (see below), and then the catalog keeps itself up to date with that location and the subtree of things