Skip to content

Commit 06706f3

Browse files
navarrsamdark
andauthored
Minor word changes and typographical fixes
Co-authored-by: Alexander Makarov <[email protected]>
1 parent 038d5f3 commit 06706f3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

proposed/internationalisation-meta.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
1-
# Internationalism Meta Document
1+
# Internationalization Meta Document
22

33
## 1. Summary
44

5-
Developers of components that are unattached to specific frameworks often find themselves in need of displaying a message to the user of the web application. However, being as they are not a component of a specific framework - their options for making these messages localisable is limited. In many cases, developers will make no attempt to pass these messages through a localisation layer.
5+
Developers of components that are not coupled to any specific framework often find themselves in need of displaying a message to the user of the web application. However, being as they are not a component of a specific framework - their options for making these messages localisable is limited. In many cases, developers will make no attempt to pass these messages through a localization layer.
66

77
To resolve this issue and encourage the localization of libraries, a standard method for translating and transforming messages is necessary.
88

99
## 3. Scope
1010

1111
### 3.1. Goals
1212

13-
* Provide a method by which an unattached component may display a message in a language other than the one in which the component was written in.
13+
* Provide a method for an indepedent component to display a message in a language other than the one in which the component was written in.
1414

1515
### 3.2. Non-Goals
1616

1717
* This PSR does not provide a standard for adding translations of existing messages to a data store (as a language pack may).
1818

1919
## 4. Approaches
2020

21-
To solve this, we currently aim to create an interface that an framework-unaffiliated component can rely on for transforming a message key of some sort with context into a translated and formatted string
21+
To solve this, we currently aim to create an interface that an framework-independent component can rely on for transforming a message key and context into a translated and formatted string.
2222

2323
## 5. People
2424

0 commit comments

Comments
 (0)