From aa3baabc61d69075eeeb4eae04f813ba72dc8ff9 Mon Sep 17 00:00:00 2001 From: Deepthi Ajith Date: Tue, 5 Aug 2025 15:54:50 +0530 Subject: [PATCH] Minor documentation changes Signed-off-by: Deepthi Ajith --- docs/features/software-templates/writing-templates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/software-templates/writing-templates.md b/docs/features/software-templates/writing-templates.md index eeaa4ad203..096cfdfa2f 100644 --- a/docs/features/software-templates/writing-templates.md +++ b/docs/features/software-templates/writing-templates.md @@ -315,7 +315,7 @@ your first set of parameter fields would be shown. The same goes for the nested spec. Make sure to use the key `backstage:featureFlag` in your templates if you want to use this functionality. -Feature Flags cannot be used in `spec.steps[].if`(the conditional on whether to execute an step/action). But you can use feature flags to display parameters that allow for skipping steps. +Feature Flags cannot be used in `spec.steps[].if`(the conditional on whether to execute a step/action). But you can use feature flags to display parameters that allow for skipping steps. ```yaml spec: @@ -749,7 +749,7 @@ Have in mind that changes in this form will not be saved on the template and is ### Custom Field Explorer -The custom filed explorer allows you to select any custom field loaded on the backstage instance and test different values and configurations. +The custom field explorer allows you to select any custom field loaded on the backstage instance and test different values and configurations. ## Presentation