CLDR-18227 Improve wording

Accept suggestions from the code review to improve wording.

Co-authored-by: Mark Davis <[email protected]>

docs/site/index/process.md

@@ -24,10 +24,13 @@ 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 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 has 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** - 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.
+- 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). Complex changes may require prototypes that demonstrate correct function according to the proposed specification.
+- New sections may be added to the specification with the status of _Technical Preview_ or _Final Candidate_. That depends on how fleshed-out 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. These terms mean the following:
+    - **Technical Preview** - The specification section is fairly complete but not stable, included in the release to gather feedback.
+Features may be modified or removed based upon feedback.
+A section in Technical Preview remain in Technical Preview in a following release, if more feedback is needed, or could advance to Final Candidate, or could advance to approved.
+It is similar to elements marked with [@TECHPREVIEW in the DTD as described in the LDML](https://www.unicode.org/reports/tr35/#dtd-annotations).
+    - **Final Candidate** - The specification section is complete and 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 where final feedback is desired. Changes will only be made if serious issues are discovered during this feedback period.