Skip to content

Commit 31430a6

Browse files
kaygeeapkozlowski-opensource
authored andcommitted
docs: fix grammatical error in template binding documentation (angular#58491)
This update corrects a grammatical error in the "CSS style properties" section of the template binding documentation. The sentence "You must create a new object instance when you modify these values in order to Angular to apply any updates" was updated to read correctly as "You must create a new object instance when you modify these values in order for Angular to apply any updates." This clarification helps improve readability and ensures the documentation communicates instructions accurately for readers. PR Close angular#58491
1 parent 4ef11c9 commit 31430a6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

adev/src/content/guide/templates/binding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ In the example above, Angular renders the `ul` element with all three CSS classe
172172

173173
Angular does not guarantee any specific order of CSS classes on rendered elements.
174174

175-
When binding `class` to an array or an object, Angular compares the previous value to the current value with the triple-equals operator (`===`). You must create a new object or array instance when you modify these values in order to Angular to apply any updates.
175+
When binding `class` to an array or an object, Angular compares the previous value to the current value with the triple-equals operator (`===`). You must create a new object or array instance when you modify these values in order for Angular to apply any updates.
176176

177177
If an element has multiple bindings for the same CSS class, Angular resolves collisions by following its style precedence order.
178178

0 commit comments

Comments
 (0)