diff --git a/R/clipboard.R b/R/clipboard.R
index a4d1fe9..e3b5be2 100644
--- a/R/clipboard.R
+++ b/R/clipboard.R
@@ -43,7 +43,7 @@ read_clip <- function() {
 #' @param content An object to be written to the system clipboard.
 #' @param object_type write_clip() tries to be smart about writing objects in a
 #'   useful manner. If passed a data.frame or matrix, it will format it using
-#'   \code{\link{write.table}} for pasting into an external spreasheet program.
+#'   \code{\link{write.table}} for pasting into an external spreadsheet program.
 #'   It will otherwise coerce the object to a character vector. \code{auto} will
 #'   check the object type, otherwise \code{table} or \code{character} can be
 #'   explicitly specified.
diff --git a/R/clipr-package.R b/R/clipr-package.R
index b1f5d33..4ceebb7 100644
--- a/R/clipr-package.R
+++ b/R/clipr-package.R
@@ -8,7 +8,7 @@
 #' clipboard. \code{\link{read_clip_tbl}} will attempt to process the clipboard
 #' content like a table copied from a spreadsheet program.
 #'
-#' \code{\link{clipr_available}} is useful when buildling packages that
+#' \code{\link{clipr_available}} is useful when building packages that
 #' depend on \link{clipr} functionality.
 #'
 #' @docType package
diff --git a/R/sys_type.R b/R/sys_type.R
index 47d8991..578596a 100644
--- a/R/sys_type.R
+++ b/R/sys_type.R
@@ -5,7 +5,7 @@ sys_type <- function() {
 
 #' Is the system clipboard available?
 #'
-#' Checks to see if the system clipboard is writeable/readable. This may be
+#' Checks to see if the system clipboard is write-able/read-able. This may be
 #' useful if you are developing a package that relies on \link{clipr} and need
 #' to ensure that it will skip tests on machines (e.g. CRAN, Travis) where
 #' the system clipboard may not be available.
diff --git a/man/clipr.Rd b/man/clipr.Rd
index 22fab57..f8c33d6 100644
--- a/man/clipr.Rd
+++ b/man/clipr.Rd
@@ -15,6 +15,6 @@ platform-specific functions for writing values from R to the system
 clipboard. \code{\link{read_clip_tbl}} will attempt to process the clipboard
 content like a table copied from a spreadsheet program.
 
-\code{\link{clipr_available}} is useful when buildling packages that
+\code{\link{clipr_available}} is useful when building packages that
 depend on \link{clipr} functionality.
 }
diff --git a/man/clipr_available.Rd b/man/clipr_available.Rd
index dc682c6..3248697 100644
--- a/man/clipr_available.Rd
+++ b/man/clipr_available.Rd
@@ -10,7 +10,7 @@ clipr_available()
 boolean
 }
 \description{
-Checks to see if the system clipboard is writeable/readable. This may be
+Checks to see if the system clipboard is write-able/read-able. This may be
 useful if you are developing a package that relies on \link{clipr} and need
 to ensure that it will skip tests on machines (e.g. CRAN, Travis) where
 the system clipboard may not be available.
diff --git a/man/write_clip.Rd b/man/write_clip.Rd
index c165fd5..4b3160e 100644
--- a/man/write_clip.Rd
+++ b/man/write_clip.Rd
@@ -12,7 +12,7 @@ write_clip(content, object_type = c("auto", "character", "table"),
 
 \item{object_type}{write_clip() tries to be smart about writing objects in a
 useful manner. If passed a data.frame or matrix, it will format it using
-\code{\link{write.table}} for pasting into an external spreasheet program.
+\code{\link{write.table}} for pasting into an external spreadsheet program.
 It will otherwise coerce the object to a character vector. \code{auto} will
 check the object type, otherwise \code{table} or \code{character} can be
 explicitly specified.}