@@ -317,25 +317,25 @@ Additional information.
317317 </section>
318318
319319 <section xml:id="submitting-changes-tested-compilation">
320− <title>Tested compilation of all pkgs that depend on this change using <command>nix-review</command></title>
320+ <title>Tested compilation of all pkgs that depend on this change using <command>nixpkgs-review</command></title>
321321
322322 <para>
323− If you are updating a package's version, you can use nix-review to make sure all packages that depend on the updated package still compile correctly. The <command>nix-review</command> utility can look for and build all dependencies either based on uncommited changes with the <literal>wip</literal> option or specifying a github pull request number.
323+ If you are updating a package's version, you can use nixpkgs-review to make sure all packages that depend on the updated package still compile correctly. The <command>nixpkgs-review</command> utility can look for and build all dependencies either based on uncommited changes with the <literal>wip</literal> option or specifying a github pull request number.
324324 </para>
325325
326326 <para>
327327 review changes from pull request number 12345:
328− <screen>nix run nixpkgs.nix-review -c nix-review pr 12345</screen>
328+ <screen>nix run nixpkgs.nixpkgs-review -c nixpkgs-review pr 12345</screen>
329329 </para>
330330
331331 <para>
332332 review uncommitted changes:
333− <screen>nix run nixpkgs.nix-review -c nix-review wip</screen>
333+ <screen>nix run nixpkgs.nixpkgs-review -c nixpkgs-review wip</screen>
334334 </para>
335335
336336 <para>
337337 review changes from last commit:
338− <screen>nix run nixpkgs.nix-review -c nix-review rev HEAD</screen>
338+ <screen>nix run nixpkgs.nixpkgs-review -c nixpkgs-review rev HEAD</screen>
339339 </para>
340340 </section>
341341
@@ -408,7 +408,7 @@ Additional information.
408408 <section xml:id="submitting-changes-master-branch">
409409 <title>Master branch</title>
410410 <para>
411− The <literal>master</literal> branch is the main development branch.
411+ The <literal>master</literal> branch is the main development branch.
412412 It should only see non-breaking commits that do not cause mass rebuilds.
413413 </para>
414414 </section>
@@ -416,8 +416,8 @@ Additional information.
416416 <section xml:id="submitting-changes-staging-branch">
417417 <title>Staging branch</title>
418418 <para>
419− The <literal>staging</literal> branch is a development branch where mass-rebuilds go.
420− It should only see non-breaking mass-rebuild commits.
419+ The <literal>staging</literal> branch is a development branch where mass-rebuilds go.
420+ It should only see non-breaking mass-rebuild commits.
421421 That means it is not to be used for testing, and changes must have been well tested already.
422422 If the branch is already in a broken state, please refrain from adding extra new breakages.
423423 </para>
@@ -426,10 +426,10 @@ Additional information.
426426 <section xml:id="submitting-changes-staging-next-branch">
427427 <title>Staging-next branch</title>
428428 <para>
429− The <literal>staging-next</literal> branch is for stabilizing mass-rebuilds submitted to the <literal>staging</literal> branch prior to merging them into <literal>master</literal>.
430− Mass-rebuilds should go via the <literal>staging</literal> branch.
429+ The <literal>staging-next</literal> branch is for stabilizing mass-rebuilds submitted to the <literal>staging</literal> branch prior to merging them into <literal>master</literal>.
430+ Mass-rebuilds should go via the <literal>staging</literal> branch.
431431 It should only see non-breaking commits that are fixing issues blocking it from being merged into the <literal>master </literal> branch.
432− </para>
432+ </para>
433433 <para>
434434 If the branch is already in a broken state, please refrain from adding extra new breakages. Stabilize it for a few days and then merge into master.
435435 </para>