publish: fix typo in feature-lifecycle.md

generated from commit 34d39de

Author: GH Actions Runner

development/feature-lifecycle.html

@@ -175,7 +175,7 @@ <h2 id="api-design-exploration"><a class="header" href="#api-design-exploration"
 <li>An alternative that should <em>always</em> be considered is simply adding this feature via a third party crate. This is even possible when adding new methods to standard library types by using extension traits.</li>
 <li>In the case of &quot;convenience&quot; functions which are simply shorthands for something that is already possible with existing APIs, the cost of extending the standard library surface should be weighed against the ergonomic impact of the new functions.
 <ul>
-<li>For example, too many convenience methods on a type makes nagivating the documentation more difficult.</li>
+<li>For example, too many convenience methods on a type makes navigating the documentation more difficult.</li>
 <li>Additionally, consider whether this method is likely to be deprecated in the future if a language-level improvement makes it unnecessary.</li>
 </ul>
 </li>

print.html

@@ -388,7 +388,7 @@ <h2 id="api-design-exploration"><a class="header" href="#api-design-exploration"
 <li>An alternative that should <em>always</em> be considered is simply adding this feature via a third party crate. This is even possible when adding new methods to standard library types by using extension traits.</li>
 <li>In the case of &quot;convenience&quot; functions which are simply shorthands for something that is already possible with existing APIs, the cost of extending the standard library surface should be weighed against the ergonomic impact of the new functions.
 <ul>
-<li>For example, too many convenience methods on a type makes nagivating the documentation more difficult.</li>
+<li>For example, too many convenience methods on a type makes navigating the documentation more difficult.</li>
 <li>Additionally, consider whether this method is likely to be deprecated in the future if a language-level improvement makes it unnecessary.</li>
 </ul>
 </li>