Merge branch 'application_limits-numbering-fix' into 'master'

docs: correct the numbering in a numbered list

See merge request gitlab-org/gitlab!41013

doc/development/application_limits.md

@@ -17,50 +17,50 @@ limits](https://about.gitlab.com/handbook/product/product-processes/#introducing
 
 ### Insert database plan limits
 
-In the `plan_limits` table, you have to create a new column and insert the
-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
-   that represents desired limit, such as:
-
-  ```ruby
-  add_column(:plan_limits, :project_hooks, :integer, default: 100, null: false)
-  ```
-
-  NOTE: **Note:**
-  Plan limits entries set to `0` mean that limits are not
-  enabled. You should use this setting only in special and documented circumstances.
-
-1. (Optionally) Create the database migration that fine-tunes each level with
-    a desired limit using `create_or_update_plan_limit` migration helper, such as:
-
-  ```ruby
-  class InsertProjectHooksPlanLimits < ActiveRecord::Migration[5.2]
-    include Gitlab::Database::MigrationHelpers
-
-    DOWNTIME = false
-
-    def up
-      create_or_update_plan_limit('project_hooks', 'default', 0)
-      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)
-    end
-
-    def down
-      create_or_update_plan_limit('project_hooks', 'default', 0)
-      create_or_update_plan_limit('project_hooks', 'free', 0)
-      create_or_update_plan_limit('project_hooks', 'bronze', 0)
-      create_or_update_plan_limit('project_hooks', 'silver', 0)
-      create_or_update_plan_limit('project_hooks', 'gold', 0)
-    end
-  end
-  ```
-
-NOTE: **Note:**
-Some plans exist only on GitLab.com. This will be no-op
-for plans that do not exist.
+In the `plan_limits` table, create a new column and insert the limit values.
+It's recommended to create two separate migration script files.
+
+1. Add a new column to the `plan_limits` table with non-null default value that
+   represents desired limit, such as:
+
+   ```ruby
+   add_column(:plan_limits, :project_hooks, :integer, default: 100, null: false)
+   ```
+
+   NOTE: **Note:**
+   Plan limits entries set to `0` mean that limits are not enabled. You should
+   use this setting only in special and documented circumstances.
+
+1. (Optionally) Create the database migration that fine-tunes each level with a
+   desired limit using `create_or_update_plan_limit` migration helper, such as:
+
+   ```ruby
+   class InsertProjectHooksPlanLimits < ActiveRecord::Migration[5.2]
+     include Gitlab::Database::MigrationHelpers
+
+     DOWNTIME = false
+
+     def up
+       create_or_update_plan_limit('project_hooks', 'default', 0)
+       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)
+     end
+
+     def down
+       create_or_update_plan_limit('project_hooks', 'default', 0)
+       create_or_update_plan_limit('project_hooks', 'free', 0)
+       create_or_update_plan_limit('project_hooks', 'bronze', 0)
+       create_or_update_plan_limit('project_hooks', 'silver', 0)
+       create_or_update_plan_limit('project_hooks', 'gold', 0)
+     end
+   end
+   ```
+
+   NOTE: **Note:**
+   Some plans exist only on GitLab.com. This will be a no-op for plans
+   that do not exist.
 
 ### Plan limits validation