Skip to content

A full-featured CRM built with React, shadcn/ui, and Supabase.

Fix typo in documentation.

Matthieu Hochlandereeafb287262d
diff --git a/doc/developer/architecture-choices.md b/doc/developer/architecture-choices.md
index 8a18e8f7..7d8cbcc0 100644
--- a/doc/developer/architecture-choices.md
+++ b/doc/developer/architecture-choices.md
@@ -12,7 +12,7 @@ When using [the FakeRest data provider](./data-providers.md#setting-up-the-faker
## Triggers
-User credentials are stored in Supabase's `auth.users` table. Supabase does not allow to add columns tp this table. That's why additional user details are stored in a `sales` table created by Atomic CRM. A database trigger is used to automatically sync the `sales` record when a user is created or updated (e.g. for the `first_name` and `last_name` fields).
+User credentials are stored in Supabase's `auth.users` table. Supabase does not allow to add columns to this table. That's why additional user details are stored in a `sales` table created by Atomic CRM. A database trigger is used to automatically sync the `sales` record when a user is created or updated (e.g. for the `first_name` and `last_name` fields).
The trigger can be found in the `supabase/migrations/20240730075425_init_triggers.sql` file.