From 652a4014254eef3910d1567a8aa938d1a66f2e52 Mon Sep 17 00:00:00 2001 From: Arjen Bax Date: Mon, 2 Sep 2024 13:04:51 +0200 Subject: [PATCH] Fix typos --- docs/guides/how-to/create-a-custom-field.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/how-to/create-a-custom-field.md b/docs/guides/how-to/create-a-custom-field.md index 04f0b49c55..ae608ae472 100644 --- a/docs/guides/how-to/create-a-custom-field.md +++ b/docs/guides/how-to/create-a-custom-field.md @@ -144,7 +144,7 @@ Then we follow the steps below: tracking interaction states etc. > N.B. Make sure you never override other property getters than the one mentioned in this tutorial, -> because those properties will loose their reactivity (they won't be considered anymore in the +> because those properties will lose their reactivity (they won't be considered anymore in the > update loop of LitElement). > Whenever a .modelValue/.formattedValue/.serializedValue needs to be computed, use > [parser/formatter/serializer](../../docs/../fundamentals/systems/form/formatting-and-parsing.md) @@ -194,7 +194,7 @@ export const createAField = () => { That was all! Now that your .modelValue is connected your component is fully compatible with our form system -> Is your `.modelValue` still undefined? Please make sure you're `.value` is of type 'string'. +> Is your `.modelValue` still undefined? Please make sure your `.value` is of type 'string'. Now you can enhance your slider by writing custom Validators for it or by writing a parser to get a custom modelValue type.