diff --git a/docs/getting_started.md b/docs/getting_started.md
index 973665d..17aac44 100644
--- a/docs/getting_started.md
+++ b/docs/getting_started.md
@@ -52,7 +52,7 @@
 
 ## Install Toolchains
 
-If you're developing on Linux or macOS, there are prebuilt toolchain binaries avaiable.
+If you're developing on Linux or macOS, there are prebuilt toolchain binaries available.
 Just run this script from your Zircon working directory:
 
 ```
@@ -255,7 +255,7 @@
 $BUILDDIR/tools/bootserver $BUILDDIR/zircon.bin /path/to/extra.bootfs
 ```
 
-By default bootserver will continue to run and every time it obsveres a netboot
+By default bootserver will continue to run and every time it observes a netboot
 beacon it will send the kernel (and bootfs if provided) to that device.  If you
 pass the -1 option, bootserver will exit after a successful boot instead.
 
diff --git a/docs/kernel_scheduling.md b/docs/kernel_scheduling.md
index f1e7656..77421f5 100644
--- a/docs/kernel_scheduling.md
+++ b/docs/kernel_scheduling.md
@@ -129,7 +129,7 @@
 6.  Any active CPU in the affinity mask.
 
 If the thread is running on a CPU not in its affinity mask (due to case
-5 above) the scheduler will try to rectify this everytime the thread is
+5 above) the scheduler will try to rectify this every time the thread is
 preempted, yields, or voluntarily reschedules. Also if the thread
 changes its affinity mask the scheduler may migrate it.
 
@@ -164,5 +164,5 @@
 a priority queue of -1. It is used to track idle time and can be used by
 platform implementations for a low power wait mode.
 
-Realtime threads (marked with THREAD_FLAG_REAL_TIME) are allowed to run without
+Realtime threads (marked with `THREAD_FLAG_REAL_TIME`) are allowed to run without
 preemption and will run until they block, yield, or manually reschedule.
diff --git a/docs/objects/channel.md b/docs/objects/channel.md
index adfdcfc..ae993d3 100644
--- a/docs/objects/channel.md
+++ b/docs/objects/channel.md
@@ -43,7 +43,7 @@
 another, even if a write was in progress, the ordering of messages is guaranteed
 to be parsimonious; packets before the transfer event originate from the
 previous owner and packets after the transfer belong to the new owner. The same
-applies if a read was in progress when the endpoint was transfered.
+applies if a read was in progress when the endpoint was transferred.
 
 The above sequential guarantee is not provided for other kernel objects, even if
 the last remaining handle is stripped of the **ZX_RIGHT_DUPLICATE** right.
diff --git a/docs/syscalls/handle_replace.md b/docs/syscalls/handle_replace.md
index df2f370..49730ae 100644
--- a/docs/syscalls/handle_replace.md
+++ b/docs/syscalls/handle_replace.md
@@ -31,7 +31,7 @@
 
 ## RETURN VALUE
 
-**handle_replace**() returns ZX_OK and the replacement handle (via *out)
+**handle_replace**() returns **ZX_OK** and the replacement handle (via *out*)
 on success.
 
 ## ERRORS
diff --git a/docs/syscalls/port_wait.md b/docs/syscalls/port_wait.md
index 70524be..d44892d 100644
--- a/docs/syscalls/port_wait.md
+++ b/docs/syscalls/port_wait.md
@@ -97,7 +97,7 @@
 
 **ZX_ERR_INVALID_ARGS** *packet* isn't a valid pointer
 
-**ZX_ERR_ACCESS_DENIED** *handle* does not have **ZX_RIGHT_READ* and may
+**ZX_ERR_ACCESS_DENIED** *handle* does not have **ZX_RIGHT_READ** and may
 not be waited upon.
 
 **ZX_ERR_TIMED_OUT** *deadline* passed and no packet was available.
diff --git a/docs/syscalls/socket_read.md b/docs/syscalls/socket_read.md
index cab8e0c..09d105a 100644
--- a/docs/syscalls/socket_read.md
+++ b/docs/syscalls/socket_read.md
@@ -57,7 +57,7 @@
 
 **ZX_ERR_INVALID_ARGS** If any of *buffer* or *actual* are non-NULL
 but invalid pointers, or if *buffer* is NULL, or if *options* is not either zero
-or **ZX_SOCKET_CONTROL*.
+or **ZX_SOCKET_CONTROL**.
 
 **ZX_ERR_ACCESS_DENIED**  *handle* does not have **ZX_RIGHT_READ**.
 
diff --git a/docs/syscalls/task_kill.md b/docs/syscalls/task_kill.md
index 8ac1792..2440a3d 100644
--- a/docs/syscalls/task_kill.md
+++ b/docs/syscalls/task_kill.md
@@ -23,7 +23,7 @@
 all its children are considered to be in the dead state and most operations
 will no longer succeed.
 
-If *handle* is a job and the syscall is sucessful, the job cannot longer be
+If *handle* is a job and the syscall is successful, the job cannot longer be
 used to create new processes.
 
 ## RIGHTS
diff --git a/docs/syscalls/thread_create.md b/docs/syscalls/thread_create.md
index 2297177..e2ffec2 100644
--- a/docs/syscalls/thread_create.md
+++ b/docs/syscalls/thread_create.md
@@ -25,7 +25,7 @@
 
 Thread handles may be waited on and will assert the signal
 *ZX_THREAD_TERMINATED* when the thread stops executing (due to
-*thread_exit**() being called).
+**thread_exit**() being called).
 
 *process* is the controlling [process object](../objects/process.md) for the
 new thread, which will become a child of that process.
diff --git a/docs/syscalls/thread_start.md b/docs/syscalls/thread_start.md
index 27861b1..bf82b1a 100644
--- a/docs/syscalls/thread_start.md
+++ b/docs/syscalls/thread_start.md
@@ -25,7 +25,7 @@
 
 Thread handles may be waited on and will assert the signal
 *ZX_THREAD_TERMINATED* when the thread stops executing (due to
-*thread_exit**() being called.
+**thread_exit**() being called.
 
 *entry* shall point to a function that must call **thread_exit**() or
 **futex_wake_handle_close_thread_exit**() or
diff --git a/docs/syscalls/timer_create.md b/docs/syscalls/timer_create.md
index 7d9e3d0..9dad3dc 100644
--- a/docs/syscalls/timer_create.md
+++ b/docs/syscalls/timer_create.md
@@ -17,7 +17,7 @@
 
 **timer_create**() creates a timer, an object that can signal
 when a specified point in time has been reached. The only valid
-*clock_id* is ZX_CLOCK_MONOTONIC.
+*clock_id* is **ZX_CLOCK_MONOTONIC**.
 
 The *options* value specifies the coalescing behavior which
 controls whether the system can fire the time earlier or later
@@ -32,10 +32,10 @@
 + **ZX_TIMER_SLACK_LATE** coalescing is allowed only with later
   timers.
 
-Passing 0 in options is equivalent to ZX_TIMER_SLACK_CENTER.
+Passing 0 in options is equivalent to **ZX_TIMER_SLACK_CENTER**.
 
-The returned handle has the ZX_RIGHT_DUPLICATE, ZX_RIGHT_TRANSFER,
-ZX_RIGHT_READ and ZX_RIGHT_WRITE right.
+The returned handle has the **ZX_RIGHT_DUPLICATE**, **ZX_RIGHT_TRANSFER**,
+**ZX_RIGHT_READ** and **ZX_RIGHT_WRITE** right.
 
 ## RIGHTS
 
@@ -51,8 +51,8 @@
 ## ERRORS
 
 **ZX_ERR_INVALID_ARGS**  *out* is an invalid pointer or NULL or
-*options* is not one of the ZX_TIMER_SLACK values or *clock_id* is
-any value other than ZX_CLOCK_MONOTONIC.
+*options* is not one of the **ZX_TIMER_SLACK** values or *clock_id* is
+any value other than **ZX_CLOCK_MONOTONIC**.
 
 **ZX_ERR_NO_MEMORY**  Failure due to lack of memory.
 There is no good way for userspace to handle this (unlikely) error.
diff --git a/docs/syscalls/vmar_map.md b/docs/syscalls/vmar_map.md
index 0ce5228..1323651 100644
--- a/docs/syscalls/vmar_map.md
+++ b/docs/syscalls/vmar_map.md
@@ -97,7 +97,7 @@
 ## NOTES
 
 The VMO that backs a memory mapping can be resized to a smaller size. This can cause the
-thread is reading or writting to the VMAR region to fault. To avoid this hazard, services
+thread is reading or writing to the VMAR region to fault. To avoid this hazard, services
 that receive VMOs from clients should use **ZX_VM_REQUIRE_NON_RESIZABLE** when mapping
 the VMO.