Add latest changes from gitlab-org/gitlab@master

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/development/application_limits.md b/doc/development/application_limits.md
index dd07a9cbfb7..f89b238cd79 100644
--- a/doc/development/application_limits.md
+++ b/doc/development/application_limits.md
@@ -22,22 +22,22 @@ limit values. It's recommended to create separate migration script files.
 
 1. Add new column to the `plan_limits` table with non-null default value 0, eg:
 
-    ```ruby
-    add_column(:plan_limits, :project_hooks, :integer, default: 0, null: false)
-    ```
+   ```ruby
+   add_column(:plan_limits, :project_hooks, :integer, default: 0, null: false)
+   ```
 
-    NOTE: **Note:** Plan limits entries set to `0` mean that limits are not
-    enabled.
+   NOTE: **Note:** Plan limits entries set to `0` mean that limits are not
+   enabled.
 
 1. Insert plan limits values into the database using
    `create_or_update_plan_limit` migration helper, eg:
 
-    ```ruby
-    create_or_update_plan_limit('project_hooks', 'free', 10)
-    create_or_update_plan_limit('project_hooks', 'bronze', 20)
-    create_or_update_plan_limit('project_hooks', 'silver', 30)
-    create_or_update_plan_limit('project_hooks', 'gold', 100)
-    ```
+   ```ruby
+   create_or_update_plan_limit('project_hooks', 'free', 10)
+   create_or_update_plan_limit('project_hooks', 'bronze', 20)
+   create_or_update_plan_limit('project_hooks', 'silver', 30)
+   create_or_update_plan_limit('project_hooks', 'gold', 100)
+   ```
 
 ### Plan limits validation