small fix

Author: raviranjanelastisys

docs/adr/0048-subscription-per-customer-model-on-azure.md

@@ -24,11 +24,11 @@ Should we consider the per Subscription-per-Customer Model for managing Azure re
    - `Good`, because subscriptions provide clear separation for billing and invoice purposes considering Azure invoices are prepared based on the Subscription ID, making it easier to track and manage costs per customer.
    - `Good`, because Azure typically operates with one tenant per organisation, closely tied to the Active Directory (AD) or Azure AD. Utilising multiple subscriptions under one tenant provides a coherent organisational structure, enhancing management and governance.
    - `Good`, because Role-Based Access Control (RBAC) settings are easier to manage at the subscription level, offering straightforward governance and security controls for each customer.
-   - `Good`, because azure imposes certain limits at the subscription level; having separate subscriptions helps in managing these limits more effectively.
+   - `Good`, because Azure imposes certain limits at the subscription level; having separate subscriptions helps in managing these limits more effectively.
    - `Good`, because virtual networks are scoped to a subscription, simplifying network management and isolation between customers.
    - `Bad`, because setting up network communication between subscriptions will require additional work than within a single subscription.
 
-1. Isolation at the Resource Group Level
+2. Isolation at the Resource Group Level
 
    - `Good` because resource groups allow for organising resources more flexibly within a single subscription, facilitating easier management of resources.
    - `Good` because managing subscriptions can reduce the complexity and overhead associated with subscription management, permissions, and billing setups.