roll in-progress work into tracking issues page

Author: KodrAus

src/SUMMARY.md

@@ -10,11 +10,10 @@
 
 This section describes the processes around how standard library features are developed and stabilized.
 
-- [Landing a new feature](./feature-lifecycle/new-unstable-features.md)
-- [Tracking issues](./feature-lifecycle/tracking-issues.md)
-- [Working on an unstable feature](./feature-lifecycle/working-on-unstable-features.md)
-- [Stabilizing a feature](./feature-lifecycle/stabilization.md)
-- [Deprecating a feature](./feature-lifecycle/deprecation.md)
+- [Landing new features](./feature-lifecycle/new-unstable-features.md)
+- [Using tracking issues](./feature-lifecycle/tracking-issues.md)
+- [Stabilizing features](./feature-lifecycle/stabilization.md)
+- [Deprecating features](./feature-lifecycle/deprecation.md)
 
 # Code considerations
 

src/feature-lifecycle/deprecation.md

@@ -1,4 +1,4 @@
-# Deprecating a feature
+# Deprecating features
 
 **Status:** Stub
 

src/feature-lifecycle/new-unstable-features.md

@@ -1,4 +1,4 @@
-# Landing a new features
+# Landing new features
 
 **Status:** Stub
 

src/feature-lifecycle/stabilization.md

@@ -1,4 +1,4 @@
-# Stabilizing a feature
+# Stabilizing features
 
 **Status:** Stub
 

src/feature-lifecycle/tracking-issues.md

@@ -1,7 +1,16 @@
-# Tracking issues
+# Using tracking issues
 
 **Status:** Stub
 
 Tracking issues are used to facilitate discussion and report on the status of standard library features. All public APIs need a dedicated tracking issue. Some larger internal units of work may also use them.
 
+## Creating a tracking issue
+
 There's a template that can be used to fill out the initial tracking issue. The Libs team also maintains [a Cargo tool](https://github.com/rust-lang/libs-team/tree/main/tools/unstable-api) that can be used to quickly dump the public API of an unstable feature.
+
+## Working on an unstable feature
+
+The current state of an unstable feature should be outlined in its tracking issue.
+
+If there's a change you'd like to make to an unstable feature, it can be discussed on the tracking issue first.
+