Skip to content

Commit

Permalink
docs: update changelog wordings
Browse files Browse the repository at this point in the history
  • Loading branch information
snitin315 authored Feb 8, 2024
1 parent 67a1172 commit 67ca36c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions .changeset/purple-flies-end.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ References**

1. The `<Amount />` component will now automatically format numbers based on the user's browser locale. For example, `<Amount value={123456.789} currency="INR">` will render `₹1,23,456.79` for browsers with the `en-IN` default locale, whereas it will render `₹123,456.79` for browsers with the `en-US` locale.

2. If you want to enable users to change the locale of your page, add the `@razorpay/i18nify-react` package and wrap your app inside the `I18nProvider`. Utilize the `setI18nState` utility to modify the locale. Please refer to the [documentation](https://www.npmjs.com/package/@razorpay/i18nify-react) for more details.
2. If you want to enable users to change the locale of your page, add the `@razorpay/i18nify-react` package and wrap your app inside the `I18nProvider`. Utilize the `setI18nState` utility to modify the locale. For more details, please refer to the [documentation](https://www.npmjs.com/package/@razorpay/i18nify-react).

3. Additionally, if you prefer to maintain a fixed locale for your page and amount component, simply enclose your app within `<I18nProvider data={{locale: 'locale-you-want'}}>..` . Please refer to the [documentation](https://www.npmjs.com/package/@razorpay/i18nify-react) for more details.
3. Additionally, if you prefer to maintain a fixed locale for your page and amount component, enclose your app within `<I18nProvider data={{locale: 'locale-you-want'}}>..`. For more details, please refer to the [documentation](https://www.npmjs.com/package/@razorpay/i18nify-react).

**How to update ?**

Expand Down

0 comments on commit 67ca36c

Please sign in to comment.