docs: new Crowdin updates

translated/es-ES/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/es-ES/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/es-ES/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).
 

translated/fr-FR/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/fr-FR/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/fr-FR/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).
 

translated/ja-JP/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/ja-JP/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/ja-JP/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).
 

translated/pt-PT/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/pt-PT/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/pt-PT/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).
 

translated/zh-CN/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/zh-CN/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/zh-CN/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).
 

translated/zh-TW/website/docs/core-concepts/icu-syntax.md

@@ -58,7 +58,7 @@ Sometimes embedding how the number will be formatted provides great context to t
 The price of this bagel is {num, number, ::sign-always compact-short currency/GBP}
 ```
 
-You can read more about this [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md).
+You can read more about this [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html).
 
 ### `date` Type
 
@@ -92,7 +92,7 @@ Internally it uses the `Intl.DateTimeFormat` API. You can define custom values f
 
 ### Supported DateTime Skeleton
 
-Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
+Similar to `number` type, we also support ICU DateTime skeleton. ICU provides a [wide array of pattern](https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table) to customize date time format. However, not all of them are available via ECMA402's Intl API. Therefore, we only support the following patterns
 
 | Symbol | Meaning                       | Notes                     |
 | ------ | ----------------------------- | ------------------------- |

translated/zh-TW/website/docs/intl-messageformat.md

@@ -210,7 +210,7 @@ new IntlMessageFormat(
 ).format({price: 100})
 ```
 
-A full set of options and syntax can be found [here](https://github.com/unicode-org/icu/blob/master/docs/userguide/format_parse/numbers/skeletons.md)
+A full set of options and syntax can be found [here](https://unicode-org.github.io/icu/userguide/format_parse/numbers/skeletons.html)
 
 #### Date/Time Skeleton
 

translated/zh-TW/website/docs/react-intl/upgrade-guide-3.x.md

@@ -350,7 +350,7 @@ This is especially beneficial in SSR where you can reuse the same `intl` object
 
 ## Message Format Syntax Changes
 
-We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/MessageFormat.html), in order to potentially support skeleton. So far the backwards-incompatible changes are:
+We've rewritten our parser to be more faithful to [ICU Message Format](https://unicode-org.github.io/icu/userguide/format_parse/messages/), in order to potentially support skeleton. So far the backwards-incompatible changes are:
 
 ### Escape character has been changed to apostrophe (`'`).