Skip to content

Commit 65c9951

Browse files
authored
Docs: fix confusing formatting in why_mf_next.md (#808)
1 parent 79f8661 commit 65c9951

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

docs/why_mf_next.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,15 @@ why MessageFormat is important and why MessageFormat 2.0 is needed.
77

88
## Intro
99

10-
The `MessageFormat` API and syntax have been around for a long time.
11-
12-
Intro
10+
The `MessageFormat` API and syntax have been around for a long time:
1311

1412
- `MessageFormat` is the Unicode API for software localization
15-
- It is 20 years old, well designed, proven solution
16-
Its design was optimized for the software development model
17-
of twenty years ago.
18-
Implementers, developers, and translators struggle with its shortcomings.
13+
- It is 20 years old and is a well-designed, proven solution
1914

20-
The current wave of software development uses dynamic languages, modern UI
21-
frameworks and new forms of user interactions (voice, VR etc.).
15+
However, its design was optimized for the software development model of twenty
16+
years ago. Implementers, developers, and translators struggle with its
17+
shortcomings. The current wave of software development uses dynamic languages,
18+
modern UI frameworks, and new forms of user interactions (voice, VR etc.).
2219

2320
Considering these new challenges, combined with the lessons learned from using
2421
`MessageFormat`, we aim to design the next iteration of `MessageFormat`

0 commit comments

Comments
 (0)