@@ -453,10 +453,10 @@ the documentation for the assigned deprecation identifier must remain in the
|
453 | 453 | Node.js API documentation. |
454 | 454 | |
455 | 455 | <a id="deprecation-cycle"></a> |
456 | | -A _Deprecation cycle_ is one full Node.js major release during which an API |
457 | | -has been in one of the three Deprecation levels. (Note that Documentation-Only |
458 | | -Deprecations may land in a Node.js minor release but must not be upgraded to |
459 | | -a Runtime Deprecation until the next major release.) |
| 456 | +A _Deprecation cycle_ is a major release during which an API has been in one of |
| 457 | +the three Deprecation levels. Documentation-Only Deprecations may land in a |
| 458 | +minor release but must not be upgraded to a Runtime Deprecation until the next |
| 459 | +major release. |
460 | 460 | |
461 | 461 | No API can be moved to End-of-life without first having gone through a |
462 | 462 | Runtime Deprecation cycle. However, there is no requirement that deprecated |
|