docs: correct the numbering in a numbered list

doc/development/application_limits.md

@@ -17,22 +17,22 @@ 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.
+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 new column to the `plan_limits` table with non-null default value
-   that represents desired limit, such as:
+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.
+   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:
+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]
@@ -58,9 +58,9 @@ limit values. It's recommended to create separate migration script files.
    end
    ```
 
-NOTE: **Note:**
-Some plans exist only on GitLab.com. This will be no-op
-for plans that do not exist.
+   NOTE: **Note:**
+   Some plans exist only on GitLab.com. This will be a no-op for plans
+   that do not exist.
 
 ### Plan limits validation