From 7fa44a9dd97a2aa1ea868dcd3eaa26553cda067a Mon Sep 17 00:00:00 2001
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Sun, 21 Jun 2020 14:36:40 +0100
Subject: [PATCH] README.md: Minor fixes

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 25c0e8c..128398f 100644
--- a/README.md
+++ b/README.md
@@ -311,7 +311,7 @@ Options
     nailing-cargo knows about `update`, `generate-lockfile` and
     `fetch`; all other subcommands are (silently) treated the same way
     as `build` (ie, no subcommand properties).  See
-    [`--subcommand-props`](#subcommand_props) for more detail about how the
+    `--subcommand-props` for more detail about how the
     subcommand affects nailing-cargo's behaviour.
 
     The default is to use the cargo subcommand found from parsing
@@ -513,7 +513,7 @@ Limitations and bugs
     subcommand you are running - especially for out-of-tree builds.
     nailing-cargo only has a short builtin list of commands it knows
     about (see [`-s<subcommand`](#s_subcommand)).  For other commands, you may need to
-    add an entry to `@subcmd_propss` in the source, or use
+    add an entry to `@subcmd_props` in the source, or use
     [`--subcommand-props`](#subcommand_props).
 
   * Out of tree builds require a unified filesystem view: eg, different
-- 
2.30.2