diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-16 18:10:18 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-16 18:10:18 +0300 |
| commit | 6364c14cc1f445d471bca118dca5af5a85b2c5dc (patch) | |
| tree | 2579c5592f207e86ff7a0c5c7499caad723cdec1 /doc/development/renaming_features.md | |
| parent | 5a2284f3500088e04cf3a5854fb06dc9db2b6077 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/renaming_features.md')
| -rw-r--r-- | doc/development/renaming_features.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/renaming_features.md b/doc/development/renaming_features.md index 2a94fd2cbc3..f7fc1c11e37 100644 --- a/doc/development/renaming_features.md +++ b/doc/development/renaming_features.md @@ -22,9 +22,9 @@ 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, or repositories). -- The renaming will be disruptive in some way (database table renaming). +- The renaming is difficult to review (feature spans many lines, files, or repositories). +- The renaming is disruptive in some way (database table renaming). ## Consider a façade-first approach -The façade approach is not necessarily a final step. It can (and possibly *should*) be treated as the first step, where later iterations will accomplish the complete rename. +The façade approach is not necessarily a final step. It can (and possibly *should*) be treated as the first step, where later iterations accomplish the complete rename. |