From a0a5dc714d02eca656fc89dcbecd1e4e9836ecf0 Mon Sep 17 00:00:00 2001 From: Jane Lusby Date: Tue, 7 Jun 2022 13:03:05 -0700 Subject: [PATCH] remove reference to unsupported command --- src/feature-lifecycle/api-change-proposals.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/feature-lifecycle/api-change-proposals.md b/src/feature-lifecycle/api-change-proposals.md index 878cad4..f16680b 100644 --- a/src/feature-lifecycle/api-change-proposals.md +++ b/src/feature-lifecycle/api-change-proposals.md @@ -13,9 +13,9 @@ being solved and concrete motivating examples. You can create an ACP in the `rust-lang/libs-team` repo using [this issue template](https://github.com/rust-lang/libs-team/issues/new?assignees=&labels=api-change-proposal%2C+T-libs-api&template=api-change-proposal.md&title=%28My+API+Change+Proposal%29). Once a t-libs-api team member has reviewed the ACP and judged that it should -move forward they will second the ACP (via `@rfcbot second`) and initiate an -ICP (inital comment period). This initial comment period is intended to give -other stake holders a chance to participate in the initial discussion prior to -starting the implementation. Once this ICP has completed you should proceed -with the implementation of your proposal and then move on to the next step of -the feature lifecycle, creating a tracking issue. +move forward they will second the ACP and initiate an ICP (inital comment +period). This initial comment period is intended to give other stake holders a +chance to participate in the initial discussion prior to starting the +implementation. Once this ICP has completed you should proceed with the +implementation of your proposal and then move on to the next step of the +feature lifecycle, creating a tracking issue.