From c546f031347db88a499c492c9b4f0b175f3dc526 Mon Sep 17 00:00:00 2001 From: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> Date: Mon, 16 Feb 2026 10:31:34 -0500 Subject: [PATCH] Correct capitalization in update-a-component.md Changed software catalog to Software Catalog Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> --- docs/getting-started/update-a-component.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started/update-a-component.md b/docs/getting-started/update-a-component.md index 588f8d137c..ffe21bc8b3 100644 --- a/docs/getting-started/update-a-component.md +++ b/docs/getting-started/update-a-component.md @@ -8,7 +8,7 @@ Audience: Developers ## Overview -Components in the software catalog are created using a software template. The template generates a `catalog-info.yaml` file in either GitHub or GitLab that defines the entity. To update the component, you must edit its corresponding `catalog-info.yaml` entity definition file. +Components in the Software Catalog are created using a software template. The template generates a `catalog-info.yaml` file in either GitHub or GitLab that defines the entity. To update the component, you must edit its corresponding `catalog-info.yaml` entity definition file. ## Updating the component @@ -28,6 +28,6 @@ To update a component using the Backstage UI: 3. Select `Commit changes` to commit your changes to the appropriate branch and go through your normal PR review procedure. -4. Once the updated `catalog-info.yaml` file has been merged into the branch associated with the component, then you will see the updated information in the software catalog. +4. Once the updated `catalog-info.yaml` file has been merged into the branch associated with the component, then you will see the updated information in the Software Catalog. ![updated component name in ui](../assets/uiguide/updated-component-name-in-ui.png)