publish: Merge pull request #41 from rust-lang/triagebot-be-gone

generated from commit a744e15

Author: GH Actions Runner

feature-lifecycle/api-change-proposals.html

@@ -159,12 +159,12 @@ <h1 id="api-change-proposals-acp"><a class="header" href="#api-change-proposals-
 being solved and concrete motivating examples.</p>
 <p>You can create an ACP in the <code>rust-lang/libs-team</code> repo using <a href="https://github.com/rust-lang/libs-team/issues/new?assignees=&amp;labels=api-change-proposal%2C+T-libs-api&amp;template=api-change-proposal.md&amp;title=%28My+API+Change+Proposal%29">this issue template</a>.</p>
 <p>Once a t-libs-api team member has reviewed the ACP and judged that it should
-move forward they will second the ACP (via <code>@rfcbot second</code>) 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.</p>
+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.</p>
 
                     </main>
 

print.html

@@ -347,12 +347,12 @@ <h1 id="println-debugging-alloc-and-core"><a class="header" href="#println-debug
 being solved and concrete motivating examples.</p>
 <p>You can create an ACP in the <code>rust-lang/libs-team</code> repo using <a href="https://github.com/rust-lang/libs-team/issues/new?assignees=&amp;labels=api-change-proposal%2C+T-libs-api&amp;template=api-change-proposal.md&amp;title=%28My+API+Change+Proposal%29">this issue template</a>.</p>
 <p>Once a t-libs-api team member has reviewed the ACP and judged that it should
-move forward they will second the ACP (via <code>@rfcbot second</code>) 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.</p>
+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.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="using-tracking-issues"><a class="header" href="#using-tracking-issues">Using tracking issues</a></h1>
 <p><strong>Status:</strong> Stub</p>
 <p>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.</p>