diff options
author | StefanVukovic99 <stefanvukovic44@gmail.com> | 2024-05-27 16:48:11 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-27 14:48:11 +0000 |
commit | 3c5df23e67a6010fb3ea7214efd1291daef7f2b1 (patch) | |
tree | 97b9a36e59b758115e7266ac952e39cd80a0c8fe | |
parent | d6aa6737821f5db61e932714322f2401f86b5200 (diff) |
remove extra word (#1001)
Signed-off-by: StefanVukovic99 <stefanvukovic44@gmail.com>
-rw-r--r-- | docs/development/language-features.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/development/language-features.md b/docs/development/language-features.md index 239fab88..9268d4ca 100644 --- a/docs/development/language-features.md +++ b/docs/development/language-features.md @@ -225,7 +225,7 @@ However, the only `conditionOut` of this rule, `n`, does not match any `conditio }, ``` -Now the rules will chain together, as shown in the image. Chaining is can be very useful (for agglutinative languages it is indispensable), but may cause unexpected behavior. For example, `boss` will now display results for the word `bo` (e.g. the staff) with the `plural` rule applied twice, i.e. it can chain with itself because the `conditionsIn` and `conditionsOut` are the same. This leads us to the actual implementation of the `plural` rule in `english-transforms.js`: +Now the rules will chain together, as shown in the image. Chaining can be very useful (for agglutinative languages it is indispensable), but may cause unexpected behavior. For example, `boss` will now display results for the word `bo` (e.g. the staff) with the `plural` rule applied twice, i.e. it can chain with itself because the `conditionsIn` and `conditionsOut` are the same. This leads us to the actual implementation of the `plural` rule in `english-transforms.js`: ```js conditions: { |