Typos and syntax

Author: JayPanoz

docs/CSS01-readiumcss_fundamentals.md

@@ -46,6 +46,6 @@ We’ve also made sure that, for most “hardcoded” styles you might add when
 
 This last principle is important since the relationship between authors and Reading Systems’ developers has not been really great so far.
 
-Therefore, feedback has been collected, samples have been used all along development, and decisions impacting authors have been openly discussed. A public documentation is also available. 
+Therefore, feedback has been collected, samples have been used all along development, and decisions impacting authors have been openly discussed. All of this has been publicly documented during research and development. 
 
 More importantly, we must clearly state what is UA styles and user styles, and why `!important` is used. This process has a significant impact when it comes to transparency since it affects the cascade itself (see user settings recommendations). Should an author file an issue scoped to your implementation, please take the time to explain why you decided to differ and use `!important`, especially as such a decision can likely be backed by users’ feedback in many cases.

docs/CSS09-default_fonts.md

@@ -490,9 +490,9 @@ font-family: "Latin Modern Math", "STIX Two Math", "XITS Math", "STIX Math", "Li
 
 ## EBPAJ patch for Japanese
 
-The EBPAJ template only references fonts from MS Windows so Readium CSS has to reference fonts from other platforms and override authors’ stylesheets. What it does in this polyfill is keeping the default value used in EBPAJ templates and providing fallbacks for all platforms.
+The EBPAJ template only references fonts from MS Windows so Readium CSS has to reference fonts from other platforms and override authors’ stylesheets. What it does in this patch is keeping the default value used in EBPAJ templates and providing fallbacks for all platforms.
 
-Implementers might want to load this polyfill only if they find one of the following metadata items in the OPF package:
+Implementers might want to load this patch only if they find one of the following metadata items in the OPF package:
 
 - version 1: `<dc:description id="ebpaj-guide">ebpaj-guide-1.0</dc:description>`
 - version 1.1: `<meta property="ebpaj:guide-version">1.1</meta>`

docs/CSS11-user_prefs.md

@@ -76,7 +76,7 @@ Possible values: `readium-font-on` | `readium-font-off`
 
 ### Advanced Settings
 
-Acts as an explicit switch to overrides publisher’s styles.
+Acts as an explicit switch to override the publisher’s styles.
 
 It must be set if the user changes `font-family` or `font-size`.
 

docs/CSS14-user_settings_recs.md

@@ -27,7 +27,7 @@ Users’ styles > Authors’ styles > Implementers’ styles
 
 Which is why conceptualizing this issue as intents may help.
 
-Typography is not just a set of settings though, it’s a complex system in which some settings impact other settings. For instance, font-size impacts line-height and line-length, which impacts the number of columns.
+Typography is not just a set of settings though, it’s a complex system in which some settings impact others. For instance, font-size impacts line-height and line-length, which impacts the number of columns.
 
 It is up to implementers to pick their preferred approach (minimal set, presets, minimal set/presets with advanced settings, maximal set) since it is primarily an UX issue.
 
@@ -59,7 +59,7 @@ For a11y-related typefaces (Open Dyslexic, bold style of sans-serif family), the
 
 Declaring a `font-family` for `body`, `p` and `p.class` is so common that it should not be considered an intent per se. While `p.class` is debatable, it is so widespread in practice (some authoring tools output `font-family` for every paragraph style) that it can’t be considered an intent in pure CSS.
 
-A different `font-family` can be set for headings (`h1`, `h2`, `h3` etc.), `blockquote`, `i`, `span`, etc.
+A different `font-family` can be set for headings (`h1`, `h2`, `h3`, etc.), `blockquote`, `i`, `span`, etc.
 
 ### What to do
 

docs/CSS15-user_pref_insights.md

@@ -12,7 +12,7 @@ This is really tricky as **there may be a cultural factor to take into account**
 
 When asked directly, the vast majority of users will say they prefer basic settings (reading modes, typeface, and font size) over other options (maximum amount of settings possible, themes, customizable themes). Customizable themes and advanced settings are equally popular, at a distant second place.
 
-Once again, this is a complex UX issue and your mileage may vary. On Android for instance, there is a lot of apps with advanced settings as the default, and millions of people use them. So it’s primarily about your UX proposal, people using it, etc.
+Once again, this is a complex UX issue and your mileage may vary. On Android for instance, there is a lot of apps with advanced settings as the default, and millions of people are using them daily. So it’s primarily about your UX proposal, people using it, etc.
 
 Hopefully, Readium CSS was designed to take all those options into account: modules are take or leave, which implies you can build any UX from them.
 
@@ -24,7 +24,7 @@ We’ve been running forms on this topic but answers can’t be taken at face va
 
 People keeping the publisher’s typeface are in the minority (< 15%). Most users at least change the typeface occasionally (see reasons below), although they don’t necessarily do it for each ebook – some ebooks simply use the default typeface so it’s quite complex to measure.
 
-What’s important is that **you’d better have some kind of bulletproof set of RS typefaces.** Bulletproof is the keyword here, since it is difficult to imagine a set that will satisfy everybody. There won’t be any silver bullet. 
+What’s important is that **you’d better have some kind of bulletproof selection of RS typefaces.** “Bulletproof” is the keyword here, since it is difficult to imagine a selection that will satisfy everybody. There won’t be any silver bullet. 
 
 Since more people systematically change the publisher’s typeface than those who never do it, **implementers might end up with a huge share of users systematically changing the typeface and could adjust the UX accordingly** (global setting applying the typeface in all books).
 

docs/CSS16-internationalization.md

@@ -12,6 +12,8 @@ This could well explain why the most popular Reading Apps tend to implement the
 
 Occasionally, when an app does support a language, it can put some constraints on authors, as there is no other way to make sure the publication will be handled well otherwise e.g. specifying the `Hans` or `Hant` script for Chinese (`zh`).
 
+We can’t overemphasize the importance of the internationalization process though, as the 24 languages we added extend support to 3,049,150,507 speakers, from the 1,150 people speaking Western Canadian Inuktitut, to the 1,200,000,000 speaking Chinese. In total, we can cover the needs of 5,262,900,507 speakers. Credit where credit is due, this wouldn’t have been possible if Operating Systems and browsers didn’t tackle this process upstream, added fonts for those languages and improved support in rendering engines.
+
 ## Resources
 
 - [W3C Internationalization Working Group Home Page](https://www.w3.org/International/core/Overview)
@@ -208,7 +210,7 @@ The most information we have, the better the fix will be. Please feel free to go
 
 ### Sending feedback
 
-We’re not saying you should do the implementation if we don’t support it at all or very well, but it is noteworthy that we can’t necessarily get all the details right, especially when we don’t know how to speak and write a language or script.
+We’re not saying you should implement a support of script yourself if we don’t support it at all or very well, but it is noteworthy that we can’t necessarily get all the details right, especially when we don’t know how to speak and write the language you wish were supported or improved.
 
 If our font-stacks are not good enough, a solider one will help. If we don’t have any font-stack for a language, a basic one will do. Additionally, you can point us to libre/open-source fonts which you think should be recommended to implementers.
 

docs/CSS17-i18n_typography.md

@@ -32,7 +32,7 @@ For vertical text the placement needs to be to the right or left of the line of
 
 Bold and italic are not always appropriate for expressing emphasis, and some scripts have their own unique ways of doing it.
 
-In Japanese, a sans-serif font or emphasis dots (horizontal writing) or sesame (vertical writing) may be used to express emphasis. 
+In Japanese, a sans-serif font, or emphasis dots (horizontal writing) and sesame (vertical writing) may be used to express emphasis. 
 
 In the Amharic Script (Ethiopic), underlines, larger text or a different color may be used to express emphasis. 
 
@@ -54,7 +54,7 @@ Although CJK doesn’t use hyphenation, documents may contain other scripts whic
 
 Typographic conventions for full text justification depend on the writing system, the content language, and the calligraphic style of the text. Some scripts have complex methods the rendering engine doesn’t necessarily support.
 
-Kashida elongation is not supported for the Arabic script for instance (`text-justify`), but authors may be using the tatweel (see [i18n glossary doc](../docs/CSS26-i18n_glossary.md)) to elongate some words.
+Kashida elongation is not supported for the Arabic script for instance (`text-justify`), but authors may be using the tatweel joining character (see [i18n glossary doc](../docs/CSS26-i18n_glossary.md)) to elongate some words.
 
 Chinese and Japanese are using `inter-character` justification for instance, while Latin uses `inter-word`. 
 
@@ -64,7 +64,7 @@ In some scripts like CJK, indents are really important. Implementers should not
 
 ## Vertical text
 
-Implementers must not try to offer users with a setting allowing users to switch from the vertical to horizontal writing mode, and vice versa, unless they support alternate stylesheets and the publication provides one for each mode. Indeed, characters, punctuation, emphasis marks, quotes, and so on and so forth, depend on the writing mode used, and an automatic switch would provide users with a subpar experience. 
+Implementers must not try to provide a setting allowing users to switch from the vertical to horizontal writing mode, and vice versa, unless they support alternate stylesheets and the publication provides one for each mode. Indeed, characters, punctuation, emphasis marks, quotes, and so on and so forth, depend on the writing mode used, and an automatic switch would provide users with a subpar experience. 
 
 It's common for content authors to want to mix short horizontal runs of text, such as the tate-chu-yoko i.e. 2-digit numbers (`text-combine-upright`) or acronyms (`text-orientation`), in a vertical text.
 

docs/CSS19-api.md

@@ -114,6 +114,40 @@ A monospace font-stack relying on pre-installed fonts.
 
 Default is `"Andale Mono", Consolas, monospace`.
 
+### Default font-stacks for Japanese publications
+
+```
+--RS__serif-ja
+```
+
+A Mincho font-stack whose fonts with proportional latin characters are prioritized for horizontal writing.
+
+Default is `"ＭＳ Ｐ明朝", "MS PMincho", "Hiragino Mincho Pro", "ヒラギノ明朝 Pro W3", "游明朝", "YuMincho", "ＭＳ 明朝", "MS Mincho", "Hiragino Mincho ProN", serif`.
+
+```
+--RS__sans-serif-ja
+```
+
+A Gothic font-stack whose fonts with proportional latin characters are prioritized for horizontal writing.
+
+Default is `"ＭＳ Ｐゴシック", "MS PGothic", "Hiragino Kaku Gothic Pro W3", "ヒラギノ角ゴ Pro W3", "Hiragino Sans GB", "ヒラギノ角ゴシック W3", "游ゴシック", "YuGothic", "ＭＳ ゴシック", "MS Gothic", "Hiragino Sans", sans-serif`.
+
+```
+--RS__serif-ja-v
+```
+
+A Mincho font-stack whose fonts with fixed-width latin characters are prioritized for vertical writing.
+
+Default is `"ＭＳ 明朝", "MS Mincho", "Hiragino Mincho Pro", "ヒラギノ明朝 Pro W3", "游明朝", "YuMincho", "ＭＳ Ｐ明朝", "MS PMincho", "Hiragino Mincho ProN", serif`.
+
+```
+--RS__sans-serif-ja-v
+```
+
+A Gothic font-stack whose fonts with fixed-width latin characters are prioritized for vertical writing.
+
+Default is `"ＭＳ ゴシック", "MS Gothic", "Hiragino Kaku Gothic Pro W3", "ヒラギノ角ゴ Pro W3", "Hiragino Sans GB", "ヒラギノ角ゴシック W3", "游ゴシック", "YuGothic", "ＭＳ Ｐゴシック", "MS PGothic", "Hiragino Sans", sans-serif`.
+
 ### Base styles for all ebooks
 
 ```
@@ -314,7 +348,7 @@ It impacts `body`.
 --USER__view
 ```
 
-Enables scroll mode.
+Switches from the paged to the scroll view.
 
 Scope: `html`
 
@@ -468,7 +502,7 @@ Scope: `html`
 --USER__darkenImages
 ```
 
-A filter to darken mages in night mode. It behaves as a switch i.e. if it is present, the filter is enabled.
+A filter to darken images in night mode.
 
 Scope: `html`
 
@@ -478,7 +512,7 @@ It impacts all `img` elements in the DOM.
 --USER__invertImages
 ```
 
-A filter to invert images in night mode. It behaves as a switch i.e. if it is present, the filter is enabled.
+A filter to invert images in night mode.
 
 Scope: `html`
 

docs/CSS21-epub_compat.md

@@ -148,7 +148,7 @@ This metadata has an `ibooks:` prefix.
 Authors must add the following prefix attribute in their `<package>` first:
 
 ```
-prefix="ibooks: http://vocabulary.itunes.apple.com/rdf/ibooks/vocabulary-extensions-1.0/
+prefix="ibooks: http://vocabulary.itunes.apple.com/rdf/ibooks/vocabulary-extensions-1.0/"
 ```
 
 Then, they can use the ibooks-specific metadata. 

docs/CSS25-performance_hacks.md

@@ -145,7 +145,7 @@ The `contain` property indicates that **the element and its contents are, as muc
 
 This allows the browser to recalculate layout, style, paint, size, or any combination of them for a limited area of the DOM and not the entire page. To put it simply, it lets developers limit the scope of the browser's styles, layout and paint work.
 
-It was primarily meants for webpages which contain a lot of widgets that are all independent as it can be used to prevent one widget's CSS rules from changing other things on the page.
+It was primarily meant for webpages which contain a lot of widgets that are all independent as it can be used to prevent one widget's CSS rules from changing other things on the page.
 
 ### Usage
 

docs/CSS26-i18n_glossary.md

@@ -300,6 +300,9 @@ This glossary has been created from the <a href="https://www.w3.org/TR/jlreq/#te
   <dt>Ideographic numerals / Kansūji (漢数字)</dt>
   <dd>Ideographic characters representing numbers.</dd>
 
+  <dt>Inline cutting note / Warichu (割注)</dt>
+  <dd>A note of two or more lines inserted in the text. It includes brackets which surround the note (JIS Z 8125)</dd>
+
   <dt>Inseparable characters rule / Bunri kinshi (分離禁止)</dt>
   <dd>A line adjustment rule that prohibits inserting any space between specific combinations of characters. (JIS Z 8125)</dd>
 
@@ -411,9 +414,6 @@ This glossary has been created from the <a href="https://www.w3.org/TR/jlreq/#te
   <dt>Vertical writing mode / Tate gumi (縦組)</dt>
   <dd>The process or the result of arranging characters on a line from top to bottom, of lines on a page from right to left, and/or of columns on a page from top to bottom. (JIS Z 8125)</dd>
 
-  <dt>Inline cutting note / Warichu (割注)</dt>
-  <dd>A note of two or more lines inserted in the text. It includes brackets which surround the note (JIS Z 8125)</dd>
-
   <dt>Widow Adjustment / Danraku matsubi shori (段落末尾処理)</dt>
   <dd>A method of line composition to adjust lines in a paragraph so that the last line consists of more than a given number of characters.</dd>
 </dl>

docs/ReadiumCSS_docs.epub

@@ -74,7 +74,7 @@
 
       <p>This last principle is important since the relationship between authors and Reading Systems’ developers has not been really great so far.</p>
 
-      <p>Therefore, feedback has been collected, samples have been used all along development, and decisions impacting authors have been openly discussed. A public documentation is also available.</p>
+      <p>Therefore, feedback has been collected, samples have been used all along development, and decisions impacting authors have been openly discussed. All of this has been publicly documented during research and development.</p>
 
       <p>More importantly, we must clearly state what is UA styles and user styles, and why <code>!important</code> is used. This process has a significant impact when it comes to transparency since it affects the cascade itself (see user settings recommendations). Should an author file an issue scoped to your implementation, please take the time to explain why you decided to differ and use <code>!important</code>, especially as such a decision can likely be backed by users’ feedback in many cases.</p>
     </section>

docs/ReadiumCSS_docs/OEBPS/Text/Section-001.xhtml

@@ -945,9 +945,9 @@ unicode-range: U+0500-052F;</code></pre>
     <section id="ebpaj-patch-for-japanese" class="level2">
       <h2 id="sigil_toc_id_130">EBPAJ patch for Japanese</h2>
 
-      <p>The EBPAJ template only references fonts from MS Windows so Readium CSS has to reference fonts from other platforms and override authors’ stylesheets. What it does in this polyfill is keeping the default value used in EBPAJ templates and providing fallbacks for all platforms.</p>
+      <p>The EBPAJ template only references fonts from MS Windows so Readium CSS has to reference fonts from other platforms and override authors’ stylesheets. What it does in this patch is keeping the default value used in EBPAJ templates and providing fallbacks for all platforms.</p>
 
-      <p>Implementers might want to load this polyfill only if they find one of the following metadata items in the OPF package:</p>
+      <p>Implementers might want to load this patch only if they find one of the following metadata items in the OPF package:</p>
 
       <ul>
         <li>version 1: <code>&lt;dc:description id="ebpaj-guide"&gt;ebpaj-guide-1.0&lt;/dc:description&gt;</code></li>

docs/ReadiumCSS_docs/OEBPS/Text/Section-009.xhtml

@@ -99,7 +99,7 @@
       <section id="advanced-settings" class="level3">
         <h3 class="sigil_not_in_toc">Advanced Settings</h3>
 
-        <p>Acts as an explicit switch to overrides publisher’s styles.</p>
+        <p>Acts as an explicit switch to override the publisher’s styles.</p>
 
         <p>It must be set if the user changes <code>font-family</code> or <code>font-size</code>.</p>
 

docs/ReadiumCSS_docs/OEBPS/Text/Section-011.xhtml

@@ -48,7 +48,7 @@
 
       <p>Which is why conceptualizing this issue as intents may help.</p>
 
-      <p>Typography is not just a set of settings though, it’s a complex system in which some settings impact other settings. For instance, font-size impacts line-height and line-length, which impacts the number of columns.</p>
+      <p>Typography is not just a set of settings though, it’s a complex system in which some settings impact others. For instance, font-size impacts line-height and line-length, which impacts the number of columns.</p>
 
       <p>It is up to implementers to pick their preferred approach (minimal set, presets, minimal set/presets with advanced settings, maximal set) since it is primarily an UX issue.</p>
     </section>
@@ -93,7 +93,7 @@
 
         <p>Declaring a <code>font-family</code> for <code>body</code>, <code>p</code> and <code>p.class</code> is so common that it should not be considered an intent <i>per se</i>. While <code>p.class</code> is debatable, it is so widespread in practice (some authoring tools output <code>font-family</code> for every paragraph style) that it can’t be considered an intent in pure CSS.</p>
 
-        <p>A different <code>font-family</code> can be set for headings (<code>h1</code>, <code>h2</code>, <code>h3</code> etc.), <code>blockquote</code>, <code>i</code>, <code>span</code>, etc.</p>
+        <p>A different <code>font-family</code> can be set for headings (<code>h1</code>, <code>h2</code>, <code>h3</code>, etc.), <code>blockquote</code>, <code>i</code>, <code>span</code>, etc.</p>
       </section>
 
       <section id="what-to-do" class="level3">