From 753d6681ffc9e9d6bc95d4e08821c9b717a62ed4 Mon Sep 17 00:00:00 2001 From: Christopher Kolstad Date: Wed, 30 Nov 2022 10:33:42 +0100 Subject: [PATCH] fix typo in preferred-form-architecture (#2566) A very quick typo fix. It's whether, not wheter. :) --- .../contributing/ADRs/front-end/preferred-form-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/contributing/ADRs/front-end/preferred-form-architecture.md b/website/docs/contributing/ADRs/front-end/preferred-form-architecture.md index 766b42390a..6352c6dd71 100644 --- a/website/docs/contributing/ADRs/front-end/preferred-form-architecture.md +++ b/website/docs/contributing/ADRs/front-end/preferred-form-architecture.md @@ -14,4 +14,4 @@ We have decided to architecture our forms in the following way: * Create a reusable form component that does not contain any logic * Create separate Create and Edit components that use the form component and the form hook to create the form and implements it's own logic for submitting the form. -In this way, we keep as much of the form as possible DRY, but we avoid passing state internally in the form so the form doesn't need to know wheter it is in create or edit mode. This allows us to keep one thing in mind when working, and not have to worry about dual states of the component. \ No newline at end of file +In this way, we keep as much of the form as possible DRY, but we avoid passing state internally in the form so the form doesn't need to know whether it is in create or edit mode. This allows us to keep one thing in mind when working, and not have to worry about dual states of the component.