From 54f28d620a91b61b31091b2e3a56314bb9eca2a3 Mon Sep 17 00:00:00 2001 From: cynavi Date: Wed, 13 May 2026 10:00:58 +0545 Subject: [PATCH] docs(docs-infra): fix typo and malformed markdown bullet in angular-developer skill --- skills/dev-skills/angular-developer/SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/skills/dev-skills/angular-developer/SKILL.md b/skills/dev-skills/angular-developer/SKILL.md index f332e3e0878f..f93d9abbda63 100644 --- a/skills/dev-skills/angular-developer/SKILL.md +++ b/skills/dev-skills/angular-developer/SKILL.md @@ -17,7 +17,7 @@ metadata: ## Creating New Projects -If no guidelines are provided by the user, here are same default rules to follow when creating a new Angular project: +If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project: 1. Use the latest stable version of Angular unless the user specifies otherwise. 2. Use Signals Forms for form management in new projects (available in Angular v21 and newer) [Find out more](references/signal-forms.md). @@ -65,8 +65,8 @@ When managing state and data reactivity, use Angular Signals and consult the fol In most cases for new apps, **prefer signal forms**. When making a forms decision, analyze the project and consider the following guidelines: -- if the application is using v21 or newer and this is a new form, **prefer signal forms**. - -For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy. +- If the application is using v21 or newer and this is a new form, **prefer signal forms**. +- For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy. - **Signal Forms**: Use signals for form state management. Read [signal-forms.md](references/signal-forms.md) - **Template-driven forms**: Use for simple forms. Read [template-driven-forms.md](references/template-driven-forms.md)