@@ -10,8 +10,11 @@ If your program doesn't take command-line arguments, you can suppress the comman
 
 Similarly, if you never access the environment table through the *`envp`* argument, you can suppress the internal environment-processing routine. To suppress its use, include the *`noenv.obj`* file (for both `main` and `wmain`) in your **`/link`** compiler options or your **`LINK`** command line.
 
+For more information on runtime startup linker options, see [Link options](../c-runtime-library/link-options.md).
+
 Your program might make calls to the `spawn` or `exec` family of routines in the C runtime library. If it does, you shouldn't suppress the environment-processing routine, since it's used to pass an environment from the parent process to the child process.
 
 ## See also
 
-[`main` function and program execution](../c-language/main-function-and-program-execution.md)
+[`main` function and program execution](../c-language/main-function-and-program-execution.md)\
+[Link options](../c-runtime-library/link-options.md).
@@ -10,7 +10,7 @@ Wildcard argument expansion is Microsoft-specific.
 
 When you run a C program, you can use either of the two wildcards, the question mark (**`?`**) and the asterisk (**`*`**), to specify filename and path arguments on the command line.
 
-By default, wildcards aren't expanded in command-line arguments. You can replace the normal argument vector `argv` loading routine with a version that does expand wildcards by linking with the *`setargv.obj`* or *`wsetargv.obj`* file. If your program uses a `main` function, link with *`setargv.obj`*. If your program uses a `wmain` function, link with *`wsetargv.obj`*. Both of these have equivalent behavior.
+By default, wildcards aren't expanded in command-line arguments. You can replace the normal argument vector `argv` loading routine with a version that does expand wildcards by linking with the *`setargv.obj`* or *`wsetargv.obj`* file. If your program uses a `main` function, link with *`setargv.obj`*. If your program uses a `wmain` function, link with *`wsetargv.obj`*. Both of these have equivalent behavior. 
 
 To link with *`setargv.obj`* or *`wsetargv.obj`*, use the **`/link`** option. For example:
 
 
@@ -163,7 +163,7 @@ The following table shows example input and expected output, demonstrating the r
 
 The Microsoft compiler optionally allows you to use *wildcard* characters, the question mark (**`?`**) and asterisk (**`*`**), to specify filename and path arguments on the command line.
 
-Command-line arguments are handled by an internal routine in the runtime startup code,, which by default doesn't expand wildcards into separate strings in the `argv` string array. You can enable wildcard expansion by including the *`setargv.obj`* file (*`wsetargv.obj`* file for `wmain`) in your **`/link`** compiler options or your **`LINK`** command line.
+Command-line arguments are handled by an internal routine in the runtime startup code, which by default doesn't expand wildcards into separate strings in the `argv` string array. You can enable wildcard expansion by including the *`setargv.obj`* file (*`wsetargv.obj`* file for `wmain`) in your **`/link`** compiler options or your **`LINK`** command line.
 
 For more information on runtime startup linker options, see [Link options](../c-runtime-library/link-options.md).