From 73b999510b5a6ec0e216669e4b76ef6b4b56553f Mon Sep 17 00:00:00 2001 From: dancer1325 Date: Mon, 12 Aug 2024 20:19:41 +0200 Subject: [PATCH] doc(docs.features.softwareCatalog.systemModel): fix typo Signed-off-by: dancer1325 --- docs/features/software-catalog/system-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/software-catalog/system-model.md b/docs/features/software-catalog/system-model.md index ee7270a960..b93dde37d2 100644 --- a/docs/features/software-catalog/system-model.md +++ b/docs/features/software-catalog/system-model.md @@ -50,7 +50,7 @@ components need to be in a known machine-readable format so we can build further tooling and analysis on top. APIs have a visibility: they are either public (making them available for any -other component to consume), restricted (only available to an allowlisted set of +other component to consume), restricted (only available to an allowed set of consumers), or private (only available within their system). As public APIs are going to be the primary way interaction between components, Backstage supports documenting, indexing and searching all APIs so we can browse them as