diff --git a/chapters/annotations.tex b/chapters/annotations.tex
index ee830ef22..bac9af1bb 100644
--- a/chapters/annotations.tex
+++ b/chapters/annotations.tex
@@ -477,7 +477,7 @@ \subsubsection{Text Markup in Captions}\label{text-markup-in-captions}
 \end{nonnormative}
 
 Vendor-specific markup can be added to a link in the form \lstinline!%[$\mathit{text}$]$\mathit{vendorSpecificMarkup}$($\mathit{link}$)!.
-The vendor-specific markup must not fundamentally alter the appearance of the link, in order to ensure that a tool can safefly ignore all vendor-specific markup and still obtain a result that fits the current context.
+The vendor-specific markup must not fundamentally alter the appearance of the link, in order to ensure that a tool can safely ignore all vendor-specific markup and still obtain a result that fits the current context.
 
 \begin{example}
 The HTML \lstinline!<a>! tag has several attributes with potential application to links, such as \lstinline!target!.
@@ -489,7 +489,7 @@ \subsubsection{Text Markup in Captions}\label{text-markup-in-captions}
 (A line break within a paragraph is not supported, and any paragraph break before the first paragraph or after the last paragraph has no impact.)
 
 Vendor-specific markup for alternative content takes the form \lstinline!%$\mathit{vendorSpecificMarkup}$[$\mathit{text}$]!.
-The vendor-specific markup must not fundamentally alter the appearance of the $\mathit{text}$, in order to ensure that a tool can safefly ignore all vendor-specific markup and still obtain a result that fits the current context.
+The vendor-specific markup must not fundamentally alter the appearance of the $\mathit{text}$, in order to ensure that a tool can safely ignore all vendor-specific markup and still obtain a result that fits the current context.
 
 \begin{example}
 One application of vendor-specific alternative content is to prototype a feature that can later be turned into standardized markup.