Fix some typos and link possible exeflags.

doc/src/manual/command-line-interface.md

@@ -131,7 +131,7 @@ The following is a complete list of command-line switches available when launchi
 |`--track-allocation[={none*\|user\|all}]` |Count bytes allocated by each source line (omitting setting is equivalent to "user")|
 |`--track-allocation=@<path>`           |Count bytes but only in files that fall under the given file path/directory. The `@` prefix is required to select this option. A `@` with no path will track the current directory.|
 |`--bug-report=KIND`                    |Launch a bug report session. It can be used to start a REPL, run a script, or evaluate expressions. It first tries to use BugReporting.jl installed in current environment and falls back to the latest compatible BugReporting.jl if not. For more information, see `--bug-report=help`.|
-|`--heap-size-hint=<size>`              |Forces garbage collection if memory usage is higher than that value. The memory hint might be specified in megabytes(500M) or gigabytes(1G)."
+|`--heap-size-hint=<size>`              |Forces garbage collection if memory usage is higher than that value. The memory hint might be specified in megabytes (500M) or gigabytes (1G).|
 |`--compile={yes*\|no\|all\|min}`       |Enable or disable JIT compiler, or request exhaustive or minimal compilation|
 |`--output-o <name>`                    |Generate an object file (including system image data)|
 |`--output-ji <name>`                   |Generate a system image data file (.ji)|

doc/src/manual/distributed-computing.md

@@ -271,10 +271,10 @@ Module [`Distributed`](@ref man-distributed) must be explicitly loaded on the ma
 It is automatically made available on the worker processes.
 
 !!! note
-  Note that workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize
-  their global state (such as command-line switches, global variables, new method definitions, and loaded modules) with any
-  of the other running processes. You may use `addprocs(exeflags="--project")` to initialize a worker with
-  a particular environment, and then `@everywhere using <modulename>` or `@everywhere include("file.jl")`.
+    Note that workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize
+    their global state (such as command-line switches, global variables, new method definitions, and loaded modules) with any
+    of the other running processes. You may use `addprocs(exeflags="--project")` to initialize a worker with
+    a particular environment, and then `@everywhere using <modulename>` or `@everywhere include("file.jl")`.
 
 Other types of clusters can be supported by writing your own custom `ClusterManager`, as described
 below in the [ClusterManagers](@ref) section.

stdlib/Distributed/src/managers.jl

@@ -111,7 +111,7 @@ addprocs([
   version is used on all remote machines because serialization and code distribution might
   fail otherwise.
 
-* `exeflags`: additional flags passed to the worker processes.
+* `exeflags`: additional [command-line switches](@ref command-line-interface) passed to the worker processes.
 
 * `topology`: Specifies how the workers connect to each other. Sending a message between
   unconnected workers results in an error.
@@ -451,7 +451,9 @@ Local workers inherit the current package environment (i.e., active project,
 [`LOAD_PATH`](@ref), and [`DEPOT_PATH`](@ref)) from the main process.
 
 !!! warning
-    Local workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize their global state.
+    Note that workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize
+    their global state (such as command-line switches, global variables, new method definitions, and loaded modules) with any
+    of the other running processes.
 
 **Keyword arguments**:
  - `restrict::Bool`: if `true` (default) binding is restricted to `127.0.0.1`.