*SVF: help/usage updates

Usage messages should use the same EBNF as the User's Guide;
no angle brackets.  Be more complete too ... some params were
missing.

Don't use "&function"; its name is its address.

Unrelated: fix typo in one "target.c" usage message.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

src/svf/svf.c

@@ -1461,10 +1461,10 @@ static int svf_run_command(struct command_context *cmd_ctx, char *cmd_str)
 static const struct command_registration svf_command_handlers[] = {
 	{
 		.name = "svf",
-		.handler = &handle_svf_command,
+		.handler = handle_svf_command,
 		.mode = COMMAND_EXEC,
 		.help = "Runs a SVF file.",
-		.usage = "<file>",
+		.usage = "filename ['quiet']",
 	},
 	COMMAND_REGISTRATION_DONE
 };

src/target/target.c

@@ -4916,7 +4916,7 @@ static const struct command_registration target_exec_command_handlers[] = {
 		.handler = handle_virt2phys_command,
 		.mode = COMMAND_ANY,
 		.help = "translate a virtual address into a physical address",
-		.usage = "virual_address",
+		.usage = "virtual_address",
 	},
 	{
 		.name = "reg",

src/xsvf/xsvf.c

@@ -1053,13 +1053,13 @@ COMMAND_HANDLER(handle_xsvf_command)
 static const struct command_registration xsvf_command_handlers[] = {
 	{
 		.name = "xsvf",
-		.handler = &handle_xsvf_command,
+		.handler = handle_xsvf_command,
 		.mode = COMMAND_EXEC,
 		.help = "Runs a XSVF file.  If 'virt2' is given, xruntest "
 			"counts are interpreted as TCK cycles rather than "
 			"as microseconds.  Without the 'quiet' option, all "
 			"comments, retries, and mismatches will be reported.",
-		.usage = "<file> [virt2] [quiet]",
+		.usage = "(tapname|'plain') filename ['virt2'] ['quiet']",
 	},
 	COMMAND_REGISTRATION_DONE
 };