summaryrefslogtreecommitdiff
path: root/doc/development/renaming_features.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/renaming_features.md')
-rw-r--r--doc/development/renaming_features.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/renaming_features.md b/doc/development/renaming_features.md
index 6a196921a5d..daf437027db 100644
--- a/doc/development/renaming_features.md
+++ b/doc/development/renaming_features.md
@@ -16,7 +16,7 @@ The more of the following that are true, the more likely you should choose the f
- You are not confident the new name is permanent.
- The feature is susceptible to bugs (large, complex, needing refactor, etc).
-- The renaming will be difficult to review (feature spans many lines/files/repos).
+- The renaming will be difficult to review (feature spans many lines, files, or repositories).
- The renaming will be disruptive in some way (database table renaming).
## Consider a façade-first approach