From a3a7a9d00105c8527682aa87e88854f82603489e Mon Sep 17 00:00:00 2001 From: Thomas Cardonne Date: Tue, 28 Apr 2026 22:03:45 +0200 Subject: [PATCH] docs(contribute): correct format issue in doc-style-guide.md Signed-off-by: Thomas Cardonne --- docs/contribute/doc-style-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contribute/doc-style-guide.md b/docs/contribute/doc-style-guide.md index 1e28ed4676..1d6438e68d 100644 --- a/docs/contribute/doc-style-guide.md +++ b/docs/contribute/doc-style-guide.md @@ -361,7 +361,7 @@ A list of Backstage-specific terms and words to be used consistently across the site. | Term | Usage | -| :----------------- | :------------------------------------------------------------------------------------------------------------------------------------- | --- | +| :----------------- | :------------------------------------------------------------------------------------------------------------------------------------- | | Backstage | Always capitalized. | | plugin | Lowercase when referring to the concept. Use code style when referring to a specific package, for example `@backstage/plugin-catalog`. | | Software Catalog | Capitalized as a product name. Use "catalog" (lowercase) when referring to the concept generically. | @@ -370,4 +370,4 @@ the site. | Scaffolder | Capitalized as a product name. | | app-config | Use code style: `app-config.yaml`. | | open source | Two words, lowercase (unless starting a sentence). | -| backend system | Lowercase when referring to the Backstage backend framework. | | +| backend system | Lowercase when referring to the Backstage backend framework. |