Improve RuboCop config and fix documentation after review

Signed-off-by: Rémy Coutable <remy@rymai.me>

.rubocop.yml

@@ -10,10 +10,9 @@ AllCops:
   Exclude:
     - 'vendor/**/*'
     - 'node_modules/**/*'
-    - 'db/*'
+    - 'db/**/*'
     - 'db/fixtures/**/*'
-    - 'db/geo/*'
-    - 'ee/db/geo/*'
+    - 'ee/db/**/*'
     - 'tmp/**/*'
     - 'bin/**/*'
     - 'generator_templates/**/*'
@@ -27,7 +26,6 @@ Style/MutableConstant:
   Exclude:
     - 'db/migrate/**/*'
     - 'db/post_migrate/**/*'
-    - 'db/geo/migrate/**/*'
     - 'ee/db/migrate/**/*'
     - 'ee/db/post_migrate/**/*'
     - 'ee/db/geo/migrate/**/*'
@@ -52,10 +50,10 @@ GitlabSecurity/PublicSend:
   Exclude:
     - 'config/**/*'
     - 'db/**/*'
-    - 'ee/db/**/*'
     - 'features/**/*'
     - 'lib/**/*.rake'
-    - 'ee/lib/**/*.rake'
     - 'qa/**/*'
     - 'spec/**/*'
+    - 'ee/db/**/*'
+    - 'ee/lib/**/*.rake'
     - 'ee/spec/**/*'

doc/development/ee_features.md

@@ -28,8 +28,8 @@ we still need to merge changes from GitLab CE to EE. To help us get there,
 we should make sure that we no longer edit CE files in place in order to
 implement EE features.
 
-Instead, all EE codes should be put inside the `ee/` top-level directory. The
-rest of codes should be as close as to the CE files.
+Instead, all EE code should be put inside the `ee/` top-level directory. The
+rest of the code should be as close to the CE files as possible.
 
 [single code base]: https://gitlab.com/gitlab-org/gitlab-ee/issues/2952#note_41016454