CLDR-18227 Fix typo

unicode-org · Jan 15, 2025 · 8daff0f · 8daff0f
1 parent c32d4b8
commit 8daff0f
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/site/index/process.md b/docs/site/index/process.md
@@ -25,9 +25,9 @@ The [UTS #35: Locale Data Markup Language (LDML)](https://www.unicode.org/report
 - Requests for changes are entered in the bug/feature request database ([file a ticket](/requesting_changes#how-to-file-a-ticket)).
 - Structural changes are always backwards-compatible. That is, previous files will continue to work. Deprecated elements remain, although their usage is strongly discouraged.
 - There is a standing policy for structural changes that require non-trivial code for proper implementation, such as time zone fallback or alias mechanisms. These require design discussions in the [CLDR Design Working Group](https://cldr.unicode.org/cldr-tc/design-wg) and approval by the [CLDR Technical Committee](https://cldr.unicode.org/cldr-tc) that demonstrates correct function according to the proposed specification.
-- New sections may be added to the specification in Techical Preview, Final Candidate depending on how finalized the new section is, what type of feedback the TC requires, and whether the feedback period needs to extend across one or more releases.
+- New sections may be added to the specification in Technical Preview, Final Candidate depending on how finalized the new section is, what type of feedback the Technical Committee requires, and whether the feedback period needs to extend across one or more releases.
     - **Technical Preview** - Specification section have been approved by the CLDR Technical Committee and open for feedback. New features may be modified or removed similar to elements marked with [@TECHPREVIEW in the DTD as described in the LDML](https://www.unicode.org/reports/tr35/#dtd-annotations).
-    - **Final Candidate** - Specification section has been finalized and approved by the CLDR Technical Committee and is expected to become a part of the stable specification in the next release. An optional Final Candidate stage follows a period of feedback in Technical Preview stage for one or more releases where additional feedback is still desired. Changes will only be made if serious issues are discovered during this feedback period.
+    - **Final Candidate** - A Final Candidate is a version of a new section of the specification that is considered ready for release, and is expected to become stable in the next release. An optional Final Candidate stage follows a period of feedback in Technical Preview stage for one or more releases where additional feedback is still desired. Changes will only be made if serious issues are discovered during this feedback period.