[design-principles] Fix typos. 他

Fix typos. w3ctag/design-principles@d46ef3a It looks like this text was duplicated w3ctag/design-principles@a43d138
triple-underscore · Dec 3, 2024 · cd58538 · cd58538
1 parent 0fee980
commit cd58538
Showing 1 changed file with 12 additions and 16 deletions.
diff --git a/design-principles-ja.html b/design-principles-ja.html
@@ -117,7 +117,7 @@
 ●●options
 
 spec_title:Web Platform Design Principles
-spec_date:2024-06-03
+spec_date:2024-12-03
 trans_update:2024-06-04
 source_checked:230406
 original_url:https://w3ctag.github.io/design-principles/
@@ -1585,7 +1585,7 @@
 [CSS-CASCADE-5]
     Elika Etemad; Miriam Suzanne; Tab Atkins Jr.. ＜CSS Cascading and Inheritance Level 5＞. URL: https://drafts.csswg.org/css-cascade-5/
 [CSS-CONDITIONAL-3]
-    David Baron; Elika Etemad; Chris Lilley. ＜CSS Conditional Rules Module Level 3＞. URL: https://drafts.csswg.org/css-conditional-3/
+    Chris Lilley; David Baron; Elika Etemad. ＜CSS Conditional Rules Module Level 3＞. URL: https://drafts.csswg.org/css-conditional-3/
 [DOM]
     Anne van Kesteren. ＜DOM Standard＞. Living Standard. URL: https://dom.spec.whatwg.org/
 [ECMASCRIPT]
@@ -1604,8 +1604,6 @@
     Dean Jackson; et al. ＜Media Queries Level 5＞. URL: https://drafts.csswg.org/mediaqueries-5/
 [PAYMENT-REQUEST]
     Marcos Caceres; Rouslan Solomakhin; Ian Jacobs. ＜Payment Request API＞. URL: https://w3c.github.io/payment-request/
-[PAYMENT-REQUEST-1.1]
-    Marcos Caceres; Rouslan Solomakhin; Ian Jacobs. ＜Payment Request API 1.1＞. URL: https://w3c.github.io/payment-request/
 [PRIVACY-PRINCIPLES]
     Robin Berjon; Jeffrey Yasskin. ＜Privacy Principles＞. URL: https://w3ctag.github.io/privacy-principles/
 [RFC2119]
@@ -1622,7 +1620,7 @@
 [APPMANIFEST]
     Marcos Caceres; et al. ＜Web Application Manifest＞. URL: https://w3c.github.io/manifest/
 [CREDENTIAL-MANAGEMENT-1]
-    Nina Satragno. ＜Credential Management Level 1＞. URL: https://w3c.github.io/webappsec-credential-management/
+    Nina Satragno; Marcos Caceres. ＜Credential Management Level 1＞. URL: https://w3c.github.io/webappsec-credential-management/
 [CSS-BACKGROUNDS-3]
     Elika Etemad; Brad Kemper. ＜CSS Backgrounds and Borders Module Level 3＞. URL: https://drafts.csswg.org/css-backgrounds/
 [CSS-FONTS-4]
@@ -1632,7 +1630,7 @@
 [CSS-GRID-1]
     Tab Atkins Jr.; et al. ＜CSS Grid Layout Module Level 1＞. URL: https://drafts.csswg.org/css-grid/
 [CSS-INLINE-3]
-    Dave Cramer; Elika Etemad. ＜CSS Inline Layout Module Level 3＞. URL: https://drafts.csswg.org/css-inline-3/
+    Elika Etemad. ＜CSS Inline Layout Module Level 3＞. URL: https://drafts.csswg.org/css-inline-3/
 [CSS-VALUES-4]
     Tab Atkins Jr.; Elika Etemad. ＜CSS Values and Units Module Level 4＞. URL: https://drafts.csswg.org/css-values-4/
 [CSS2]
@@ -1646,7 +1644,7 @@
 [DOM-Parsing]
     Travis Leithead. ＜DOM Parsing and Serialization＞. URL: https://w3c.github.io/DOM-Parsing/
 [ENCRYPTED-MEDIA]
-    David Dorwin; et al. ＜Encrypted Media Extensions＞. URL: https://w3c.github.io/encrypted-media/
+    Joey Parrish; Greg Freedman. ＜Encrypted Media Extensions＞. URL: https://w3c.github.io/encrypted-media/
 [ETHICAL-WEB]
     Daniel Appelquist; Hadley Beeman. ＜W3C TAG Ethical Web Principles＞. 27 October 2020. TAG Finding. URL: https://www.w3.org/2001/tag/doc/ethical-web-principles/
 [FETCH]
@@ -1666,7 +1664,7 @@
 [RFC8890]
     M. Nottingham. ＜The Internet is for End Users＞. August 2020. Informational. URL: https://www.rfc-editor.org/rfc/rfc8890
 [RFC8941]
-    M. Nottingham; P-H. Kamp. ＜Structured Field Values for HTTP＞. February 2021. Proposed Standard. URL: https://httpwg.org/specs/rfc8941.html
+    M. Nottingham; P-H. Kamp. ＜Structured Field Values for HTTP＞. September 2024. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc9651
 [UIEVENTS]
     Gary Kacmarcik; Travis Leithead. ＜UI Events＞. URL: https://w3c.github.io/uievents/
 [UNSANCTIONED-TRACKING]
@@ -1893,7 +1891,7 @@ <h3 title="It should be safe to visit a web page">1.2. ~web~pageは安全に訪
 未知な~web~pageを訪問するのは安全でない
 ］と感じるようになる。
 ◎
-For example, an API which allows any website to detect the use of assistive technologies may make users of these technologies feel unsafe visiting unknown web pages, since any web page may detect this private information.
+For example, an API that allows any website to detect the use of assistive technologies may make users of these technologies feel unsafe visiting unknown web pages, since any web page may detect this private information.
 </p>
 
 <p>
@@ -2311,9 +2309,7 @@ <h3 title="Add new capabilities with care">1.7. 新たな能力は~careの下で
 変更／除去
 ］はアリでないとは見做さないこと。
 ◎
-Do not assume that a change or removal is impossible without first checking.＼
-（以下重複）
-Before adding items, consider integration with existing, similar capabilities. If this leads to a preferred design approach that cannot be implemented by only adding items, it might still be possible; see § 1.8 Remove or change capabilities only once you understand existing usage. Do not assume that a change or removal is impossible without first checking.
+Do not assume that a change or removal is impossible without first checking.
 </p>
 
 		</section>
@@ -2562,7 +2558,7 @@ <h3 title="Consider tradeoffs between high level and low level APIs">2.2. 高~le
 ~nativeな~font~pickerには、
 組込みの~accessibilityもついて来るので，末端-利用者にとっての一貫性を供する。
 ◎
-A font picker (high level API) was recommended by the TAG over a Font Enumeration API (low level API) as it addresses the bulk of use cases, while preserving user privacy, as it is free from the the fingerprinting concerns that accompany a general Font Enumeration API. A native font picker also comes with accessibility built-in, and provides consistency for end users.
+A font picker (high level API) was recommended by the TAG over a Font Enumeration API (low level API) as it addresses the bulk of use cases, while preserving user privacy, as it is free from the fingerprinting concerns that accompany a general Font Enumeration API. A native font picker also comes with accessibility built-in, and provides consistency for end users.
 </div>
 
 <p>
@@ -5410,7 +5406,7 @@ <h3 title="Cancel asynchronous APIs/operations using AbortSignal">6.11. 非同
 非同期的な演算を取消す仕方として， `AbortSignal^I を一貫して利用すれば、
 作者は，~codeをもっと単純に書せるようになる。
 ◎
-Using AbortSignal consistently as the way to cancel an asychronous operation means that authors can write less complex code.
+Using AbortSignal consistently as the way to cancel an asynchronous operation means that authors can write less complex code.
 </p>
 
 <p>
@@ -7076,7 +7072,7 @@ <h3 title="Use care when exposing APIs for selecting or enumerating devices">9.2
 ］を考慮すること。
 `LEAST-POWER$r
 ◎
-If an API exposes the the existence, capabilities, or identifiers of more than one device, all of the risks in § 9.1 Don’t expose unnecessary information about devices are multiplied by the number of devices. For the same reasons, consider whether your user needs could be satisfied by a less powerful API. [LEAST-POWER]
+If an API exposes the existence, capabilities, or identifiers of more than one device, all of the risks in § 9.1 Don’t expose unnecessary information about devices are multiplied by the number of devices. For the same reasons, consider whether your user needs could be satisfied by a less powerful API. [LEAST-POWER]
 </p>
 
 <p>
@@ -8668,7 +8664,7 @@ <h4 title="If you need to monkey patch">11.4.1. ~monkey~patchする必要があ
 — したがって、
 各種~margin~propの使用~値は，拘束され過ぎを正すよう調整されない。
 ◎
-In terms of CSS2.1 block-level formatting [CSS2], the rules for “over-constrained” computations in CSS 2.1 § 10.3.3 Block-level, non-replaced elements in normal flow are ignored in favor of alignment as specified here and the used value of the margin properties are therefore not adjusted to correct for the over-constraint.
+In terms of CSS2.1 block-level formatting [CSS2], the rules for “over-constrained” computations in Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification § blockwidth are ignored in favor of alignment as specified here and the used value of the margin properties are therefore not adjusted to correct for the over-constraint.
 </p>
 </div>