summaryrefslogtreecommitdiff
path: root/doc/development/database/creating_enums.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/database/creating_enums.md')
-rw-r--r--doc/development/database/creating_enums.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/database/creating_enums.md b/doc/development/database/creating_enums.md
index 73c3f546728..e2ae36f7481 100644
--- a/doc/development/database/creating_enums.md
+++ b/doc/development/database/creating_enums.md
@@ -79,7 +79,7 @@ This works as-is, however, it has a couple of downside that:
- When it happens, we have to ship a database migration to fix the data integrity,
which might be impossible if you cannot recover the original value.
-Also, you might observe a workaround for this concern by setting an offset in EE's values.
+Also, you might observe a workaround for this concern by setting an offset in the `EE` module's values.
For example, this example sets `1000` as the offset:
```ruby