diff --git a/R/as_data_frame.R b/R/as_data_frame.R
index 48352e7e27..f2a5d039d2 100644
--- a/R/as_data_frame.R
+++ b/R/as_data_frame.R
@@ -28,8 +28,19 @@
 #'
 #' This facilitates conversion of the `gt_tbl` object to a data frame.
 #'
-#' @param x An object of class `gt_tbl`.
-#' @param ... Any additional parameters.
+#' @param x *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Optional parameters*
+#'
+#'   `<multiple expressions>` --- (`optional`)
+#'
+#'   Anything provided here in `...` will be passed to internal function calls
+#'   that can consume it.
 #'
 #' @keywords internal
 #'
diff --git a/R/data_color.R b/R/data_color.R
index 39a873e292..12b06d774b 100644
--- a/R/data_color.R
+++ b/R/data_color.R
@@ -66,76 +66,180 @@
 #' without running into too many errors.
 #'
 #' @inheritParams fmt_number
-#' @param columns,rows The columns and rows to which cell data color operations
-#'   are constrained.
-#' @param direction Should the color computations be performed column-wise or
-#'   row-wise? By default this is set with the `"column"` keyword and colors
-#'   will be applied down columns. The alternative option with the `"row"`
-#'   keyword ensures that the color mapping works across rows.
-#' @param target_columns For indirect column coloring treatments, we can supply
-#'   the columns that will receive the styling. The necessary precondition is
-#'   that we must use `direction = "column"`. If `columns` resolves to a single
-#'   column then we may use one or more columns in `target_columns`. If on the
-#'   other hand `columns` resolves to multiple columns, then `target_columns`
-#'   must resolve to the same multiple.
-#' @param method A method for computing color based on the data within body
-#'   cells. Can be `"auto"` (the default), `"numeric"`, `"bin"`, `"quantile"`,
-#'   or `"factor"`. The `"auto"` method will automatically choose the
-#'   `"numeric"` method for numerical input data or the `"factor"` method for
-#'   any non-numeric inputs.
-#' @param palette A vector of color names, the name of an **RColorBrewer**
-#'   palette, the name of a **viridis** palette, or a discrete palette
-#'   accessible from the **paletteer** package using the `<package>::<palette>`
-#'   syntax (e.g., `"wesanderson::IsleofDogs1"`). If providing a vector of
-#'   colors as a palette, each color value provided must either be a color name
-#'   (Only R/X11 color names or CSS 3.0 color names) or a hexadecimal string in
-#'   the form of `"#RRGGBB"` or `"#RRGGBBAA"`. If nothing is provided here, the
-#'   default R color palette is used (i.e., the colors from `palette()`).
-#' @param domain The possible values that can be mapped. For the `"numeric"` and
-#'   `"bin"` methods, this can be a numeric range specified with a length of two
-#'   vector. Representative numeric data is needed for the `"quantile"` method
-#'   and categorical data must be used for the `"factor"` method. If `NULL` (the
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which cell data color operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for cell data color operations. The default
+#'   [everything()] results in all rows in `columns` being formatted.
+#'   Alternatively, we can supply a vector of row captions within [c()], a
+#'   vector of row indices, or a select helper function. Examples of select
+#'   helper functions include [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], [num_range()], and [everything()]. We can also use
+#'   expressions to filter down to the rows we need (e.g., `[colname_1] > 100 &
+#'   [colname_2] < 50`).
+#'
+#' @param direction *Color computation direction*
+#'
+#'   `singl-kw:[column|row]` --- *default:* `"column"`
+#'
+#'   Should the color computations be performed column-wise or row-wise? By
+#'   default this is set with the `"column"` keyword and colors will be applied
+#'   down columns. The alternative option with the `"row"` keyword ensures that
+#'   the color mapping works across rows.
+#'
+#' @param target_columns *Indirect columns to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `NULL` `optional`
+#'
+#'   For indirect column coloring treatments, we can supply the columns that
+#'   will receive the styling. The necessary precondition is that we must use
+#'   `direction = "column"`. If `columns` resolves to a single column then we
+#'   may use one or more columns in `target_columns`. If on the other hand
+#'   `columns` resolves to multiple columns, then `target_columns` must resolve
+#'   to the same multiple.
+#'
+#' @param method *Color computation method*
+#'
+#'   `singl-kw:[auto|numeric|bin|quantile|factor]` --- *default:* `"auto"`
+#'
+#'   A method for computing color based on the data within body cells. Can be
+#'   `"auto"` (the default), `"numeric"`, `"bin"`, `"quantile"`, or `"factor"`.
+#'   The `"auto"` method will automatically choose the `"numeric"` method for
+#'   numerical input data or the `"factor"` method for any non-numeric inputs.
+#'
+#' @param palette *Color palette*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A vector of color names, the name of an **RColorBrewer** palette, the name
+#'   of a **viridis** palette, or a discrete palette accessible from the
+#'   **paletteer** package using the `<package>::<palette>` syntax (e.g.,
+#'   `"wesanderson::IsleofDogs1"`). If providing a vector of colors as a
+#'   palette, each color value provided must either be a color name (Only R/X11
+#'   color names or CSS 3.0 color names) or a hexadecimal string in the form of
+#'   `"#RRGGBB"` or `"#RRGGBBAA"`. If nothing is provided here, the default R
+#'   color palette is used (i.e., the colors from `palette()`).
+#'
+#' @param domain *Value domain*
+#'
+#'   `vector<numeric|integer|character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The possible values that can be mapped. For the `"numeric"` and `"bin"`
+#'   methods, this can be a numeric range specified with a length of two vector.
+#'   Representative numeric data is needed for the `"quantile"` method and
+#'   categorical data must be used for the `"factor"` method. If `NULL` (the
 #'   default value), the values in each column or row (depending on `direction`)
 #'   value will represent the domain.
-#' @param bins For `method = "bin"` this can either be a numeric vector of two
-#'   or more unique cut points, or, a single numeric value (greater than or
-#'   equal to `2`) giving the number of intervals into which the domain values
-#'   are to be cut. By default, this is `8`.
-#' @param quantiles For `method = "quantile"` this is the number of equal-size
-#'   quantiles to use. By default, this is set to `4`.
-#' @param levels For `method = "factor"` this allows for an alternate way of
-#'   specifying levels. If anything is provided here then any value supplied to
-#'   `domain` will be ignored. This should be a character vector of unique
-#'   values.
-#' @param ordered For `method = "factor"`, setting this to `TRUE` means that the
-#'   vector supplied to `domain` will be treated as being in the correct order
-#'   if that vector needs to be coerced to a factor. By default, this is
-#'   `FALSE`.
-#' @param na_color The color to use for missing values. By default (with
-#'   `na_color = NULL`) gray, `"#808080"`, will be used.
-#' @param alpha An optional, fixed alpha transparency value that will be applied
-#'   to all of the `colors` provided (regardless of whether a color palette was
-#'   directly supplied or generated through a color mapping function).
-#' @param reverse Should the colors computed operate in reverse order?
-#'   If `TRUE` then colors that normally change from red to blue will change in
-#'   the opposite direction. By default, this is `FALSE`.
-#' @param fn A color-mapping function. The function should be able to take a
-#'   vector of data values as input and return an equal-length vector of color
-#'   values. The `col_*()` functions provided in the **scales** package (i.e.,
+#'
+#' @param bins *Specification of bin number*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `8`
+#'
+#'   For `method = "bin"` this can either be a numeric vector of two or more
+#'   unique cut points, or, a single numeric value (greater than or equal to
+#'   `2`) giving the number of intervals into which the domain values are to be
+#'   cut. By default, this is `8`.
+#'
+#' @param quantiles *Specification of quantile number*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `4`
+#'
+#'   For `method = "quantile"` this is the number of equal-size quantiles to
+#'   use. By default, this is set to `4`.
+#'
+#' @param levels *Specification of factor levels*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   For `method = "factor"` this allows for an alternate way of specifying
+#'   levels. If anything is provided here then any value supplied to `domain`
+#'   will be ignored. This should be a character vector of unique values.
+#'
+#' @param ordered *Use an ordered factor*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   For `method = "factor"`, setting this to `TRUE` means that the vector
+#'   supplied to `domain` will be treated as being in the correct order if that
+#'   vector needs to be coerced to a factor. By default, this is `FALSE`.
+#'
+#' @param na_color *Default color for `NA` values*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The color to use for missing values. By default (with `na_color = NULL`),
+#'   the color gray (`"#808080"`) will be used. This option has no effect if
+#'   providing a color-mapping function to `fn`.
+#'
+#' @param alpha *Transparency value*
+#'
+#'   `scalar<numeric|integer>(0>=val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional, fixed alpha transparency value that will be applied to all of
+#'   the `colors` provided (regardless of whether a color palette was directly
+#'   supplied or generated through a color mapping function).
+#'
+#' @param reverse *Reverse order of computed colors*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the colors computed operate in the reverse order? If `TRUE` then
+#'   colors that normally change from red to blue will change in the opposite
+#'   direction.
+#'
+#' @param fn *Color-mapping function*
+#'
+#'   `function` --- *default:* `NULL` (`optional`)
+#'
+#'   A color-mapping function. The function should be able to take a vector of
+#'   data values as input and return an equal-length vector of color values. The
+#'   `col_*()` functions provided in the **scales** package (i.e.,
 #'   [scales::col_numeric()], [scales::col_bin()], and [scales::col_factor()])
 #'   can be invoked here with options, as those functions themselves return a
 #'   color-mapping function.
-#' @param apply_to Which style element should the colors be applied to? Options
-#'   include the cell background (the default, given as `"fill"`) or the cell
-#'   text (`"text"`).
-#' @param autocolor_text An option to let **gt** modify the coloring of text
-#'   within cells undergoing background coloring. This will result in better
-#'   text-to-background color contrast. By default, this is set to `TRUE`.
-#' @param contrast_algo The color contrast algorithm to use when
-#'   `autocolor_text = TRUE`. By default this is `"apca"` (Accessible Perceptual
-#'   Contrast Algorithm) and the alternative to this is `"wcag"` (Web Content
-#'   Accessibility Guidelines).
-#' @param colors Deprecated. Use the `fn` argument instead to provide a
+#'
+#' @param apply_to *How to apply color*
+#'
+#'   `singl-kw:[fill|text]` --- *default:* `"fill"`
+#'
+#'   Which style element should the colors be applied to? Options include the
+#'   cell background (the default, given as `"fill"`) or the cell text
+#'   (`"text"`).
+#'
+#' @param autocolor_text *Automatically recolor text*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to let **gt** modify the coloring of text within cells undergoing
+#'   background coloring. This will result in better text-to-background color
+#'   contrast. By default, this is set to `TRUE`.
+#'
+#' @param contrast_algo *Color contrast algorithm choice*
+#'
+#'   `singl-kw:[apca|wcag]` --- *default:* `"apca"`
+#'
+#'   The color contrast algorithm to use when `autocolor_text = TRUE`. By
+#'   default this is `"apca"` (Accessible Perceptual Contrast Algorithm) and the
+#'   alternative to this is `"wcag"` (Web Content Accessibility Guidelines).
+#'
+#' @param colors *[Deprecated] Color mapping function*
+#'
+#'   `function` --- *default:* `NULL` (`optional`)
+#'
+#'   This argument is deprecated. Use the `fn` argument instead to provide a
 #'   **scales**-based color-mapping function. If providing a palette, use the
 #'   `palette` argument.
 #'
diff --git a/R/export.R b/R/export.R
index a4444ec42d..ec0e650c17 100644
--- a/R/export.R
+++ b/R/export.R
@@ -69,15 +69,33 @@
 #' package needs to be installed before attempting to save any table as a
 #' `.docx` document.
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param filename The file name to create on disk. Ensure that an extension
-#'   compatible with the output types is provided (`.html`, `.tex`, `.ltx`,
-#'   `.rtf`, `.docx`). If a custom save function is provided then the file
-#'   extension is disregarded.
-#' @param path An optional path to which the file should be saved (combined with
-#'   filename).
-#' @param ... All other options passed to the appropriate internal saving
-#'   function.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param filename *Output filename*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The file name to create on disk. Ensure that an extension compatible with
+#'   the output types is provided (`.html`, `.tex`, `.ltx`, `.rtf`, `.docx`). If
+#'   a custom save function is provided then the file extension is disregarded.
+#'
+#' @param path *Output path*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional path to which the file should be saved (combined with
+#'   `filename`).
+#'
+#' @param ... *Additional options*
+#'
+#'   `<named arguments>`
+#'
+#'   All other options passed to the appropriate internal saving function.
 #'
 #' @return Invisibly returns `TRUE` if the export process is successful.
 #'
@@ -430,7 +448,7 @@ gt_save_docx <- function(
     output = filename
   )
 
-  if(needs_gt_as_word_post_processing(word_md_text)){
+  if (needs_gt_as_word_post_processing(word_md_text)) {
     gt_as_word_post_processing(filename)
   }
 
@@ -474,11 +492,21 @@ gtsave_filename <- function(path, filename) {
 #' tags. This option is preferable when using the output HTML table in an
 #' emailing context.
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param inline_css An option to supply styles to table elements as inlined CSS
-#'   styles. This is useful when including the table HTML as part of an HTML
-#'   email message body, since inlined styles are largely supported in email
-#'   clients over using CSS in a `<style>` block.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param inline_css *Use inline CSS*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to supply styles to table elements as inlined CSS styles. This is
+#'   useful when including the table HTML as part of an HTML email message body,
+#'   since inlined styles are largely supported in email clients over using CSS
+#'   in a `<style>` block.
 #'
 #' @section Examples:
 #'
@@ -558,7 +586,12 @@ as_raw_html <- function(
 #' `as.character()` on the created object will result in a single-element vector
 #' containing the LaTeX code.
 #'
-#' @param data A table object that is created using the [gt()] function.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
 #'
 #' @details
 #'
@@ -674,16 +707,39 @@ as_latex <- function(data) {
 #' vector. This object can be used with `writeLines()` to generate a valid .rtf
 #' file that can be opened by RTF readers.
 #'
-#' @param data A table object that is created using the `gt()` function.
-#' @param incl_open,incl_close Options that govern whether the opening or
-#'   closing `"{"` and `"}"` should be included. By default, both options are
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param incl_open,incl_close *Include opening/closing braces*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Options that govern whether the opening or closing `"{"` and `"}"` should
+#'   be included. By default, both options are `TRUE`.
+#'
+#' @param incl_header *Include RTF header*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the RTF header be included in the output? By default, this is
 #'   `TRUE`.
-#' @param incl_header Should the RTF header be included in the output? By
-#'   default, this is `TRUE`.
-#' @param incl_page_info Should the RTF output include directives for the
-#'   document pages? This is `TRUE` by default.
-#' @param incl_body An option to include the body of RTF document. By
-#'   default, this is `TRUE`.
+#'
+#' @param incl_page_info *Include RTF page information*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the RTF output include directives for the document pages? This is
+#'   `TRUE` by default.
+#'
+#' @param incl_body *Include RTF body*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to include the body of RTF document. By default, this is `TRUE`.
 #'
 #' @section Examples:
 #'
@@ -794,21 +850,49 @@ as_rtf <- function(
 #'
 #' @description
 #'
-#' Get the Open Office XML table tag content from a `gt_tbl` object as as a
+#' Get the Open Office XML table tag content from a `gt_tbl` object as a
 #' single-element character vector.
 #'
-#' @param data A table object that is created using the `gt()` function.
-#' @param align An option for table alignment. Can either be `"center"` (the
-#'   default), `"left"`, or `"right"`.
-#' @param caption_location Determines where the caption should be positioned.
-#'   This can either be `"top"` (the default), `"bottom"`, or `"embed"`.
-#' @param caption_align Determines the alignment of the caption. This is
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param align *Table alignment*
+#'
+#'   `scalar<character>` --- *default:* `"center"`
+#'
+#'   An option for table alignment. Can either be `"center"`, `"left"`, or
+#'   `"right"`.
+#'
+#' @param caption_location *Caption location*
+#'
+#'   `singl-kw:[top|bottom|embed]` --- *default:* `"top"`
+#'
+#'   Determines where the caption should be positioned. This can either be
+#'   `"top"`, `"bottom"`, or `"embed"`.
+#'
+#' @param caption_align *Caption alignment*
+#'
+#'   Determines the alignment of the caption. This is
 #'   either `"left"` (the default), `"center"`, or `"right"`. This option is
 #'   only used when `caption_location` is not set as `"embed"`.
-#' @param split A `TRUE` or `FALSE` (the default) value that indicates whether
-#'   to activate the Word option `Allow row to break across pages`.
-#' @param keep_with_next A `TRUE` (the default) or `FALSE` value that indicates
-#'   whether a table should use Word option `keep rows together`.
+#'
+#' @param split *Allow splitting*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   A logical value that indicates whether to activate the Word option
+#'   `Allow row to break across pages`.
+#'
+#' @param keep_with_next *Keeping rows together*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   A logical value that indicates whether a table should use Word option
+#'   `keep rows together`.
 #'
 #' @section Examples:
 #'
@@ -1010,7 +1094,12 @@ as_word_tbl_body <- function(
 #' contain the `group_id` and `rowname` columns, whereby `rowname` contains
 #' descriptive stub labels for the summary rows.
 #'
-#' @param data A table object that is created using the [gt()] function.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
 #'
 #' @return A list of data frames containing summary data.
 #'
@@ -1125,24 +1214,43 @@ extract_summary <- function(data) {
 #' Get a vector of cell data from a `gt_tbl` object. The output vector will have
 #' cell data formatted in the same way as the table.
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param columns The columns containing the cells to extract. Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
-#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
-#'   [num_range()], and [everything()].
-#' @param rows Optional rows to limit the extraction of cells. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   formatted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param output The output style of the resulting character vector. This can
-#'   either be `"auto"` (the default), `"plain"`, `"html"`, `"latex"`, `"rtf"`,
-#'   or `"word"`. In **knitr** rendering (i.e., Quarto or R Markdown), the
-#'   `"auto"` option will choose the correct `output` value
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   Can either be a series of column names provided in [c()], a vector of
+#'   column indices, or a select helper function. Examples of select helper
+#'   functions include [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for extraction. The default [everything()] results in all
+#'   rows in `columns` being formatted. Alternatively, we can supply a vector of
+#'   row captions within [c()], a vector of row indices, or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()]. We can also use expressions to filter down to the rows we
+#'   need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param output *Output format*
+#'
+#'   `singl-kw:[auto|plain|html|latex|rtf|word]` --- *default:* `"auto"`
+#'
+#'   The output style of the resulting character vector. This can either be
+#'   `"auto"` (the default), `"plain"`, `"html"`, `"latex"`, `"rtf"`, or
+#'   `"word"`. In **knitr** rendering (i.e., Quarto or R Markdown), the `"auto"`
+#'   option will choose the correct `output` value
 #'
 #' @return A vector of cell data extracted from a **gt** table.
 #'
diff --git a/R/format_data.R b/R/format_data.R
index a14f4d9389..9e103b5a09 100644
--- a/R/format_data.R
+++ b/R/format_data.R
@@ -43,90 +43,187 @@
 #' - locale-based formatting: providing a locale ID will result in number
 #' formatting specific to the chosen locale
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param columns The columns to format. Can either be a series of column names
-#'   provided in [c()], a vector of column indices, or a helper function
-#'   focused on selections. The select helper functions are: [starts_with()],
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   Can either be a series of column names provided in [c()], a vector of
+#'   column indices, or a select helper function. Examples of select helper
+#'   functions include [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   undergo formatting. The default [everything()] results in all rows in
+#'   `columns` being formatted. Alternatively, we can supply a vector of row
+#'   captions within [c()], a vector of row indices, or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
 #'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
-#'   [everything()].
-#' @param rows Optional rows to format. Providing [everything()] (the
-#'   default) results in all rows in `columns` being formatted. Alternatively,
-#'   we can supply a vector of row captions within [c()], a vector of row
-#'   indices, or a helper function focused on selections. The select helper
-#'   functions are: [starts_with()], [ends_with()], [contains()], [matches()],
-#'   [one_of()], [num_range()], and [everything()]. We can also use expressions
-#'   to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param decimals An option to specify the exact number of decimal places to
-#'   use. The default number of decimal places is `2`.
-#' @param n_sigfig A option to format numbers to *n* significant figures. By
-#'   default, this is `NULL` and thus number values will be formatted according
-#'   to the number of decimal places set via `decimals`. If opting to format
-#'   according to the rules of significant figures, `n_sigfig` must be a number
-#'   greater than or equal to `1`. Any values passed to the `decimals` and
-#'   `drop_trailing_zeros` arguments will be ignored.
-#' @param drop_trailing_zeros A logical value that allows for removal of
-#'   trailing zeros (those redundant zeros after the decimal mark).
-#' @param drop_trailing_dec_mark A logical value that determines whether decimal
-#'   marks should always appear even if there are no decimal digits to display
-#'   after formatting (e.g, `23` becomes `23.`). The default for this is `TRUE`,
-#'   which means that trailing decimal marks are not shown.
-#' @param use_seps An option to use digit group separators. The type of digit
-#'   group separator is set by `sep_mark` and overridden if a locale ID is
-#'   provided to `locale`. This setting is `TRUE` by default.
-#' @param accounting An option to use accounting style for values. With `FALSE`
-#'   (the default), negative values will be shown with a minus sign. Using
-#'   `accounting = TRUE` will put negative values in parentheses.
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#'   This value will be ignored if using any of the `suffixing` options (i.e.,
-#'   where `suffixing` is not set to `FALSE`).
-#' @param suffixing An option to scale and apply suffixes to larger numbers
-#'   (e.g., `1924000` can be transformed to `1.92M`). This option can accept a
-#'   logical value, where `FALSE` (the default) will not perform this
-#'   transformation and `TRUE` will apply thousands (`K`), millions (`M`),
-#'   billions (`B`), and trillions (`T`) suffixes after automatic value scaling.
-#'   We can also specify which symbols to use for each of the value ranges by
-#'   using a character vector of the preferred symbols to replace the defaults
-#'   (e.g., `c("k", "Ml", "Bn", "Tr")`).
+#'   [everything()]. We can also use expressions to filter down to the rows we
+#'   need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param decimals *Number of decimal places*
+#'
+#'   `scalar<numeric|integer>(val>=0)` --- *default:* `2`
+#'
+#'   This corresponds to the exact number of decimal places to use. A value
+#'   such as `2.34` can, for example, be formatted with `0` decimal places and
+#'   it would result in `"2"`. With `4` decimal places, the formatted value
+#'   becomes `"2.3400"`. The trailing zeros can be removed with
+#'   `drop_trailing_zeros = TRUE`. If you always need `decimals = 0`, the
+#'   [fmt_integer()] function should be considered.
+#'
+#' @param n_sigfig *Number of significant figures*
+#'
+#'   `scalar<numeric|integer>(val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   A option to format numbers to *n* significant figures. By default, this is
+#'   `NULL` and thus number values will be formatted according to the number of
+#'   decimal places set via `decimals`. If opting to format according to the
+#'   rules of significant figures, `n_sigfig` must be a number greater than or
+#'   equal to `1`. Any values passed to the `decimals` and `drop_trailing_zeros`
+#'   arguments will be ignored.
+#'
+#' @param drop_trailing_zeros *Drop any trailing zeros*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   A logical value that allows for removal of trailing zeros (those redundant
+#'   zeros after the decimal mark).
+#'
+#' @param drop_trailing_dec_mark *Drop the trailing decimal mark*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   A logical value that determines whether decimal marks should always appear
+#'   even if there are no decimal digits to display after formatting (e.g., `23`
+#'   becomes `23.` if `FALSE`). By default trailing decimal marks are not shown.
+#'
+#' @param use_seps *Use digit group separators*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to use digit group separators. The type of digit group separator
+#'   is set by `sep_mark` and overridden if a locale ID is provided to `locale`.
+#'   This setting is `TRUE` by default.
+#'
+#' @param accounting *Use accounting style*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option to use accounting style for values. Normally, negative values
+#'   will be shown with a minus sign but using accounting style will instead put
+#'   any negative values in parentheses.
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied. This value will be
+#'   ignored if using any of the `suffixing` options (i.e., where `suffixing` is
+#'   not set to `FALSE`).
+#'
+#' @param suffixing *Specification for large-number suffixing*
+#'
+#'   `scalar<logical>|vector<character>` --- *default:* `FALSE`
+#'
+#'   The `suffixing` option allows us to scale and apply suffixes to larger
+#'   numbers (e.g., `1924000` can be transformed to `1.92M`). This option can
+#'   accept a logical value, where `FALSE` (the default) will not perform this
+#'   transformation and `TRUE` will apply thousands (`"K"`), millions (`"M"`),
+#'   billions (`"B"`), and trillions (`"T"`) suffixes after automatic value
+#'   scaling.
+#'
+#'   We can alternatively provide a character vector that serves as a
+#'   specification for which symbols are to used for each of the value ranges.
+#'   These preferred symbols will replace the defaults (e.g.,
+#'   `c("k", "Ml", "Bn", "Tr")` replaces `"K"`, `"M"`, `"B"`, and `"T"`).
 #'
 #'   Including `NA` values in the vector will ensure that the particular range
-#'   will either not be included in the transformation (e.g, `c(NA, "M", "B",
-#'   "T")` won't modify numbers in the thousands range) or the range will
-#'   inherit a previous suffix (e.g., with `c("K", "M", NA, "T")`, all numbers
-#'   in the range of millions and billions will be in terms of millions).
+#'   will either not be included in the transformation (e.g.,
+#'   `c(NA, "M", "B", "T")` won't modify numbers at all in the thousands range)
+#'   or the range will inherit a previous suffix (e.g., with
+#'   `c("K", "M", NA, "T")`, all numbers in the range of millions and billions
+#'   will be in terms of millions).
 #'
 #'   Any use of `suffixing` (where it is not set expressly as `FALSE`) means
 #'   that any value provided to `scale_by` will be ignored.
 #'
 #'   If using `system = "ind"` then the default suffix set provided by
-#'   `suffixing = TRUE` will be `c(NA, "L", "Cr")`. This doesn't apply suffixes
-#'   to the thousands range, but does express values in lakhs and crores.
-#'
-#' @param pattern A formatting pattern that allows for decoration of the
-#'   formatted value. The value itself is represented by `{x}` and all other
-#'   characters are taken to be string literals.
-#' @param sep_mark The mark to use as a separator between groups of digits
-#'   (e.g., using `sep_mark = ","` with `1000` would result in a formatted value
-#'   of `1,000`).
-#' @param dec_mark The character to use as a decimal mark (e.g., using `dec_mark
-#'   = ","` with `0.152` would result in a formatted value of `0,152`).
-#' @param force_sign Should the positive sign be shown for positive values
-#'   (effectively showing a sign for all values except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative numbers will
-#'   display a minus sign. This option is disregarded when using accounting
-#'   notation with `accounting = TRUE`.
-#' @param system The numbering system to use. By default, this is the
-#'   international numbering system (`"intl"`) whereby grouping separators
-#'   (i.e., `sep_mark`) are separated by three digits. The alternative system,
-#'   the Indian numbering system (`"ind"`) uses grouping separators that
-#'   correspond to thousand, lakh, crore, and higher quantities.
-#' @param locale An optional locale identifier that can be used for formatting
-#'   the value according the locale's rules. Examples include `"en"` for English
-#'   (United States) and `"fr"` for French (France). The use of a locale ID will
-#'   override any locale-specific values provided. We can use the
-#'   [info_locales()] function as a useful reference for all of the locales that
-#'   are supported.
+#'   `suffixing = TRUE` will be the equivalent of `c(NA, "L", "Cr")`. This
+#'   doesn't apply suffixes to the thousands range, but does express values in
+#'   *lakhs* and *crores*.
+#'
+#' @param pattern *Specification of the formatting pattern*
+#'
+#'   `scalar<character>` --- *default:* `"{x}"`
+#'
+#'   A formatting pattern that allows for decoration of the formatted value. The
+#'   formatted value is represented by the `{x}` (which can be used multiple
+#'   times, if needed) and all other characters will be interpreted as string
+#'   literals.
+#'
+#' @param sep_mark *Separator mark for digit grouping*
+#'
+#'   `scalar<character>` --- *default:* `","`
+#'
+#'   The string to use as a separator between groups of digits. For example,
+#'   using `sep_mark = ","` with a value of `1000` would result in a formatted
+#'   value of `"1,000"`. This argument is ignored if a `locale` is supplied
+#'   (i.e., is not `NULL`).
+#'
+#' @param dec_mark *Decimal mark*
+#'
+#'   `scalar<character>` --- *default:* `"."`
+#'
+#'   The string to be used as the decimal mark. For example, using
+#'   `dec_mark = ","` with the value `0.152` would result in a formatted value
+#'   of `"0,152"`). This argument is ignored if a `locale` is supplied (i.e., is
+#'   not `NULL`).
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive values (effectively showing
+#'   a sign for all values except zero)? If so, use `TRUE` for this option. The
+#'   default is `FALSE`, where only negative numbers will display a minus sign.
+#'   This option is disregarded when using accounting notation with
+#'   `accounting = TRUE`.
+#'
+#' @param system *Numbering system for grouping separators*
+#'
+#'   `singl-kw:[intl|ind]` --- *default:* `"intl"`
+#'
+#'   The international numbering system (keyword: `"intl"`) is widely used and
+#'   its grouping separators (i.e., `sep_mark`) are always separated by three
+#'   digits. The alternative system, the Indian numbering system (keyword:
+#'   `"ind"`), uses grouping separators that correspond to thousand, lakh,
+#'   crore, and higher quantities.
+#'
+#' @param locale *Locale identifier*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional locale identifier that can be used for formatting values
+#'   according the locale's rules. Examples include `"en"` for English (United
+#'   States) and `"fr"` for French (France). We can use the [info_locales()]
+#'   function as a useful reference for all of the locales that are supported. A
+#'   locale ID can be also set in the initial [gt()] function call (where it
+#'   would be used automatically by any function with a `locale` argument) but a
+#'   `locale` value provided here will override that global locale.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -422,24 +519,37 @@ fmt_number <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param suffixing An option to scale and apply suffixes to larger numbers
-#'   (e.g., `1924000` can be transformed to `2M`). This option can accept a
-#'   logical value, where `FALSE` (the default) will not perform this
+#'
+#' @param suffixing *Specification for large-number suffixing*
+#'
+#'   `scalar<logical>|vector<character>` --- *default:* `FALSE`
+#'
+#'   The `suffixing` option allows us to scale and apply suffixes to larger
+#'   numbers (e.g., `1924000` can be transformed to `2M`). This option can
+#'   accept a logical value, where `FALSE` (the default) will not perform this
 #'   transformation and `TRUE` will apply thousands (`K`), millions (`M`),
 #'   billions (`B`), and trillions (`T`) suffixes after automatic value scaling.
-#'   We can also specify which symbols to use for each of the value ranges by
-#'   using a character vector of the preferred symbols to replace the defaults
-#'   (e.g., `c("k", "Ml", "Bn", "Tr")`).
+#'
+#'   We can alternatively provide a character vector that serves as a
+#'   specification for which symbols are to used for each of the value ranges.
+#'   These preferred symbols will replace the defaults (e.g.,
+#'   `c("k", "Ml", "Bn", "Tr")` replaces `"K"`, `"M"`, `"B"`, and `"T"`).
 #'
 #'   Including `NA` values in the vector will ensure that the particular range
-#'   will either not be included in the transformation (e.g, `c(NA, "M", "B",
-#'   "T")` won't modify numbers in the thousands range) or the range will
-#'   inherit a previous suffix (e.g., with `c("K", "M", NA, "T")`, all numbers
-#'   in the range of millions and billions will be in terms of millions).
+#'   will either not be included in the transformation (e.g.,
+#'   `c(NA, "M", "B", "T")` won't modify numbers at all in the thousands range)
+#'   or the range will inherit a previous suffix (e.g., with
+#'   `c("K", "M", NA, "T")`, all numbers in the range of millions and billions
+#'   will be in terms of millions).
 #'
 #'   Any use of `suffixing` (where it is not set expressly as `FALSE`) means
 #'   that any value provided to `scale_by` will be ignored.
 #'
+#'   If using `system = "ind"` then the default suffix set provided by
+#'   `suffixing = TRUE` will be the equivalent of `c(NA, "L", "Cr")`. This
+#'   doesn't apply suffixes to the thousands range, but does express values in
+#'   *lakhs* and *crores*.
+#'
 #' @return An object of class `gt_tbl`.
 #'
 #' @section Compatibility of formatting function with data values:
@@ -597,15 +707,31 @@ fmt_integer <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#' @param exp_style Style of formatting to use for the scientific notation
-#'   formatting. By default this is `"x10n"` but other options include using
-#'   a single letter (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to
-#'   signal a minimum digit width of one, or `"low-ten"` for using a stylized
-#'   `"10"` marker.
-#' @param force_sign_m,force_sign_n Should the plus sign be shown for positive
-#'   values of the mantissa (first component) or the exponent? This would
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied.
+#'
+#' @param exp_style *Style declaration for exponent formatting*
+#'
+#'   `scalar<character>` --- *default:* `"x10n"`
+#'
+#'   Style of formatting to use for the scientific notation formatting. By
+#'   default this is `"x10n"` but other options include using a single letter
+#'   (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to signal a
+#'   minimum digit width of one, or `"low-ten"` for using a stylized `"10"`
+#'   marker.
+#'
+#' @param force_sign_m,force_sign_n *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the plus sign be shown for positive values of the mantissa (first
+#'   component, `force_sign_m`) or the exponent (`force_sign_n`)? This would
 #'   effectively show a sign for all values except zero on either of those
 #'   numeric components of the notation. If so, use `TRUE` for either one of
 #'   these options. The default for both is `FALSE`, where only negative numbers
@@ -965,15 +1091,31 @@ fmt_scientific <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#' @param exp_style Style of formatting to use for the engineering notation
-#'   formatting. By default this is `"x10n"` but other options include using
-#'   a single letter (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to
-#'   signal a minimum digit width of one, or `"low-ten"` for using a stylized
-#'   `"10"` marker.
-#' @param force_sign_m,force_sign_n Should the plus sign be shown for positive
-#'   values of the mantissa (first component) or the exponent? This would
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied.
+#'
+#' @param exp_style *Style declaration for exponent formatting*
+#'
+#'   `scalar<character>` --- *default:* `"x10n"`
+#'
+#'   Style of formatting to use for the scientific notation formatting. By
+#'   default this is `"x10n"` but other options include using a single letter
+#'   (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to signal a
+#'   minimum digit width of one, or `"low-ten"` for using a stylized `"10"`
+#'   marker.
+#'
+#' @param force_sign_m,force_sign_n *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the plus sign be shown for positive values of the mantissa (first
+#'   component, `force_sign_m`) or the exponent (`force_sign_n`)? This would
 #'   effectively show a sign for all values except zero on either of those
 #'   numeric components of the notation. If so, use `TRUE` for either one of
 #'   these options. The default for both is `FALSE`, where only negative numbers
@@ -1472,14 +1614,29 @@ fmt_symbol <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param scale_values Should the values be scaled through multiplication by
-#'   100? By default this is `TRUE` since the expectation is that normally
-#'   values are proportions. Setting to `FALSE` signifies that the values are
+#'
+#' @param scale_values *Multiply input values by 100*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the values be scaled through multiplication by 100? By default this
+#'   scaling is performed since the expectation is that incoming values are
+#'   usually proportional. Setting to `FALSE` signifies that the values are
 #'   already scaled and require only the percent sign when formatted.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the percent sign. The default is to not introduce a space character.
-#' @param placement The placement of the percent sign. This can be either be
-#'   `right` (the default) or `left`.
+#'
+#' @param incl_space *Include a space between the value and the % sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option for whether to include a space between the value and the percent
+#'   sign. The default is to not introduce a space character.
+#'
+#' @param placement *Percent sign placement*
+#'
+#'   `scalar<character>` --- *default:* `"right"`
+#'
+#'   This option governs the placement of the percent sign. This can be either
+#'   be `right` (the default) or `left`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1697,22 +1854,42 @@ fmt_percent <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param to_units A keyword that signifies the desired output quantity. This
-#'   can be any from the following set: `"per-mille"`, `"per-myriad"`, `"pcm"`,
-#'   `"ppm"`, `"ppb"`, `"ppt"`, or `"ppq"`.
-#' @param symbol The symbol/units to use for the quantity. By default, this is
-#'   set to `"auto"` and **gt** will choose the appropriate symbol based on the
+#'
+#' @param to_units *Output Quantity*
+#'
+#'   `singl-kw:[per-mille|per-myriad|pcm|ppm|ppb|ppt|ppq]` --- *default:* `"per-mille"`
+#'
+#'   A keyword that signifies the desired output quantity. This can be any from
+#'   the following set: `"per-mille"`, `"per-myriad"`, `"pcm"`, `"ppm"`,
+#'   `"ppb"`, `"ppt"`, or `"ppq"`.
+#'
+#' @param symbol *Symbol or units to use in output display*
+#'
+#'   `scalar<character>` --- *default:* `"auto"`
+#'
+#'   The symbol/units to use for the quantity. By default, this is set to
+#'   `"auto"` and **gt** will choose the appropriate symbol based on the
 #'   `to_units` keyword and the output context. However, this can be changed by
 #'   supplying a string (e.g, using `symbol = "ppbV"` when `to_units = "ppb"`).
-#' @param scale_values Should the values be scaled through multiplication
-#'   according to the keyword set in `to_units`? By default this is `TRUE` since
-#'   the expectation is that normally values are proportions. Setting to `FALSE`
-#'   signifies that the values are already scaled and require only the
-#'   appropriate symbol/units when formatted.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the symbol/units. The default is `"auto"` which provides spacing
-#'   dependent on the mark itself. This can be directly controlled by using
-#'   either `TRUE` or `FALSE`.
+#'
+#' @param scale_values *Scale input values accordingly*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the values be scaled through multiplication according to the keyword
+#'   set in `to_units`? By default this is `TRUE` since the expectation is that
+#'   normally values are proportions. Setting to `FALSE` signifies that the
+#'   values are already scaled and require only the appropriate symbol/units
+#'   when formatted.
+#'
+#' @param incl_space *Include a space between the value and the symbol/units*
+#'
+#'   `scalar<character>|scalar<logical>` --- *default:* `"auto"`
+#'
+#'   An option for whether to include a space between the value and the
+#'   symbol/units. The default is `"auto"` which provides spacing dependent on
+#'   the mark itself. This can be directly controlled by using either `TRUE` or
+#'   `FALSE`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1960,21 +2137,36 @@ fmt_partsper <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param accuracy The type of fractions to generate. This can either be one of
-#'   the keywords `"low"`, `"med"`, or `"high"` (to generate fractions with
-#'   denominators of up to 1, 2, or 3 digits, respectively) or an integer value
-#'   greater than zero to obtain fractions with a fixed denominator (`2` yields
-#'   halves, `3` is for thirds, `4` is quarters, etc.). For the latter option,
-#'   using `simplify = TRUE` will simplify fractions where possible (e.g., `2/4`
-#'   will be simplified as `1/2`). By default, the `"low"` option is used.
-#' @param simplify If choosing to provide a numeric value for `accuracy`, the
-#'   option to simplify the fraction (where possible) can be taken with `TRUE`
-#'   (the default). With `FALSE`, denominators in fractions will be fixed to the
+#'
+#' @param accuracy *Accuracy of fractions*
+#'
+#'   `singl-kw:[low|med|high]|scalar<numeric|integer>(val>=1)` --- *default:* `"low"`
+#'
+#'   The type of fractions to generate. This can either be one of the keywords
+#'   `"low"`, `"med"`, or `"high"` (to generate fractions with denominators of
+#'   up to 1, 2, or 3 digits, respectively) or an integer value greater than
+#'   zero to obtain fractions with a fixed denominator (`2` yields halves, `3`
+#'   is for thirds, `4` is quarters, etc.). For the latter option, using
+#'   `simplify = TRUE` will simplify fractions where possible (e.g., `2/4` will
+#'   be simplified as `1/2`). By default, the `"low"` option is used.
+#'
+#' @param simplify *Simplify the fraction*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   If choosing to provide a numeric value for `accuracy`, the option to
+#'   simplify the fraction (where possible) can be taken with `TRUE` (the
+#'   default). With `FALSE`, denominators in fractions will be fixed to the
 #'   value provided in `accuracy`.
-#' @param layout For HTML output, the `"inline"` layout is the default. This
-#'   layout places the numerals of the fraction on the baseline and uses a
-#'   standard slash character. The `"diagonal"` layout will generate fractions
-#'   that are typeset with raised/lowered numerals and a virgule.
+#'
+#' @param layout *Layout of fractions in HTML output*
+#'
+#'   `singl-kw:[inline|diagonal]` --- *default:* `"inline"`
+#'
+#'   For HTML output, the `"inline"` layout is the default. This layout places
+#'   the numerals of the fraction on the baseline and uses a standard slash
+#'   character. The `"diagonal"` layout will generate fractions that are typeset
+#'   with raised/lowered numerals and a virgule.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2516,7 +2708,12 @@ round_gt <- function(x, digits = 0) {
 #' the possible inputs to the `currency` argument.
 #'
 #' @inheritParams fmt_number
-#' @param currency The currency to use for the numeric value. This input can be
+#'
+#' @param currency *Currency to use*
+#'
+#'   `scalar<character>|obj:<gt_currency>` --- *default:* `"USD"`
+#'
+#'   The currency to use for the numeric value. This input can be
 #'   supplied as a 3-letter currency code (e.g., `"USD"` for U.S. Dollars,
 #'   `"EUR"` for the Euro currency). Use [info_currencies()] to get an
 #'   information table with all of the valid currency codes and examples of
@@ -2533,14 +2730,28 @@ round_gt <- function(x, digits = 0) {
 #'   the letter "f" in all other output contexts). Please note that `decimals`
 #'   will default to `2` when using the [currency()] helper function.
 #'
-#'   If nothing is provided to `currency` then `"USD"` (U.S. dollars) will be
-#'   used.
-#' @param use_subunits An option for whether the subunits portion of a currency
-#'   value should be displayed. By default, this is `TRUE`.
-#' @param placement The placement of the currency symbol. This can be either be
-#'   `left` (the default) or `right`.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the currency symbol. The default is to not introduce a space character.
+#' @param use_subunits *Show or hide currency subunits*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option for whether the subunits portion of a currency value should be
+#'   displayed. For example, with an input value of `273.81`, the default
+#'   formatting will produce `"$273.81"`. Removing the subunits (with
+#'   `use_subunits = FALSE`) will give us `"$273"`.
+#'
+#' @param placement *Currency symbol placement*
+#'
+#'   `scalar<character>` --- *default:* `"left"`
+#'
+#'   The placement of the currency symbol. This can be either be `left` (as
+#'   in `"$450"`) or `right` (which yields `"450$"`).
+#'
+#' @param incl_space *Include a space between the value and the currency symbol*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option for whether to include a space between the value and the currency
+#'   symbol. The default is to not introduce a space character.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2756,8 +2967,13 @@ fmt_currency <- function(
 #' numerals, rounding values as necessary.
 #'
 #' @inheritParams fmt_number
-#' @param case Should Roman numerals should be rendered as uppercase (`"upper"`)
-#'   or lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
+#'
+#' @param case *Use uppercase or lowercase letters*
+#'
+#'   `singl-kw:[upper|lower]` --- *default:* `"upper"`
+#'
+#'   Should Roman numerals should be rendered as uppercase (`"upper"`) or
+#'   lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2925,14 +3141,23 @@ fmt_roman <- function(
 #' diacritical marks).
 #'
 #' @inheritParams fmt_number
-#' @param case Should resulting index characters be rendered as uppercase
-#'   (`"upper"`) or lowercase (`"lower"`) letters? By default, this is set to
-#'   `"upper"`.
-#' @param index_algo The indexing algorithm for handling the recycling of the
-#'   index character set. By default, the `"repeat"` option is used where
-#'   characters are doubled, tripled, and so on, when moving past the character
-#'   set limit. The alternative is the `"excel"` option, where Excel-based
-#'   column naming is adapted and used here (e.g., `[..., Y, Z, AA, AB, ...]`).
+#'
+#' @param case *Use uppercase or lowercase letters*
+#'
+#'   `singl-kw:[upper|lower]` --- *default:* `"upper"`
+#'
+#'   Should the resulting index characters be rendered as uppercase (`"upper"`)
+#'   or lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
+#'
+#' @param index_algo *Indexing algorithm*
+#'
+#'   `singl-kw:[repeat|excel]` --- *default:* `"repeat"`
+#'
+#'   The indexing algorithm handles the recycling of the index character set. By
+#'   default, the `"repeat"` option is used where characters are doubled,
+#'   tripled, and so on, when moving past the character set limit. The
+#'   alternative is the `"excel"` option, where Excel-based column naming is
+#'   adapted and used here (e.g., `[..., Y, Z, AA, AB, ...]`).
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -3466,15 +3691,39 @@ fmt_spelled_num <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams fmt_number
-#' @param standard The way to express large byte sizes.
-#' @param decimals An option to specify the exact number of decimal places to
-#'   use. The default number of decimal places is `1`.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the units. The default of `TRUE` uses a space character for separation.
-#' @param force_sign Should the positive sign be shown for positive numbers
-#'   (effectively showing a sign for all numbers except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative numbers will
-#'   display a minus sign.
+#'
+#' @param standard *Standard used to express byte sizes*
+#'
+#'   `singl-kw:[decimal|binary]` --- *default:* `"decimal"`
+#'
+#'   The form of expressing large byte sizes is divided between: (1) decimal
+#'   units (powers of 1000; e.g., `"kB"` and `"MB"`), and (2) binary units
+#'   (powers of 1024; e.g., `"KiB"` and `"MiB"`).
+#'
+#' @param decimals *Number of decimal places*
+#'
+#'   `scalar<numeric|integer>(val>=0)` --- *default:* `1`
+#'
+#'   This corresponds to the exact number of decimal places to use. A value
+#'   such as `2.34` can, for example, be formatted with `0` decimal places and
+#'   it would result in `"2"`. With `4` decimal places, the formatted value
+#'   becomes `"2.3400"`. The trailing zeros can be removed with
+#'   `drop_trailing_zeros = TRUE`.
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive numbers (effectively showing
+#'   a sign for all numbers except zero)? If so, use `TRUE` for this option. The
+#'   default is `FALSE`, where only negative numbers will display a minus sign.
+#'
+#' @param incl_space *Include a space between the value and the units*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option for whether to include a space between the value and the units.
+#'   The default is to use a space character for separation.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -3720,9 +3969,14 @@ fmt_bytes <- function(
 #' `YYYY-MM-DD`).
 #'
 #' @inheritParams fmt_number
-#' @param date_style The date style to use. By default this is `"iso"` which
-#'   corresponds to ISO 8601 date formatting. The other date styles can be
-#'   viewed using [info_date_style()].
+#'
+#' @param date_style *Predefined style for dates*
+#'
+#'   `scalar<character>|scalar<numeric|integer>(1<=val<=41)` --- *default:* `"iso"`
+#'
+#'   The date style to use. By default this is the short name `"iso"` which
+#'   corresponds to ISO 8601 date formatting. There are 41 date styles in total
+#'   and their short names can be viewed using [info_date_style()].
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -4009,9 +4263,15 @@ fmt_date <- function(
 #' always results in the formatting of `00:00:00`).
 #'
 #' @inheritParams fmt_number
-#' @param time_style The time style to use. By default this is `"iso"` which
-#'   corresponds to how times are formatted within ISO 8601 datetime values. The
-#'   other time styles can be viewed using [info_time_style()].
+#'
+#' @param time_style *Predefined style for times*
+#'
+#'   `scalar<character>|scalar<numeric|integer>(1<=val<=25)` --- *default:* `"iso"`
+#'
+#'   The time style to use. By default this is the short name `"iso"` which
+#'   corresponds to how times are formatted within ISO 8601 datetime values.
+#'   There are 25 time styles in total and their short names can be viewed using
+#'   [info_time_style()].
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -4291,16 +4551,33 @@ fmt_time <- function(
 #' in the ISO 8601 form of `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`).
 #'
 #' @inheritParams fmt_number
+#'
 #' @inheritParams fmt_date
+#'
 #' @inheritParams fmt_time
-#' @param sep The separator string to use between the date and time components.
-#'   By default, this is a single space character (`" "`). Only used when not
+#'
+#' @param sep *Separator between date and time components*
+#'
+#'   `scalar<character>` --- *default:* `" "`
+#'
+#'   The separator string to use between the date and time components. By
+#'   default, this is a single space character (`" "`). Only used when not
 #'   specifying a `format` code.
-#' @param format An optional formatting string used for generating custom
-#'   dates/times. If used then the arguments governing preset styles
-#'   (`date_style` and `time_style`) will be ignored in favor of formatting via
-#'   the `format` string.
-#' @param tz The time zone for printing dates/times (i.e., the output). The
+#'
+#' @param format *Date/time formatting string*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional formatting string used for generating custom dates/times. If
+#'   used then the arguments governing preset styles (`date_style` and
+#'   `time_style`) will be ignored in favor of formatting via the `format`
+#'   string.
+#'
+#' @param tz *Time zone*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The time zone for printing dates/times (i.e., the output). The
 #'   default of `NULL` will preserve the time zone of the input data in the
 #'   output. If providing a time zone, it must be one that is recognized by the
 #'   user's operating system (a vector of all valid `tz` values can be produced
@@ -5282,45 +5559,74 @@ fmt_datetime <- function(
 #' which is `c("days", "hours", "minutes", "seconds")`
 #'
 #' @inheritParams fmt_number
-#' @param input_units If one or more selected columns contains numeric values, a
-#'   keyword must be provided for `input_units` for **gt** to determine how
-#'   those values are to be interpreted in terms of duration. The accepted units
-#'   are: `"seconds"`, `"minutes"`, `"hours"`, `"days"`, and `"weeks"`.
-#' @param output_units Controls the output time units. The default, `NULL`,
-#'   means that **gt** will automatically choose time units based on the input
-#'   duration value. To control which time units are to be considered for output
-#'   (before trimming with `trim_zero_units`) we can specify a vector of one or
-#'   more of the following keywords: `"weeks"`, `"days"`, `"hours"`,
-#'   `"minutes"`, or `"seconds"`.
-#' @param duration_style A choice of four formatting styles for the output
-#'   duration values. With `"narrow"` (the default style), duration values will
-#'   be formatted with single letter time-part units (e.g., 1.35 days will be
-#'   styled as `"1d 8h 24m`). With `"wide"`, this example value will be expanded
-#'   to `"1 day 8 hours 24 minutes"` after formatting. The `"colon-sep"` style
-#'   will put days, hours, minutes, and seconds in the `"([D]/)[HH]:[MM]:[SS]"`
+#'
+#' @param input_units *Declaration of duration units for numerical values*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   If one or more selected columns contains numeric values (not `difftime`
+#'   values, which contain the duration units), a keyword must be provided for
+#'   `input_units` for **gt** to determine how those values are to be
+#'   interpreted in terms of duration. The accepted units are: `"seconds"`,
+#'   `"minutes"`, `"hours"`, `"days"`, and `"weeks"`.
+#'
+#' @param output_units *Choice of output units*
+#'
+#'   `mult-kw:[weeks|days|hours|minutes|seconds]` --- *default:* `NULL` (`optional`)
+#'
+#'   Controls the output time units. The default, `NULL`, means that **gt** will
+#'   automatically choose time units based on the input duration value. To
+#'   control which time units are to be considered for output (before trimming
+#'   with `trim_zero_units`) we can specify a vector of one or more of the
+#'   following keywords: `"weeks"`, `"days"`, `"hours"`, `"minutes"`, or
+#'   `"seconds"`.
+#'
+#' @param duration_style *Style for representing duration values*
+#'
+#'   `singl-kw:[narrow|wide|colon-sep|iso]` --- *default:* `"narrow"`
+#'
+#'   A choice of four formatting styles for the output duration values. With
+#'   `"narrow"` (the default style), duration values will be formatted with
+#'   single letter time-part units (e.g., 1.35 days will be styled as
+#'   `"1d 8h 24m"`). With `"wide"`, this example value will be expanded to
+#'   `"1 day 8 hours 24 minutes"` after formatting. The `"colon-sep"` style will
+#'   put days, hours, minutes, and seconds in the `"([D]/)[HH]:[MM]:[SS]"`
 #'   format. The `"iso"` style will produce a value that conforms to the ISO
 #'   8601 rules for duration values (e.g., 1.35 days will become `"P1DT8H24M"`).
-#' @param trim_zero_units Provides methods to remove output time units that have
-#'   zero values. By default this is `TRUE` and duration values that might
-#'   otherwise be formatted as `"0w 1d 0h 4m 19s"` with
-#'   `trim_zero_units = FALSE` are instead displayed as `"1d 4m 19s"`. Aside
-#'   from using `TRUE`/`FALSE` we could provide a vector of keywords for more
-#'   precise control. These keywords are: (1) `"leading"`, to omit all leading
-#'   zero-value time units (e.g., `"0w 1d"` -> `"1d"`), (2) `"trailing"`, to
-#'   omit all trailing zero-value time units (e.g., `"3d 5h 0s"` -> `"3d 5h"`),
-#'   and `"internal"`, which removes all internal zero-value time units (e.g.,
-#'   `"5d 0h 33m"` -> `"5d 33m"`).
-#' @param max_output_units If `output_units` is `NULL`, where the output time
-#'   units are unspecified and left to **gt** to handle, a numeric value
-#'   provided for `max_output_units` will be taken as the maximum number of time
-#'   units to display in all output time duration values. By default, this is
-#'   `NULL` and all possible time units will be displayed. This option has no
-#'   effect when `duration_style = "colon-sep"` (only `output_units` can be used
-#'   to customize that type of duration output).
-#' @param force_sign Should the positive sign be shown for positive values
-#'   (effectively showing a sign for all values except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative value will
-#'   display a minus sign.
+#'
+#' @param trim_zero_units *Trimming of zero values*
+#'
+#'   `scalar<logical>|mult-kw:[leading|trailing|internal]` --- *default:* `TRUE`
+#'
+#'   Provides methods to remove output time units that have zero values. By
+#'   default this is `TRUE` and duration values that might otherwise be
+#'   formatted as `"0w 1d 0h 4m 19s"` with `trim_zero_units = FALSE` are instead
+#'   displayed as `"1d 4m 19s"`. Aside from using `TRUE`/`FALSE` we could
+#'   provide a vector of keywords for more precise control. These keywords are:
+#'   (1) `"leading"`, to omit all leading zero-value time units (e.g., `"0w 1d"`
+#'   -> `"1d"`), (2) `"trailing"`, to omit all trailing zero-value time units
+#'   (e.g., `"3d 5h 0s"` -> `"3d 5h"`), and `"internal"`, which removes all
+#'   internal zero-value time units (e.g., `"5d 0h 33m"` -> `"5d 33m"`).
+#'
+#' @param max_output_units *Maximum number of time units to display*
+#'
+#'   `scalar<numeric|integer>(val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   If `output_units` is `NULL`, where the output time units are unspecified
+#'   and left to **gt** to handle, a numeric value provided for
+#'   `max_output_units` will be taken as the maximum number of time units to
+#'   display in all output time duration values. By default, this is `NULL` and
+#'   all possible time units will be displayed. This option has no effect when
+#'   `duration_style = "colon-sep"` (only `output_units` can be used to
+#'   customize that type of duration output).
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive values (effectively showing
+#'   a sign for all values except zero)? If so, use `TRUE` for this option. By
+#'   default only negative values will display a minus sign.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -6093,13 +6399,23 @@ extract_duration_pattern <- function(
 #' argument, and, the separator can be modified with the `sep` argument.
 #'
 #' @inheritParams fmt_number
-#' @param sep The separator text that indicates the values are ranged. The
-#'   default value of `"--"` indicates that an en dash will be used for the
-#'   range separator. Using `"---"` will be taken to mean that an em dash should
-#'   be used. Should you want these special symbols to be taken literally, they
-#'   can be supplied within the base [I()] function.
-#' @param fmt Formatting expressions in formula form. The RHS of `~` should
-#'   contain a formatting call (e.g.,
+#'
+#' @param sep *Separator between values*
+#'
+#'   `scalar<character>` --- *default:* `"--"`
+#'
+#'   The separator text that indicates the values are ranged. The default value
+#'   of `"--"` indicates that an en dash will be used for the range separator.
+#'   Using `"---"` will be taken to mean that an em dash should be used. Should
+#'   you want these special symbols to be taken literally, they can be supplied
+#'   within the base [I()] function.
+#'
+#' @param fmt *Formatting expressions*
+#'
+#'   `<single expression>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional formatting expression in formula form. If used, the RHS of `~`
+#'   should contain a formatting call (e.g.,
 #'   `~ fmt_number(., decimals = 3, use_seps = FALSE`).
 #'
 #' @return An object of class `gt_tbl`.
@@ -6371,25 +6687,49 @@ format_bins_by_context <- function(x, sep, fmt, context) {
 #' text.
 #'
 #' @inheritParams fmt_number
-#' @param label The visible 'label' to use for the link. If `NULL` (the default)
+#'
+#' @param label *Link label*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The visible 'label' to use for the link. If `NULL` (the default)
 #'   the URL will serve as the label. There are two non-`NULL` options: (1) a
 #'   static text can be used for the label by providing a string, and (2) a
 #'   function can be provided to fashion a label from every URL.
-#' @param as_button An option to style the link as a button. By default, this is
+#'
+#' @param as_button *Style link as a button*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option to style the link as a button. By default, this is
 #'   `FALSE`. If this option is chosen then the `button_fill` argument becomes
 #'   usable.
-#' @param color The color used for the resulting link and its underline. This is
+#'
+#' @param color *Link color*
+#'
+#'   `scalar<character>` --- *default:* `"auto"`
+#'
+#'   The color used for the resulting link and its underline. This is
 #'   `"auto"` by default; this allows **gt** to choose an appropriate color
-#'   based on various factors (e.g., background `button_fill` when `as_button`
-#'   is `TRUE`).
-#' @param show_underline Should the link be decorated with an underline? By
+#'   based on various factors (such as the background `button_fill` when
+#'   `as_button` is `TRUE`).
+#'
+#' @param show_underline *Show the link underline*
+#'
+#'   `scalar<character>|scalar<logical>` --- *default:* `"auto"`
+#'
+#'   Should the link be decorated with an underline? By
 #'   default this is `"auto"` which means that **gt** will choose `TRUE` when
 #'   `as_button = FALSE` and `FALSE` in the other case. The link underline will
 #'   be the same color as that set in the `color` option.
-#' @param button_fill,button_width,button_outline Options for styling a
-#'   link-as-button (and only applies if `as_button = TRUE`). All of these
-#'   options are by default set to `"auto"`, allowing **gt** to choose
-#'   appropriate fill, width, and outline values.
+#'
+#' @param button_fill,button_width,button_outline *Button options*
+#'
+#'   `scalar<character>` --- *default:* `"auto"`
+#'
+#'   Options for styling a link-as-button (and only applies if
+#'   `as_button = TRUE`). All of these options are by default set to `"auto"`,
+#'   allowing **gt** to choose appropriate fill, width, and outline values.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -6864,16 +7204,42 @@ fmt_url <- function(
 #' separator to be applied between images.
 #'
 #' @inheritParams fmt_number
-#' @param height The absolute height of the image in the table cell. By default,
-#'   this is set to `"1em"`.
-#' @param sep In the output of images within a body cell, `sep` provides the
-#'   separator between each image.
-#' @param path An optional path to local image files (this is combined with all
+#'
+#' @param height *Height of image*
+#'
+#'   `scalar<character>` --- *default:* `"1em"`
+#'
+#'   The absolute height of the image in the table cell. By default, this is set
+#'   to `"1em"`.
+#'
+#' @param sep *Separator between images*
+#'
+#'   `scalar<character>` --- *default:* `" "`
+#'
+#'   In the output of images within a body cell, `sep` provides the separator
+#'   between each image.
+#'
+#' @param path *Path to image files*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional path to local image files (this is combined with all
 #'   filenames).
-#' @param file_pattern The pattern to use for mapping input values in the body
-#'   cells to the names of the graphics files.
-#' @param encode The option to always use Base64 encoding for image paths that
-#'   are determined to be local. By default, this is `TRUE`.
+#'
+#' @param file_pattern *File pattern specification*
+#'
+#'   `scalar<character>` --- *default:* `"{x}"`
+#'
+#'   The pattern to use for mapping input values in the body cells to the names
+#'   of the graphics files. The string supplied should use `"{x}"` in the
+#'   pattern to map filename fragments to input strings.
+#'
+#' @param encode *Use Base64 encoding*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   The option to always use Base64 encoding for image paths that are
+#'   determined to be local. By default, this is `TRUE`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -7141,13 +7507,28 @@ fmt_image <- function(
 #' icons.
 #'
 #' @inheritParams fmt_number
-#' @param height The absolute height of the flag icon in the table cell. By
-#'   default, this is set to `"1em"`.
-#' @param sep In the output of flag icons within a body cell, `sep` provides the
+#'
+#' @param height *Height of flag*
+#'
+#'   `scalar<character>` --- *default:* `"1em"`
+#'
+#'   The absolute height of the flag icon in the table cell. By default, this is
+#'   set to `"1em"`.
+#'
+#' @param sep *Separator between flags*
+#'
+#'   `scalar<character>` --- *default:* `" "`
+#'
+#'   In the output of flag icons within a body cell, `sep` provides the
 #'   separator between each icon. By default, this is a single space character
 #'   (`" "`).
-#' @param use_title An option to display a tooltip for the country name when
-#'   hovering over the flag icon. By default this is `TRUE`.
+#'
+#' @param use_title *Display country name on hover*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to display a tooltip for the country name (in English) when
+#'   hovering over the flag icon.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -7450,10 +7831,15 @@ fmt_flag <- function(
 #' appropriate output type during render when using `fmt_markdown()`.
 #'
 #' @inheritParams fmt_number
-#' @param md_engine The engine preference for Markdown rendering. By default,
-#'   this is set to `"markdown"` where **gt** will use the **markdown** package
-#'   for Markdown conversion to HTML and LaTeX. The other option is
-#'   `"commonmark"` and with that the **commonmark** package will be used.
+#'
+#' @param md_engine *Choice of Markdown engine*
+#'
+#'   `singl-kw:[markdown|commonmark]` --- *default:* `"markdown"`
+#'
+#'   The engine preference for Markdown rendering. By default, this is set to
+#'   `"markdown"` where **gt** will use the **markdown** package for Markdown
+#'   conversion to HTML and LaTeX. The other option is `"commonmark"` and with
+#'   that the **commonmark** package will be used.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -7620,11 +8006,16 @@ fmt_markdown <- function(
 #' the input data other than to decorate it within a pattern.
 #'
 #' @inheritParams fmt_number
-#' @param escape An option to escape text according to the final output format
-#'   of the table. For example, if a LaTeX table is to be generated then LaTeX
-#'   escaping would be performed during rendering. By default this is set to
-#'   `TRUE` and setting to `FALSE` would be useful in the case where text is
-#'   crafted for a specific output format in mind.
+#'
+#' @param escape *Text escaping*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to escape text according to the final output format of the table.
+#'   For example, if a LaTeX table is to be generated then LaTeX escaping would
+#'   be performed during rendering. By default this is set to `TRUE` but setting
+#'   as `FALSE` would be useful in the case where text is crafted for a specific
+#'   output format in mind.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -7805,12 +8196,23 @@ fmt_passthrough <- function(
 #' formatting will be applied.
 #'
 #' @inheritParams fmt_number
-#' @param scope The scope of automatic formatting. By default this includes
-#'   `"numbers"`-type values and `"currency"`-type values though the scope can
-#'   be reduced to a single type of value to format.
-#' @param lg_num_pref The preference toward either scientific notation for very
-#'   small and very large values (`"sci"`, the default option), or, suffixed
-#'   numbers (`"suf"`, for large values only).
+#'
+#' @param scope *Scope of automatic formatting*
+#'
+#'   `mult-kw:[numbers|currency]` --- *default:* `c("numbers", "currency")`
+#'
+#'   By default, the function will format both `"numbers"`-type values and
+#'   `"currency"`-type values though the scope can be reduced to a single type
+#'   of value to format.
+#'
+#' @param lg_num_pref *Large-number preference*
+#'
+#'   `singl-kw:[sci|suf]` --- *default:* `"sci"`
+#'
+#'   When large numbers are present, there can be a fixed preference toward how
+#'   they are formatted. Choices are scientific notation for very small and very
+#'   large values (`"sci"`), or, the use of suffixed numbers (`"suf"`, for large
+#'   values only).
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -8129,9 +8531,19 @@ fmt_auto <- function(
 #' fallback if all contexts aren't provided.
 #'
 #' @inheritParams fmt_number
-#' @param fns Either a single formatting function or a named list of functions.
-#' @param compat An optional vector that provides the compatible classes for the
-#' formatter. By default this is `NULL`.
+#'
+#' @param compat *Formatting compatibility*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional vector that provides the compatible classes for the formatting.
+#'   By default this is `NULL`.
+#'
+#' @param fns *Formatting functions*
+#'
+#'   `function|list of functions` --- **required**
+#'
+#'   Either a single formatting function or a named list of functions.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/format_vec.R b/R/format_vec.R
index 501ec8eaeb..9e338c29e0 100644
--- a/R/format_vec.R
+++ b/R/format_vec.R
@@ -42,72 +42,159 @@
 #' - locale-based formatting: providing a locale ID will result in number
 #' formatting specific to the chosen locale
 #'
-#' @param x A numeric vector.
-#' @param decimals An option to specify the exact number of decimal places to
-#'   use. The default number of decimal places is `2`.
-#' @param n_sigfig A option to format numbers to *n* significant figures. By
-#'   default, this is `NULL` and thus number values will be formatted according
-#'   to the number of decimal places set via `decimals`. If opting to format
-#'   according to the rules of significant figures, `n_sigfig` must be a number
-#'   greater than or equal to `1`. Any values passed to the `decimals` and
-#'   `drop_trailing_zeros` arguments will be ignored.
-#' @param drop_trailing_zeros A logical value that allows for removal of
-#'   trailing zeros (those redundant zeros after the decimal mark).
-#' @param drop_trailing_dec_mark A logical value that determines whether decimal
-#'   marks should always appear even if there are no decimal digits to display
-#'   after formatting (e.g, `23` becomes `23.`). The default for this is `TRUE`,
-#'   which means that trailing decimal marks are not shown.
-#' @param use_seps An option to use digit group separators. The type of digit
-#'   group separator is set by `sep_mark` and overridden if a locale ID is
-#'   provided to `locale`. This setting is `TRUE` by default.
-#' @param accounting An option to use accounting style for values. With `FALSE`
-#'   (the default), negative values will be shown with a minus sign. Using
-#'   `accounting = TRUE` will put negative values in parentheses.
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#'   This value will be ignored if using any of the `suffixing` options (i.e.,
-#'   where `suffixing` is not set to `FALSE`).
-#' @param suffixing An option to scale and apply suffixes to larger numbers
-#'   (e.g., `1924000` can be transformed to `1.92M`). This option can accept a
-#'   logical value, where `FALSE` (the default) will not perform this
-#'   transformation and `TRUE` will apply thousands (`K`), millions (`M`),
-#'   billions (`B`), and trillions (`T`) suffixes after automatic value scaling.
-#'   We can also specify which symbols to use for each of the value ranges by
-#'   using a character vector of the preferred symbols to replace the defaults
-#'   (e.g., `c("k", "Ml", "Bn", "Tr")`).
+#' @param x *The input vector*
+#'
+#'   `vector(numeric|integer)` --- **required**
+#'
+#'   This is the input vector that will undergo transformation to a character
+#'   vector of the same length. Values within the vector will be formatted.
+#'
+#' @param decimals *Number of decimal places*
+#'
+#'   `scalar<numeric|integer>(val>=0)` --- *default:* `2`
+#'
+#'   This corresponds to the exact number of decimal places to use. A value
+#'   such as `2.34` can, for example, be formatted with `0` decimal places and
+#'   it would result in `"2"`. With `4` decimal places, the formatted value
+#'   becomes `"2.3400"`. The trailing zeros can be removed with
+#'   `drop_trailing_zeros = TRUE`. If you always need `decimals = 0`, the
+#'   [fmt_integer()] function should be considered.
+#'
+#' @param n_sigfig *Number of significant figures*
+#'
+#'   `scalar<numeric|integer>(val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   A option to format numbers to *n* significant figures. By default, this is
+#'   `NULL` and thus number values will be formatted according to the number of
+#'   decimal places set via `decimals`. If opting to format according to the
+#'   rules of significant figures, `n_sigfig` must be a number greater than or
+#'   equal to `1`. Any values passed to the `decimals` and `drop_trailing_zeros`
+#'   arguments will be ignored.
+#'
+#' @param drop_trailing_zeros *Drop any trailing zeros*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   A logical value that allows for removal of trailing zeros (those redundant
+#'   zeros after the decimal mark).
+#'
+#' @param drop_trailing_dec_mark *Drop the trailing decimal mark*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   A logical value that determines whether decimal marks should always appear
+#'   even if there are no decimal digits to display after formatting (e.g., `23`
+#'   becomes `23.` if `FALSE`). By default trailing decimal marks are not shown.
+#'
+#' @param use_seps *Use digit group separators*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to use digit group separators. The type of digit group separator
+#'   is set by `sep_mark` and overridden if a locale ID is provided to `locale`.
+#'   This setting is `TRUE` by default.
+#'
+#' @param accounting *Use accounting style*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option to use accounting style for values. Normally, negative values
+#'   will be shown with a minus sign but using accounting style will instead put
+#'   any negative values in parentheses.
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied. This value will be
+#'   ignored if using any of the `suffixing` options (i.e., where `suffixing` is
+#'   not set to `FALSE`).
+#'
+#' @param suffixing *Specification for large-number suffixing*
+#'
+#'   `scalar<logical>|vector<character>` --- *default:* `FALSE`
+#'
+#'   The `suffixing` option allows us to scale and apply suffixes to larger
+#'   numbers (e.g., `1924000` can be transformed to `1.92M`). This option can
+#'   accept a logical value, where `FALSE` (the default) will not perform this
+#'   transformation and `TRUE` will apply thousands (`"K"`), millions (`"M"`),
+#'   billions (`"B"`), and trillions (`"T"`) suffixes after automatic value
+#'   scaling.
+#'
+#'   We can alternatively provide a character vector that serves as a
+#'   specification for which symbols are to used for each of the value ranges.
+#'   These preferred symbols will replace the defaults (e.g.,
+#'   `c("k", "Ml", "Bn", "Tr")` replaces `"K"`, `"M"`, `"B"`, and `"T"`).
 #'
 #'   Including `NA` values in the vector will ensure that the particular range
-#'   will either not be included in the transformation (e.g, `c(NA, "M", "B",
-#'   "T")` won't modify numbers in the thousands range) or the range will
-#'   inherit a previous suffix (e.g., with `c("K", "M", NA, "T")`, all numbers
-#'   in the range of millions and billions will be in terms of millions).
+#'   will either not be included in the transformation (e.g.,
+#'   `c(NA, "M", "B", "T")` won't modify numbers at all in the thousands range)
+#'   or the range will inherit a previous suffix (e.g., with
+#'   `c("K", "M", NA, "T")`, all numbers in the range of millions and billions
+#'   will be in terms of millions).
 #'
 #'   Any use of `suffixing` (where it is not set expressly as `FALSE`) means
 #'   that any value provided to `scale_by` will be ignored.
-#' @param pattern A formatting pattern that allows for decoration of the
-#'   formatted value. The value itself is represented by `{x}` and all other
-#'   characters are taken to be string literals.
-#' @param sep_mark The mark to use as a separator between groups of digits
-#'   (e.g., using `sep_mark = ","` with `1000` would result in a formatted value
-#'   of `1,000`).
-#' @param dec_mark The character to use as a decimal mark (e.g., using
-#'   `dec_mark = ","` with `0.152` would result in a formatted value of
-#'   `0,152`).
-#' @param force_sign Should the positive sign be shown for positive values
-#'   (effectively showing a sign for all values except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative numbers will
-#'   display a minus sign. This option is disregarded when using accounting
-#'   notation with `accounting = TRUE`.
-#' @param locale An optional locale identifier that can be used for formatting
-#'   the value according the locale's rules. Examples include `"en"` for English
-#'   (United States) and `"fr"` for French (France). The use of a locale ID will
-#'   override any locale-specific values provided. We can use the
-#'   [info_locales()] function as a useful reference for all of the locales that
-#'   are supported.
-#' @param output The output style of the resulting character vector. This can
-#'   either be `"auto"` (the default), `"plain"`, `"html"`, `"latex"`, `"rtf"`,
-#'   or `"word"`. In **knitr** rendering (i.e., Quarto or R Markdown), the
-#'   `"auto"` option will choose the correct `output` value
+#'
+#' @param pattern *Specification of the formatting pattern*
+#'
+#'   `scalar<character>` --- *default:* `"{x}"`
+#'
+#'   A formatting pattern that allows for decoration of the formatted value. The
+#'   formatted value is represented by the `{x}` (which can be used multiple
+#'   times, if needed) and all other characters will be interpreted as string
+#'   literals.
+#'
+#' @param sep_mark *Separator mark for digit grouping*
+#'
+#'   `scalar<character>` --- *default:* `","`
+#'
+#'   The string to use as a separator between groups of digits. For example,
+#'   using `sep_mark = ","` with a value of `1000` would result in a formatted
+#'   value of `"1,000"`. This argument is ignored if a `locale` is supplied
+#'   (i.e., is not `NULL`).
+#'
+#' @param dec_mark *Decimal mark*
+#'
+#'   `scalar<character>` --- *default:* `"."`
+#'
+#'   The string to be used as the decimal mark. For example, using
+#'   `dec_mark = ","` with the value `0.152` would result in a formatted value
+#'   of `"0,152"`). This argument is ignored if a `locale` is supplied (i.e., is
+#'   not `NULL`).
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive values (effectively showing
+#'   a sign for all values except zero)? If so, use `TRUE` for this option. The
+#'   default is `FALSE`, where only negative numbers will display a minus sign.
+#'   This option is disregarded when using accounting notation with
+#'   `accounting = TRUE`.
+#'
+#' @param locale *Locale identifier*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional locale identifier that can be used for formatting values
+#'   according the locale's rules. Examples include `"en"` for English (United
+#'   States) and `"fr"` for French (France). We can use the [info_locales()]
+#'   function as a useful reference for all of the locales that are supported. A
+#'   locale ID can be also set in the initial [gt()] function call (where it
+#'   would be used automatically by any function with a `locale` argument) but a
+#'   `locale` value provided here will override that global locale.
+#'
+#' @param output *Output format*
+#'
+#'   `singl-kw:[auto|plain|html|latex|rtf|word]` --- *default:* `"auto"`
+#'
+#'   The output style of the resulting character vector. This can either be
+#'   `"auto"` (the default), `"plain"`, `"html"`, `"latex"`, `"rtf"`, or
+#'   `"word"`. In **knitr** rendering (i.e., Quarto or R Markdown), the `"auto"`
+#'   option will choose the correct `output` value
 #'
 #' @return A character vector.
 #'
@@ -271,20 +358,28 @@ vec_fmt_number <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param suffixing An option to scale and apply suffixes to larger numbers
-#'   (e.g., `1924000` can be transformed to `2M`). This option can accept a
-#'   logical value, where `FALSE` (the default) will not perform this
+#'
+#' @param suffixing *Specification for large-number suffixing*
+#'
+#'   `scalar<logical>|vector<character>` --- *default:* `FALSE`
+#'
+#'   The `suffixing` option allows us to scale and apply suffixes to larger
+#'   numbers (e.g., `1924000` can be transformed to `2M`). This option can
+#'   accept a logical value, where `FALSE` (the default) will not perform this
 #'   transformation and `TRUE` will apply thousands (`K`), millions (`M`),
 #'   billions (`B`), and trillions (`T`) suffixes after automatic value scaling.
-#'   We can also specify which symbols to use for each of the value ranges by
-#'   using a character vector of the preferred symbols to replace the defaults
-#'   (e.g., `c("k", "Ml", "Bn", "Tr")`).
+#'
+#'   We can alternatively provide a character vector that serves as a
+#'   specification for which symbols are to used for each of the value ranges.
+#'   These preferred symbols will replace the defaults (e.g.,
+#'   `c("k", "Ml", "Bn", "Tr")` replaces `"K"`, `"M"`, `"B"`, and `"T"`).
 #'
 #'   Including `NA` values in the vector will ensure that the particular range
-#'   will either not be included in the transformation (e.g, `c(NA, "M", "B",
-#'   "T")` won't modify numbers in the thousands range) or the range will
-#'   inherit a previous suffix (e.g., with `c("K", "M", NA, "T")`, all numbers
-#'   in the range of millions and billions will be in terms of millions).
+#'   will either not be included in the transformation (e.g.,
+#'   `c(NA, "M", "B", "T")` won't modify numbers at all in the thousands range)
+#'   or the range will inherit a previous suffix (e.g., with
+#'   `c("K", "M", NA, "T")`, all numbers in the range of millions and billions
+#'   will be in terms of millions).
 #'
 #'   Any use of `suffixing` (where it is not set expressly as `FALSE`) means
 #'   that any value provided to `scale_by` will be ignored.
@@ -418,15 +513,31 @@ vec_fmt_integer <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#' @param exp_style Style of formatting to use for the scientific notation
-#'   formatting. By default this is `"x10n"` but other options include using
-#'   a single letter (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to
-#'   signal a minimum digit width of one, or `"low-ten"` for using a stylized
-#'   `"10"` marker.
-#' @param force_sign_m,force_sign_n Should the plus sign be shown for positive
-#'   values of the mantissa (first component) or the exponent? This would
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied.
+#'
+#' @param exp_style *Style declaration for exponent formatting*
+#'
+#'   `scalar<character>` --- *default:* `"x10n"`
+#'
+#'   Style of formatting to use for the scientific notation formatting. By
+#'   default this is `"x10n"` but other options include using a single letter
+#'   (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to signal a
+#'   minimum digit width of one, or `"low-ten"` for using a stylized `"10"`
+#'   marker.
+#'
+#' @param force_sign_m,force_sign_n *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the plus sign be shown for positive values of the mantissa (first
+#'   component, `force_sign_m`) or the exponent (`force_sign_n`)? This would
 #'   effectively show a sign for all values except zero on either of those
 #'   numeric components of the notation. If so, use `TRUE` for either one of
 #'   these options. The default for both is `FALSE`, where only negative numbers
@@ -580,15 +691,31 @@ vec_fmt_scientific <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param scale_by A value to scale the input. The default is `1.0`. All numeric
-#'   values will be multiplied by this value first before undergoing formatting.
-#' @param exp_style Style of formatting to use for the engineering notation
-#'   formatting. By default this is `"x10n"` but other options include using
-#'   a single letter (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to
-#'   signal a minimum digit width of one, or `"low-ten"` for using a stylized
-#'   `"10"` marker.
-#' @param force_sign_m,force_sign_n Should the plus sign be shown for positive
-#'   values of the mantissa (first component) or the exponent? This would
+#'
+#' @param scale_by *Scale values by a fixed multiplier*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   All numeric values will be multiplied by the `scale_by` value before
+#'   undergoing formatting. Since the `default` value is `1`, no values will be
+#'   changed unless a different multiplier value is supplied.
+#'
+#' @param exp_style *Style declaration for exponent formatting*
+#'
+#'   `scalar<character>` --- *default:* `"x10n"`
+#'
+#'   Style of formatting to use for the scientific notation formatting. By
+#'   default this is `"x10n"` but other options include using a single letter
+#'   (e.g., `"e"`, `"E"`, etc.), a letter followed by a `"1"` to signal a
+#'   minimum digit width of one, or `"low-ten"` for using a stylized `"10"`
+#'   marker.
+#'
+#' @param force_sign_m,force_sign_n *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the plus sign be shown for positive values of the mantissa (first
+#'   component, `force_sign_m`) or the exponent (`force_sign_n`)? This would
 #'   effectively show a sign for all values except zero on either of those
 #'   numeric components of the notation. If so, use `TRUE` for either one of
 #'   these options. The default for both is `FALSE`, where only negative numbers
@@ -742,14 +869,29 @@ vec_fmt_engineering <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param scale_values Should the values be scaled through multiplication by
-#'   100? By default this is `TRUE` since the expectation is that normally
-#'   values are proportions. Setting to `FALSE` signifies that the values are
+#'
+#' @param scale_values *Multiply input values by 100*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the values be scaled through multiplication by 100? By default this
+#'   scaling is performed since the expectation is that incoming values are
+#'   usually proportional. Setting to `FALSE` signifies that the values are
 #'   already scaled and require only the percent sign when formatted.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the percent sign. The default is to not introduce a space character.
-#' @param placement The placement of the percent sign. This can be either be
-#'   `right` (the default) or `left`.
+#'
+#' @param incl_space *Include a space between the value and the % sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option for whether to include a space between the value and the percent
+#'   sign. The default is to not introduce a space character.
+#'
+#' @param placement *Percent sign placement*
+#'
+#'   `scalar<character>` --- *default:* `"right"`
+#'
+#'   This option governs the placement of the percent sign. This can be either
+#'   be `right` (the default) or `left`.
 #'
 #' @return A character vector.
 #'
@@ -929,22 +1071,42 @@ vec_fmt_percent <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param to_units A keyword that signifies the desired output quantity. This
-#'   can be any from the following set: `"per-mille"`, `"per-myriad"`, `"pcm"`,
-#'   `"ppm"`, `"ppb"`, `"ppt"`, or `"ppq"`.
-#' @param symbol The symbol/units to use for the quantity. By default, this is
-#'   set to `"auto"` and **gt** will choose the appropriate symbol based on the
+#'
+#' @param to_units *Output Quantity*
+#'
+#'   `singl-kw:[per-mille|per-myriad|pcm|ppm|ppb|ppt|ppq]` --- *default:* `"per-mille"`
+#'
+#'   A keyword that signifies the desired output quantity. This can be any from
+#'   the following set: `"per-mille"`, `"per-myriad"`, `"pcm"`, `"ppm"`,
+#'   `"ppb"`, `"ppt"`, or `"ppq"`.
+#'
+#' @param symbol *Symbol or units to use in output display*
+#'
+#'   `scalar<character>` --- *default:* `"auto"`
+#'
+#'   The symbol/units to use for the quantity. By default, this is set to
+#'   `"auto"` and **gt** will choose the appropriate symbol based on the
 #'   `to_units` keyword and the output context. However, this can be changed by
 #'   supplying a string (e.g, using `symbol = "ppbV"` when `to_units = "ppb"`).
-#' @param scale_values Should the values be scaled through multiplication
-#'   according to the keyword set in `to_units`? By default this is `TRUE` since
-#'   the expectation is that normally values are proportions. Setting to `FALSE`
-#'   signifies that the values are already scaled and require only the
-#'   appropriate symbol/units when formatted.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the symbol/units. The default is `"auto"` which provides spacing
-#'   dependent on the mark itself. This can be directly controlled by using
-#'   either `TRUE` or `FALSE`.
+#'
+#' @param scale_values *Scale input values accordingly*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should the values be scaled through multiplication according to the keyword
+#'   set in `to_units`? By default this is `TRUE` since the expectation is that
+#'   normally values are proportions. Setting to `FALSE` signifies that the
+#'   values are already scaled and require only the appropriate symbol/units
+#'   when formatted.
+#'
+#' @param incl_space *Include a space between the value and the symbol/units*
+#'
+#'   `scalar<character>|scalar<logical>` --- *default:* `"auto"`
+#'
+#'   An option for whether to include a space between the value and the
+#'   symbol/units. The default is `"auto"` which provides spacing dependent on
+#'   the mark itself. This can be directly controlled by using either `TRUE` or
+#'   `FALSE`.
 #'
 #' @return A character vector.
 #'
@@ -1111,21 +1273,36 @@ vec_fmt_partsper <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param accuracy The type of fractions to generate. This can either be one of
-#'   the keywords `"low"`, `"med"`, or `"high"` (to generate fractions with
-#'   denominators of up to 1, 2, or 3 digits, respectively) or an integer value
-#'   greater than zero to obtain fractions with a fixed denominator (`2` yields
-#'   halves, `3` is for thirds, `4` is quarters, etc.). For the latter option,
-#'   using `simplify = TRUE` will simplify fractions where possible (e.g., `2/4`
-#'   will be simplified as `1/2`). By default, the `"low"` option is used.
-#' @param simplify If choosing to provide a numeric value for `accuracy`, the
-#'   option to simplify the fraction (where possible) can be taken with `TRUE`
-#'   (the default). With `FALSE`, denominators in fractions will be fixed to the
+#'
+#' @param accuracy *Accuracy of fractions*
+#'
+#'   `singl-kw:[low|med|high]|scalar<numeric|integer>(val>=1)` --- *default:* `"low"`
+#'
+#'   The type of fractions to generate. This can either be one of the keywords
+#'   `"low"`, `"med"`, or `"high"` (to generate fractions with denominators of
+#'   up to 1, 2, or 3 digits, respectively) or an integer value greater than
+#'   zero to obtain fractions with a fixed denominator (`2` yields halves, `3`
+#'   is for thirds, `4` is quarters, etc.). For the latter option, using
+#'   `simplify = TRUE` will simplify fractions where possible (e.g., `2/4` will
+#'   be simplified as `1/2`). By default, the `"low"` option is used.
+#'
+#' @param simplify *Simplify the fraction*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   If choosing to provide a numeric value for `accuracy`, the option to
+#'   simplify the fraction (where possible) can be taken with `TRUE` (the
+#'   default). With `FALSE`, denominators in fractions will be fixed to the
 #'   value provided in `accuracy`.
-#' @param layout For HTML output, the `"inline"` layout is the default. This
-#'   layout places the numerals of the fraction on the baseline and uses a
-#'   standard slash character. The `"diagonal"` layout will generate fractions
-#'   that are typeset with raised/lowered numerals and a virgule.
+#'
+#' @param layout *Layout of fractions in HTML output*
+#'
+#'   `singl-kw:[inline|diagonal]` --- *default:* `"inline"`
+#'
+#'   For HTML output, the `"inline"` layout is the default. This layout places
+#'   the numerals of the fraction on the baseline and uses a standard slash
+#'   character. The `"diagonal"` layout will generate fractions that are typeset
+#'   with raised/lowered numerals and a virgule.
 #'
 #' @return A character vector.
 #'
@@ -1265,7 +1442,12 @@ vec_fmt_fraction <- function(
 #' the possible inputs to the `currency` argument.
 #'
 #' @inheritParams vec_fmt_number
-#' @param currency The currency to use for the numeric value. This input can be
+#'
+#' @param currency *Currency to use*
+#'
+#'   `scalar<character>|obj:<gt_currency>` --- *default:* `"USD"`
+#'
+#'   The currency to use for the numeric value. This input can be
 #'   supplied as a 3-letter currency code (e.g., `"USD"` for U.S. Dollars,
 #'   `"EUR"` for the Euro currency). Use [info_currencies()] to get an
 #'   information table with all of the valid currency codes and examples of
@@ -1282,14 +1464,28 @@ vec_fmt_fraction <- function(
 #'   the letter "f" in all other output contexts). Please note that `decimals`
 #'   will default to `2` when using the [currency()] helper function.
 #'
-#'   If nothing is provided to `currency` then `"USD"` (U.S. dollars) will be
-#'   used.
-#' @param use_subunits An option for whether the subunits portion of a currency
-#'   value should be displayed. By default, this is `TRUE`.
-#' @param placement The placement of the currency symbol. This can be either be
-#'   `left` (the default) or `right`.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the currency symbol. The default is to not introduce a space character.
+#' @param use_subunits *Show or hide currency subunits*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option for whether the subunits portion of a currency value should be
+#'   displayed. For example, with an input value of `273.81`, the default
+#'   formatting will produce `"$273.81"`. Removing the subunits (with
+#'   `use_subunits = FALSE`) will give us `"$273"`.
+#'
+#' @param placement *Currency symbol placement*
+#'
+#'   `scalar<character>` --- *default:* `"left"`
+#'
+#'   The placement of the currency symbol. This can be either be `left` (as
+#'   in `"$450"`) or `right` (which yields `"450$"`).
+#'
+#' @param incl_space *Include a space between the value and the currency symbol*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option for whether to include a space between the value and the currency
+#'   symbol. The default is to not introduce a space character.
 #'
 #' @return A character vector.
 #'
@@ -1435,8 +1631,13 @@ vec_fmt_currency <- function(
 #' rounding values as necessary.
 #'
 #' @inheritParams vec_fmt_number
-#' @param case Should Roman numerals should be rendered as uppercase (`"upper"`)
-#'   or lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
+#'
+#' @param case *Use uppercase or lowercase letters*
+#'
+#'   `singl-kw:[upper|lower]` --- *default:* `"upper"`
+#'
+#'   Should Roman numerals should be rendered as uppercase (`"upper"`) or
+#'   lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
 #'
 #' @return A character vector.
 #'
@@ -1546,14 +1747,23 @@ vec_fmt_roman <- function(
 #' diacritical marks).
 #'
 #' @inheritParams vec_fmt_number
-#' @param case Should resulting index characters be rendered as uppercase
-#'   (`"upper"`) or lowercase (`"lower"`) letters? By default, this is set to
-#'   `"upper"`.
-#' @param index_algo The indexing algorithm for handling the recycling of the
-#'   index character set. By default, the `"repeat"` option is used where
-#'   characters are doubled, tripled, and so on, when moving past the character
-#'   set limit. The alternative is the `"excel"` option, where Excel-based
-#'   column naming is adapted and used here (e.g., `[..., Y, Z, AA, AB, ...]`).
+#'
+#' @param case *Use uppercase or lowercase letters*
+#'
+#'   `singl-kw:[upper|lower]` --- *default:* `"upper"`
+#'
+#'   Should the resulting index characters be rendered as uppercase (`"upper"`)
+#'   or lowercase (`"lower"`) letters? By default, this is set to `"upper"`.
+#'
+#' @param index_algo *Indexing algorithm*
+#'
+#'   `singl-kw:[repeat|excel]` --- *default:* `"repeat"`
+#'
+#'   The indexing algorithm handles the recycling of the index character set. By
+#'   default, the `"repeat"` option is used where characters are doubled,
+#'   tripled, and so on, when moving past the character set limit. The
+#'   alternative is the `"excel"` option, where Excel-based column naming is
+#'   adapted and used here (e.g., `[..., Y, Z, AA, AB, ...]`).
 #'
 #' @return A character vector.
 #'
@@ -1826,15 +2036,39 @@ vec_fmt_spelled_num <- function(
 #' formatting specific to the chosen locale
 #'
 #' @inheritParams vec_fmt_number
-#' @param standard The way to express large byte sizes.
-#' @param decimals An option to specify the exact number of decimal places to
-#'   use. The default number of decimal places is `1`.
-#' @param incl_space An option for whether to include a space between the value
-#'   and the units. The default of `TRUE` uses a space character for separation.
-#' @param force_sign Should the positive sign be shown for positive numbers
-#'   (effectively showing a sign for all numbers except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative numbers will
-#'   display a minus sign.
+#'
+#' @param standard *Standard used to express byte sizes*
+#'
+#'   `singl-kw:[decimal|binary]` --- *default:* `"decimal"`
+#'
+#'   The form of expressing large byte sizes is divided between: (1) decimal
+#'   units (powers of 1000; e.g., `"kB"` and `"MB"`), and (2) binary units
+#'   (powers of 1024; e.g., `"KiB"` and `"MiB"`).
+#'
+#' @param decimals *Number of decimal places*
+#'
+#'   `scalar<numeric|integer>(val>=0)` --- *default:* `1`
+#'
+#'   This corresponds to the exact number of decimal places to use. A value
+#'   such as `2.34` can, for example, be formatted with `0` decimal places and
+#'   it would result in `"2"`. With `4` decimal places, the formatted value
+#'   becomes `"2.3400"`. The trailing zeros can be removed with
+#'   `drop_trailing_zeros = TRUE`.
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive numbers (effectively showing
+#'   a sign for all numbers except zero)? If so, use `TRUE` for this option. The
+#'   default is `FALSE`, where only negative numbers will display a minus sign.
+#'
+#' @param incl_space *Include a space between the value and the units*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option for whether to include a space between the value and the units.
+#'   The default is to use a space character for separation.
 #'
 #' @return A character vector.
 #'
@@ -1977,9 +2211,14 @@ vec_fmt_bytes <- function(
 #' `YYYY-MM-DD`).
 #'
 #' @inheritParams vec_fmt_number
-#' @param date_style The date style to use. By default this is `"iso"` which
-#'   corresponds to ISO 8601 date formatting. The other date styles can be
-#'   viewed using [info_date_style()].
+#'
+#' @param date_style *Predefined style for dates*
+#'
+#'   `scalar<character>|scalar<numeric|integer>(1<=val<=41)` --- *default:* `"iso"`
+#'
+#'   The date style to use. By default this is the short name `"iso"` which
+#'   corresponds to ISO 8601 date formatting. There are 41 date styles in total
+#'   and their short names can be viewed using [info_date_style()].
 #'
 #' @return A character vector.
 #'
@@ -2158,9 +2397,15 @@ vec_fmt_date <- function(
 #' always results in the formatting of `00:00:00`).
 #'
 #' @inheritParams vec_fmt_number
-#' @param time_style The time style to use. By default this is `"iso"` which
-#'   corresponds to how times are formatted within ISO 8601 datetime values. The
-#'   other time styles can be viewed using [info_time_style()].
+#'
+#' @param time_style *Predefined style for times*
+#'
+#'   `scalar<character>|scalar<numeric|integer>(1<=val<=25)` --- *default:* `"iso"`
+#'
+#'   The time style to use. By default this is the short name `"iso"` which
+#'   corresponds to how times are formatted within ISO 8601 datetime values.
+#'   There are 25 time styles in total and their short names can be viewed using
+#'   [info_time_style()].
 #'
 #' @return A character vector.
 #'
@@ -2329,16 +2574,33 @@ vec_fmt_time <- function(
 #' the ISO 8601 form of `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`).
 #'
 #' @inheritParams vec_fmt_number
+#'
 #' @inheritParams vec_fmt_date
+#'
 #' @inheritParams vec_fmt_time
-#' @param sep The separator string to use between the date and time components.
-#'   By default, this is a single space character (`" "`). Only used when not
+#'
+#' @param sep *Separator between date and time components*
+#'
+#'   `scalar<character>` --- *default:* `" "`
+#'
+#'   The separator string to use between the date and time components. By
+#'   default, this is a single space character (`" "`). Only used when not
 #'   specifying a `format` code.
-#' @param format An optional format code used for generating custom dates/times.
-#'   If used then the arguments governing preset styles (`date_style` and
+#'
+#' @param format *Date/time formatting string*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional formatting string used for generating custom dates/times. If
+#'   used then the arguments governing preset styles (`date_style` and
 #'   `time_style`) will be ignored in favor of formatting via the `format`
 #'   string.
-#' @param tz The time zone for printing dates/times (i.e., the output). The
+#'
+#' @param tz *Time zone*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The time zone for printing dates/times (i.e., the output). The
 #'   default of `NULL` will preserve the time zone of the input data in the
 #'   output. If providing a time zone, it must be one that is recognized by the
 #'   user's operating system (a vector of all valid `tz` values can be produced
@@ -3183,45 +3445,74 @@ vec_fmt_datetime <- function(
 #' which is `c("days", "hours", "minutes", "seconds")`
 #'
 #' @inheritParams vec_fmt_number
-#' @param input_units If one or more selected columns contains numeric values, a
-#'   keyword must be provided for `input_units` for **gt** to determine how
-#'   those values are to be interpreted in terms of duration. The accepted units
-#'   are: `"seconds"`, `"minutes"`, `"hours"`, `"days"`, and `"weeks"`.
-#' @param output_units Controls the output time units. The default, `NULL`,
-#'   means that **gt** will automatically choose time units based on the input
-#'   duration value. To control which time units are to be considered for output
-#'   (before trimming with `trim_zero_units`) we can specify a vector of one or
-#'   more of the following keywords: `"weeks"`, `"days"`, `"hours"`,
-#'   `"minutes"`, or `"seconds"`.
-#' @param duration_style A choice of four formatting styles for the output
-#'   duration values. With `"narrow"` (the default style), duration values will
-#'   be formatted with single letter time-part units (e.g., 1.35 days will be
-#'   styled as `"1d 8h 24m`). With `"wide"`, this example value will be expanded
-#'   to `"1 day 8 hours 24 minutes"` after formatting. The `"colon-sep"` style
-#'   will put days, hours, minutes, and seconds in the `"([D]/)[HH]:[MM]:[SS]"`
+#'
+#' @param input_units *Declaration of duration units for numerical values*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   If one or more selected columns contains numeric values (not `difftime`
+#'   values, which contain the duration units), a keyword must be provided for
+#'   `input_units` for **gt** to determine how those values are to be
+#'   interpreted in terms of duration. The accepted units are: `"seconds"`,
+#'   `"minutes"`, `"hours"`, `"days"`, and `"weeks"`.
+#'
+#' @param output_units *Choice of output units*
+#'
+#'   `mult-kw:[weeks|days|hours|minutes|seconds]` --- *default:* `NULL` (`optional`)
+#'
+#'   Controls the output time units. The default, `NULL`, means that **gt** will
+#'   automatically choose time units based on the input duration value. To
+#'   control which time units are to be considered for output (before trimming
+#'   with `trim_zero_units`) we can specify a vector of one or more of the
+#'   following keywords: `"weeks"`, `"days"`, `"hours"`, `"minutes"`, or
+#'   `"seconds"`.
+#'
+#' @param duration_style *Style for representing duration values*
+#'
+#'   `singl-kw:[narrow|wide|colon-sep|iso]` --- *default:* `"narrow"`
+#'
+#'   A choice of four formatting styles for the output duration values. With
+#'   `"narrow"` (the default style), duration values will be formatted with
+#'   single letter time-part units (e.g., 1.35 days will be styled as
+#'   `"1d 8h 24m"`). With `"wide"`, this example value will be expanded to
+#'   `"1 day 8 hours 24 minutes"` after formatting. The `"colon-sep"` style will
+#'   put days, hours, minutes, and seconds in the `"([D]/)[HH]:[MM]:[SS]"`
 #'   format. The `"iso"` style will produce a value that conforms to the ISO
 #'   8601 rules for duration values (e.g., 1.35 days will become `"P1DT8H24M"`).
-#' @param trim_zero_units Provides methods to remove output time units that have
-#'   zero values. By default this is `TRUE` and duration values that might
-#'   otherwise be formatted as `"0w 1d 0h 4m 19s"` with
-#'   `trim_zero_units = FALSE` are instead displayed as `"1d 4m 19s"`. Aside
-#'   from using `TRUE`/`FALSE` we could provide a vector of keywords for more
-#'   precise control. These keywords are: (1) `"leading"`, to omit all leading
-#'   zero-value time units (e.g., `"0w 1d"` -> `"1d"`), (2) `"trailing"`, to
-#'   omit all trailing zero-value time units (e.g., `"3d 5h 0s"` -> `"3d 5h"`),
-#'   and `"internal"`, which removes all internal zero-value time units (e.g.,
-#'   `"5d 0h 33m"` -> `"5d 33m"`).
-#' @param max_output_units If `output_units` is `NULL`, where the output time
-#'   units are unspecified and left to **gt** to handle, a numeric value
-#'   provided for `max_output_units` will be taken as the maximum number of time
-#'   units to display in all output time duration values. By default, this is
-#'   `NULL` and all possible time units will be displayed. This option has no
-#'   effect when `duration_style = "colon-sep"` (only `output_units` can be used
-#'   to customize that type of duration output).
-#' @param force_sign Should the positive sign be shown for positive values
-#'   (effectively showing a sign for all values except zero)? If so, use `TRUE`
-#'   for this option. The default is `FALSE`, where only negative value will
-#'   display a minus sign.
+#'
+#' @param trim_zero_units *Trimming of zero values*
+#'
+#'   `scalar<logical>|mult-kw:[leading|trailing|internal]` --- *default:* `TRUE`
+#'
+#'   Provides methods to remove output time units that have zero values. By
+#'   default this is `TRUE` and duration values that might otherwise be
+#'   formatted as `"0w 1d 0h 4m 19s"` with `trim_zero_units = FALSE` are instead
+#'   displayed as `"1d 4m 19s"`. Aside from using `TRUE`/`FALSE` we could
+#'   provide a vector of keywords for more precise control. These keywords are:
+#'   (1) `"leading"`, to omit all leading zero-value time units (e.g., `"0w 1d"`
+#'   -> `"1d"`), (2) `"trailing"`, to omit all trailing zero-value time units
+#'   (e.g., `"3d 5h 0s"` -> `"3d 5h"`), and `"internal"`, which removes all
+#'   internal zero-value time units (e.g., `"5d 0h 33m"` -> `"5d 33m"`).
+#'
+#' @param max_output_units *Maximum number of time units to display*
+#'
+#'   `scalar<numeric|integer>(val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   If `output_units` is `NULL`, where the output time units are unspecified
+#'   and left to **gt** to handle, a numeric value provided for
+#'   `max_output_units` will be taken as the maximum number of time units to
+#'   display in all output time duration values. By default, this is `NULL` and
+#'   all possible time units will be displayed. This option has no effect when
+#'   `duration_style = "colon-sep"` (only `output_units` can be used to
+#'   customize that type of duration output).
+#'
+#' @param force_sign *Forcing the display of a positive sign*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the positive sign be shown for positive values (effectively showing
+#'   a sign for all values except zero)? If so, use `TRUE` for this option. By
+#'   default only negative values will display a minus sign.
 #'
 #' @return A character vector.
 #'
@@ -3397,10 +3688,15 @@ vec_fmt_duration <- function(
 #' appropriate output type.
 #'
 #' @inheritParams vec_fmt_number
-#' @param md_engine The engine preference for Markdown rendering. By default,
-#'   this is set to `"markdown"` where **gt** will use the **markdown** package
-#'   for Markdown conversion to HTML and LaTeX. The other option is
-#'   `"commonmark"` and with that the **commonmark** package will be used.
+#'
+#' @param md_engine *Choice of Markdown engine*
+#'
+#'   `singl-kw:[markdown|commonmark]` --- *default:* `"markdown"`
+#'
+#'   The engine preference for Markdown rendering. By default, this is set to
+#'   `"markdown"` where **gt** will use the **markdown** package for Markdown
+#'   conversion to HTML and LaTeX. The other option is `"commonmark"` and with
+#'   that the **commonmark** package will be used.
 #'
 #' @return A character vector.
 #'
diff --git a/R/gt.R b/R/gt.R
index 7344448cfb..871a8c01ed 100644
--- a/R/gt.R
+++ b/R/gt.R
@@ -47,39 +47,92 @@
 #' `row_group.sep` argument allows for control in how the row group label will
 #' appear in the display table.
 #'
-#' @param data A `data.frame` object or a tibble.
-#' @param rowname_col The column name in the input `data` table to use as row
-#'   captions to be placed in the display table stub. If the `rownames_to_stub`
-#'   option is `TRUE` then any column name provided to `rowname_col` will be
-#'   ignored.
-#' @param groupname_col The column name in the input `data` table to use as
-#'   group labels for generation of stub row groups. If the input `data` table
-#'   has the `grouped_df` class (through use of the [dplyr::group_by()] function
-#'   or associated `group_by*()` functions) then any input here is ignored.
-#' @param process_md Should the contents of the `rowname_col` and
-#'   `groupname_col` be interpreted as Markdown? By default this is `FALSE`.
-#' @param caption An optional table caption to use for cross-referencing in R
-#'   Markdown, Quarto, or **bookdown**.
-#' @param rownames_to_stub An option to take rownames from the input `data`
-#'   table as row captions in the display table stub.
-#' @param row_group_as_column An option that alters the display of row group
-#'   labels. By default this is `FALSE` and row group labels will appear in
-#'   dedicated rows above their respective groups of rows. If `TRUE`, row group
-#'   labels will occupy a secondary column in the table stub.
-#' @param auto_align Optionally have column data be aligned depending on the
-#'   content contained in each column of the input `data`. Internally, this
-#'   calls `cols_align(align = "auto")` for all columns.
-#' @param id The table ID. By default, with `NULL`, this will be a random,
-#'   ten-letter ID as generated by using the [random_id()] function. A custom
-#'   table ID can be used with any single-length character vector.
-#' @param locale An optional locale ID that can be set as the default locale for
-#'   all functions that take a `locale` argument. Examples of valid locales
-#'   include `"en"` for English (United States) and `"fr"` for French (France).
-#'   Refer to the information provided by the [info_locales()] function to
-#'   determine which locales are supported.
-#' @param row_group.sep The separator to use between consecutive group names (a
-#'   possibility when providing `data` as a `grouped_df` with multiple groups)
-#'   in the displayed stub row group label.
+#' @param data *Input data table*
+#'
+#'   `obj:<data.frame>|obj:<tbl_df>` --- **required**
+#'
+#'   A `data.frame` object or a tibble (`tbl_df`).
+#'
+#' @param rowname_col *Column for row names/labels from `data`*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The column name in the input `data` table to use as row labels to be placed
+#'   in the table stub. If the `rownames_to_stub` option is `TRUE` then any
+#'   column name provided to `rowname_col` will be ignored.
+#'
+#' @param groupname_col *Column for group names/labels from `data`*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The column name in the input `data` table to use as group labels for
+#'   generation of stub row groups. If the input `data` table has the
+#'   `grouped_df` class (through use of the [dplyr::group_by()] function or
+#'   associated `group_by*()` functions) then any input here is ignored.
+#'
+#' @param process_md *Process Markdown in `rowname_col` and `groupname_col`*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the contents of the `rowname_col` and `groupname_col` be interpreted
+#'   as Markdown? By default this won't happen.
+#'
+#' @param caption *Table caption text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional table caption to use for cross-referencing in R Markdown,
+#'   Quarto, or **bookdown**.
+#'
+#' @param rownames_to_stub *Use data frame row labels in the stub*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option to take rownames from the input `data` table (should they be
+#'   available) as row labels in the display table stub.
+#'
+#' @param row_group_as_column *Mode for displaying row group labels in the stub*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   An option that alters the display of row group labels. By default this is
+#'   `FALSE` and row group labels will appear in dedicated rows above their
+#'   respective groups of rows. If `TRUE` row group labels will occupy a
+#'   secondary column in the table stub.
+#'
+#' @param auto_align *Automatic alignment of column values and labels*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Optionally have column data be aligned depending on the content contained
+#'   in each column of the input `data`. Internally, this calls
+#'   `cols_align(align = "auto")` for all columns.
+#'
+#' @param id *The table ID*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   By default (with `NULL`) this will be a random, ten-letter ID as generated
+#'   by using the [random_id()] function. A custom table ID can be used be
+#'   providing a single-length character vector.
+#'
+#' @param locale *Locale identifier*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional locale identifier that can be set as the default locale for all
+#'   functions that take a `locale` argument. Examples include `"en"` for
+#'   English (United States) and `"fr"` for French (France). We can use the
+#'   [info_locales()] function as a useful reference for all of the locales that
+#'   are supported.
+#'
+#' @param row_group.sep *Separator text for multiple row group labels*
+#'
+#'   `scalar<character>` --- *default:* `getOption("gt.row_group.sep", " - ")`
+#'
+#'   The separator to use between consecutive group names (a possibility when
+#'   providing `data` as a `grouped_df` with multiple groups) in the displayed
+#'   row group label.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/gt_group.R b/R/gt_group.R
index bc3b6f8708..e0d5322300 100644
--- a/R/gt_group.R
+++ b/R/gt_group.R
@@ -33,11 +33,25 @@
 #' can be printed independently and table separation (usually a page break)
 #' occurs between each of those.
 #'
-#' @param ... One or more **gt** table (`gt_tbl`) objects, typically generated
-#'   via the [gt()] function.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
-#' @param .use_grp_opts Should options specified in the `gt_group` object be
-#'   applied to all contained **gt** tables? By default this is `FALSE`.
+#' @param ... *One or more gt table data objects*
+#'
+#'   `obj:<gt_tbl>` --- (`optional`)
+#'
+#'   One or more **gt** table (`gt_tbl`) objects, typically generated via the
+#'   [gt()] function.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .use_grp_opts *Apply options to all contained tables?*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should options specified in the `gt_group` object be applied to all
+#'   contained **gt** tables? By default this is `FALSE`.
 #'
 #' @return An object of class `gt_group`.
 #'
@@ -96,9 +110,19 @@ gt_group <- function(
 #' The only thing you need to provide is the index value for the **gt** table
 #' within the `gt_group` object.
 #'
-#' @param data A `gt_group` container object, typically generated through use of
-#'   the [gt_group()] function along with one or more `gt_tbl` objects.
-#' @param which An index value denoting which `gt_tbl` table should be obtained
+#' @param data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is a `gt_group` container object. It is typically generated through
+#'   use of the [gt_group()] function along with one or more `gt_tbl` objects,
+#'   or, made by splitting a **gt** table with [gt_split()].
+#'
+#' @param which *The table to pull from the group*
+#'
+#'   `scalar<numeric|integer>` --- **required**
+#'
+#'   A single index value denoting which `gt_tbl` table should be obtained
 #'   from the `gt_group` object.
 #'
 #' @return An object of class `gt_tbl`.
@@ -143,15 +167,35 @@ grp_pull <- function(
 #' workflow might be, the `grp_add()` function makes it possible to flexibly
 #' add one or more new **gt** tables, returning a refreshed `gt_group` object.
 #'
-#' @param .data A `gt_group` container object, typically generated through use
-#'   of the [gt_group()] function along with one or more `gt_tbl` objects.
-#' @param ... One or more **gt** table (`gt_tbl`) objects, typically generated
-#'   via the [gt()] function.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
-#' @param .before,.after A single index for either `.before` or `.after`,
-#'   specifying where the supplied `gt_tbl` objects should be placed amongst the
-#'   existing collection of **gt** tables. If nothing is provided for either
-#'   argument the incoming `gt_tbl` objects will be appended.
+#' @param .data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is a `gt_group` container object. It is typically generated through
+#'   use of the [gt_group()] function along with one or more `gt_tbl` objects,
+#'   or, made by splitting a **gt** table with [gt_split()].
+#'
+#' @param ... *One or more gt table objects*
+#'
+#'   `obj:<gt_tbl>` --- **required** (or, use `...`)
+#'
+#'   One or more **gt** table (`gt_tbl`) objects, typically generated via the
+#'   [gt()] function.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .before,.after *Table used as anchor*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   A single index for either `.before` or `.after`, specifying where the
+#'   supplied `gt_tbl` objects should be placed amongst the existing collection
+#'   of **gt** tables. If nothing is provided for either argument the incoming
+#'   `gt_tbl` objects will be appended.
 #'
 #' @return An object of class `gt_group`.
 #'
@@ -280,14 +324,29 @@ grp_add <- function(
 #' function and the placement of the cloned **gt** tables can be controlled with
 #' either the `before` or `after` arguments.
 #'
-#' @param data A `gt_group` container object, typically generated through use
-#'   of the [gt_group()] function along with one or more `gt_tbl` objects.
-#' @param which A vector of index values denoting which `gt_tbl` tables should
-#'   be cloned inside of the `gt_group` object.
-#' @param before,after A single index for either `before` or `after`,
-#'   specifies where the cloned `gt_tbl` objects should be placed amongst the
-#'   existing collection of **gt** tables. If nothing is provided for either
-#'   argument the incoming `gt_tbl` objects will be appended.
+#' @param data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is a `gt_group` container object. It is typically generated through
+#'   use of the [gt_group()] function along with one or more `gt_tbl` objects,
+#'   or, made by splitting a **gt** table with [gt_split()].
+#'
+#' @param which *The tables to clone*
+#'
+#'   `vector<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   A vector of index values denoting which **gt** tables should be cloned
+#'   inside of the `gt_group` object.
+#'
+#' @param before,after *Table used as anchor*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   A single index for either `before` or `after`, specifies where the cloned
+#'   `gt_tbl` objects should be placed amongst the existing collection of **gt**
+#'   tables. If nothing is provided for either argument, the incoming `gt_tbl`
+#'   objects will be appended.
 #'
 #' @return An object of class `gt_group`.
 #'
@@ -403,13 +462,33 @@ grp_clone <- function(
 #' tables provided must equal the number of indices for tables present in the
 #' `gt_group` object.
 #'
-#' @param .data A `gt_group` container object, typically generated through use
-#'   of the [gt_group()] function along with one or more `gt_tbl` objects.
-#' @param ... One or more **gt** table (`gt_tbl`) objects, typically generated
-#'   via the [gt()] function.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
-#' @param .which Index values denoting which `gt_tbl` tables should be replaced
-#'   in the `gt_group` object.
+#' @param .data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is a `gt_group` container object. It is typically generated through
+#'   use of the [gt_group()] function along with one or more `gt_tbl` objects,
+#'   or, made by splitting a **gt** table with [gt_split()].
+#'
+#' @param ... *One or more gt table objects*
+#'
+#'   `obj:<gt_tbl>` --- **required** (or, use `...`)
+#'
+#'   One or more **gt** table (`gt_tbl`) objects, typically generated via the
+#'   [gt()] function.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .which *The tables to replace*
+#'
+#'   `vector<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   A vector of index values denoting which **gt** tables should be replaced
+#'   inside of the `gt_group` object.
 #'
 #' @return An object of class `gt_group`.
 #'
@@ -475,9 +554,19 @@ grp_replace <- function(
 #' specified `gt_tbl` objects gone. The only thing you need to provide is the
 #' index value for the **gt** table within the `gt_group` object.
 #'
-#' @param data A `gt_group` container object, typically generated through use of
-#'   the [gt_group()] function along with one or more `gt_tbl` objects.
-#' @param which An index value denoting which `gt_tbl` table should be removed
+#' @param data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is a `gt_group` container object. It is typically generated through
+#'   use of the [gt_group()] function along with one or more `gt_tbl` objects,
+#'   or, made by splitting a **gt** table with [gt_split()].
+#'
+#' @param which *The table to remove from the group*
+#'
+#'   `scalar<numeric|integer>` --- **required**
+#'
+#'   A single index value denoting which `gt_tbl` table should be removed
 #'   from the `gt_group` object.
 #'
 #' @return An object of class `gt_group`.
@@ -507,8 +596,14 @@ grp_rm <- function(
 #' element that can adjusted.
 #'
 #' @inheritParams tab_options
-#' @param data A `gt_group` container object, typically generated through use of
-#'   the [gt_group()] function along with one or more `gt_tbl` objects.
+#'
+#' @param data *The gt table group object*
+#'
+#'   `obj:<gt_group>` --- **required**
+#'
+#'   This is `gt_group` container object. It is typically generated through use
+#'   of the [gt_group()] function along with one or more `gt_tbl` objects, or,
+#'   made by splitting a **gt** table with [gt_split()].
 #'
 #' @return An object of class `gt_group`.
 #'
diff --git a/R/gt_preview.R b/R/gt_preview.R
index 5bc7a7609d..5cff932b6d 100644
--- a/R/gt_preview.R
+++ b/R/gt_preview.R
@@ -33,15 +33,33 @@
 #' modify the output of `gt_preview()`. Furthermore, you cannot pass a **gt**
 #' object to `gt_preview()`.
 #'
-#' @param data A `data.frame` object or a tibble.
-#' @param top_n This value will be used as the number of rows from the top of
-#'   the table to display. The default, `5`, will show the first five rows of
-#'   the table.
-#' @param bottom_n The value will be used as the number of rows from the bottom
+#' @param data *Input data table*
+#'
+#'   `obj:<data.frame>|obj:<tbl_df>` --- **required**
+#'
+#'   A `data.frame` object or a tibble (`tbl_df`).
+#'
+#' @param top_n *Top n rows to display*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `5`
+#'
+#'   The `top_n` value will be used as the number of rows from the top of the
+#'   table to display. The default, `5`, will show the first five rows of the
+#'   table.
+#'
+#' @param bottom_n *Bottom n rows to display*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1`
+#'
+#'   The `bottom_n` value will be used as the number of rows from the bottom
 #'   of the table to display. The default, `1`, will show the final row of the
 #'   table.
-#' @param incl_rownums An option to include the row numbers for `data` in the
-#'   table stub. By default, this is `TRUE`.
+#'
+#' @param incl_rownums *Display row numbers*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to include the row numbers for `data` in the table stub.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/gt_split.R b/R/gt_split.R
index a7a33a3515..cd633710e3 100644
--- a/R/gt_split.R
+++ b/R/gt_split.R
@@ -32,15 +32,37 @@
 #' smaller tables across multiple pages (in RTF and Word outputs, primarily via
 #' [gtsave()]), or, with breaks between them when the output context is HTML.
 #'
-#' @param data A **gt** table object (`gt_tbl`) that is created using the [gt()]
-#'   function.
-#' @param row_every_n A directive to split at every *n* number of rows. This
-#'   argument expects a single numerical value.
-#' @param row_slice_i An argument for splitting at specific row indices. Here,
-#'   we expect either a vector of index values or a function that evaluates to a
-#'   numeric vector.
-#' @param col_slice_at Any columns where vertical splitting across should occur.
-#'   The splits occur to the right of the resolved column names.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param row_every_n *Split at every n rows*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   A directive to split at every *n* number of rows. This argument expects a
+#'   single numerical value.
+#'
+#' @param row_slice_i *Row-slicing indices*
+#'
+#'   `vector<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   An argument for splitting at specific row indices. Here, we expect either a
+#'   vector of index values or a function that evaluates to a numeric vector.
+#'
+#' @param col_slice_at *Column-slicing locations*
+#'
+#'   `<column-targeting expression>` --- *default:* `NULL` (`optional`)
+#'
+#'   Any columns where vertical splitting across should occur. The splits occur
+#'   to the right of the resolved column names. Can either be a series of column
+#'   names provided in [c()], a vector of column indices, or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()].
 #'
 #' @return An object of class `gt_group`.
 #'
diff --git a/R/helpers.R b/R/helpers.R
index 5cf0d624f6..405d42ce90 100644
--- a/R/helpers.R
+++ b/R/helpers.R
@@ -32,10 +32,14 @@
 #' in HTML but this function `md()`... it's almost like a two-for-one deal (you
 #' get to use Markdown plus any HTML fragments *at the same time*).
 #'
-#' @param text The text that is understood to contain Markdown formatting.
+#' @param text *Markdown text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text that is understood to contain Markdown formatting.
 #'
 #' @return A character object of class `from_markdown`. It's tagged as being
-#'   Markdown text and it will undergo conversion to HTML.
+#'   Markdown text and it will undergo conversion to the desired output context.
 #'
 #' @section Examples:
 #'
@@ -79,8 +83,19 @@ md <- function(text) {
 #' against escaping, so, your HTML tags will come through as HTML when
 #' rendered... to HTML.
 #'
-#' @param text,... The text that is understood to be HTML text, which is to be
-#'   preserved.
+#' @param text *HTML text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text that is understood to be HTML text, which is to be preserved in
+#'   the HTML output context.
+#'
+#' @param ... *Optional parameters for `htmltools::HTML()`*
+#'
+#'   `<multiple expressions>` --- (`optional`)
+#'
+#'   The `htmltools::HTML()` function contains `...` and anything provided here
+#'   will be passed to that internal function call.
 #'
 #' @return A character object of class `html`. It's tagged as an HTML fragment
 #'   that is not to be sanitized.
@@ -143,9 +158,13 @@ is_rtf <- function(x) {
 #' for an absolute definition of size as opposed to the analogous helper
 #' function [pct()].
 #'
-#' @param x the numeric value to format as a string (e.g., `"12px"`) for
-#'   some [tab_options()] arguments that can take values as units of
-#'   pixels (e.g., `table.font.size`).
+#' @param x *Numeric length in pixels*
+#'
+#'   `scalar<numeric|integer>` --- **required**
+#'
+#'   The numeric value to format as a string (e.g., `"12px"`) for some
+#'   [tab_options()] arguments that can take values as units of pixels (e.g.,
+#'   `table.font.size`).
 #'
 #' @return A character vector with a single value in pixel units.
 #'
@@ -199,9 +218,12 @@ px <- function(x) {
 #' [cell_borders()]). Should a more exact definition of size be required, the
 #' analogous helper function [pct()] will be more useful.
 #'
-#' @param x the numeric value to format as a string percentage for some
-#'   [tab_options()] arguments that can take percentage values
-#'   (e.g., `table.width`).
+#' @param x *Numeric value in percent*
+#'
+#'   `scalar<numeric|integer>` --- **required**
+#'
+#'   The numeric value to format as a string percentage for some [tab_options()]
+#'   arguments that can take percentage values (e.g., `table.width`).
 #'
 #' @return A character vector with a single value in percentage units.
 #'
@@ -306,9 +328,12 @@ stub <- function() {
 #' `locations` argument. The header location where the title and optionally the
 #' subtitle reside is generated by the [tab_header()] function.
 #'
-#' @param groups We can either specify `"title"`, `"subtitle"`, or both (the
-#'   default) in a vector to target the title element, the subtitle element, or
-#'   both elements.
+#' @param groups *Specification of groups*
+#'
+#'   `mult-kw:[title|subtitle]` --- *default:* `c("title", "subtitle")`
+#'
+#'   We can either specify `"title"`, `"subtitle"`, or both (the default) in a
+#'   vector to target the title element, the subtitle element, or both elements.
 #'
 #' @return A list object of classes `cells_title` and `location_cells`.
 #'
@@ -517,7 +542,14 @@ cells_stubhead <- function() {
 #' 'column_spanners' location is generated by one or more uses of the
 #' [tab_spanner()] function or the [tab_spanner_delim()] function.
 #'
-#' @param spanners The names of the spanners that are to be targeted.
+#' @param spanners *Specification of spanner IDs*
+#'
+#'   `<spanner-targeting expression>` --- *default:* `everything()`
+#'
+#'   The spanners to which targeting operations are constrained. Can either be a
+#'   series of spanner ID values provided in [c()] or a select helper function.
+#'   Examples of select helper functions include [starts_with()], [ends_with()],
+#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
 #'
 #' @return A list object with the classes `cells_column_spanners` and
 #' `location_cells`.
@@ -622,7 +654,15 @@ cells_column_spanners <- function(spanners = everything()) {
 #' functions' `locations` argument. The 'column_labels' location is present by
 #' default in every **gt** table.
 #'
-#' @param columns The names of the column labels that are to be targeted.
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which targeting operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
 #'
 #' @return A list object with the classes `cells_column_labels` and
 #'   `location_cells`.
@@ -747,7 +787,15 @@ cells_column_labels <- function(columns = everything()) {
 #' (by way of [dplyr::group_by()]), or, by specifying groups with the
 #' [tab_row_group()] function.
 #'
-#' @param groups The names of the row groups that are to be targeted.
+#' @param groups *Specification of row group IDs*
+#'
+#'   `<row-group-targeting expression>` --- *default:* `everything()`
+#'
+#'   The row groups to which targeting operations are constrained. Can either be
+#'   a series of row group ID values provided in [c()] or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()].
 #'
 #' @return A list object with the classes `cells_row_groups` and
 #'   `location_cells`.
@@ -886,7 +934,18 @@ cells_group <- function(groups = everything()) {
 #' [grand_summary_rows()] with neither of the previous two conditions being
 #' true.
 #'
-#' @param rows The names of the rows that are to be targeted.
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   The rows to which targeting operations are constrained. The default
+#'   [everything()] results in all rows in `columns` being formatted.
+#'   Alternatively, we can supply a vector of row captions within [c()], a
+#'   vector of row indices, or a select helper function. Examples of select
+#'   helper functions include [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], [num_range()], and [everything()]. We can also use
+#'   expressions to filter down to the rows we need (e.g., `[colname_1] > 100 &
+#'   [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_stub` and `location_cells`.
 #'
@@ -991,8 +1050,28 @@ cells_stub <- function(rows = everything()) {
 #' functions' `locations` argument. The 'body' location is present by default in
 #' every **gt** table.
 #'
-#' @param columns The names of the columns that are to be targeted.
-#' @param rows The names of the rows that are to be targeted.
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which targeting operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_body` and `location_cells`.
 #'
@@ -1130,9 +1209,39 @@ cells_body <- function(
 #' those functions' `locations` argument. The 'summary' location is generated by
 #' the [summary_rows()] function.
 #'
-#' @param groups The names of the groups that the summary rows reside in.
-#' @param columns The names of the columns that are to be targeted.
-#' @param rows The names of the rows that are to be targeted.
+#' @param groups *Specification of row group IDs*
+#'
+#'   `<row-group-targeting expression>` --- *default:* `everything()`
+#'
+#'   The row groups to which targeting operations are constrained. This aids in
+#'   targeting the summary rows that reside in certain row groups. Can either be
+#'   a series of row group ID values provided in [c()] or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()].
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which targeting operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_summary` and `location_cells`.
 #'
@@ -1302,8 +1411,28 @@ cells_summary <- function(
 #' each of those functions' `locations` argument. The 'grand_summary' location
 #' is generated by the [grand_summary_rows()] function.
 #'
-#' @param columns The names of the columns that are to be targeted.
-#' @param rows The names of the rows that are to be targeted.
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which targeting operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_grand_summary` and
 #'   `location_cells`.
@@ -1448,8 +1577,28 @@ cells_grand_summary <- function(
 #' each of those functions' `locations` argument. The 'stub_summary' location is
 #' generated by the [summary_rows()] function.
 #'
-#' @param groups The names of the groups that are to be targeted.
-#' @param rows The names of the rows that are to be targeted.
+#' @param groups *Specification of row group IDs*
+#'
+#'   `<row-group-targeting expression>` --- *default:* `everything()`
+#'
+#'   The row groups to which targeting operations are constrained. Can either be
+#'   a series of row group ID values provided in [c()] or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()].
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `groups`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_stub_summary` and
 #'   `location_cells`.
@@ -1595,7 +1744,17 @@ cells_stub_summary <- function(
 #' 'stub_grand_summary' location is generated by the [grand_summary_rows()]
 #' function.
 #'
-#' @param rows The names of the rows that are to be targeted.
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   We can specify which rows should be targeted. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
 #'
 #' @return A list object with the classes `cells_stub_grand_summary` and
 #'   `location_cells`.
@@ -1945,9 +2104,18 @@ cells_source_notes <- function() {
 #' we were to specify currency strings for multiple output contexts, names are
 #' required each and every context.
 #'
-#' @param ... One or more named arguments using output contexts as the names and
+#' @param ... *Currency symbols by output context*
+#'
+#'   `<named arguments>` --- **required** (or, use `.list`)
+#'
+#'   One or more named arguments using output contexts as the names and
 #'   currency symbol text as the values.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- **required** (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
 #'
 #' @return A list object of class `gt_currency`.
 #'
@@ -2032,44 +2200,102 @@ currency <- function(
 #' also define several styles within a single call of `cell_text()` and
 #' [tab_style()] will reliably apply those styles to the targeted element.
 #'
-#' @param color The text color.
-#' @param font The font or collection of fonts (subsequent font names are) used
-#'   as fallbacks.
-#' @param size The size of the font. Can be provided as a number that is assumed
-#'   to represent `px` values (or could be wrapped in the [px()]) helper
-#'   function. We can also use one of the following absolute size keywords:
-#'   `"xx-small"`, `"x-small"`, `"small"`, `"medium"`, `"large"`, `"x-large"`,
-#'   or `"xx-large"`.
-#' @param style The text style. Can be one of either `"normal"`, `"italic"`, or
-#'   `"oblique"`.
-#' @param weight The weight of the font. Can be a text-based keyword such as
+#' @param color *Text color*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The text color can be modified through the `color` argument.
+#'
+#' @param font *Font (or collection of fonts) used for text*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The font or collection of fonts (subsequent font names are) used as
+#'   fallbacks.
+#'
+#' @param size *Text size*
+#'
+#'   `scalar<numeric|integer|character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The size of the font. Can be provided as a number that is assumed to
+#'   represent `px` values (or could be wrapped in the [px()]) helper function.
+#'   We can also use one of the following absolute size keywords: `"xx-small"`,
+#'   `"x-small"`, `"small"`, `"medium"`, `"large"`, `"x-large"`, or
+#'   `"xx-large"`.
+#'
+#' @param style *Text style*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Can be one of either `"normal"`, `"italic"`, or `"oblique"`.
+#'
+#' @param weight *Font weight*
+#'
+#'   `scalar<character|numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   The weight of the font can be modified thorough a text-based option such as
 #'   `"normal"`, `"bold"`, `"lighter"`, `"bolder"`, or, a numeric value between
 #'   `1` and `1000`, inclusive. Note that only variable fonts may support the
 #'   numeric mapping of weight.
-#' @param align The text alignment. Can be one of either `"center"`, `"left"`,
-#'   `"right"`, or `"justify"`.
-#' @param v_align The vertical alignment of the text in the cell. Options are
-#'   `"middle"`, `"top"`, or `"bottom"`.
-#' @param stretch Allows for text to either be condensed or expanded. We can use
-#'   one of the following text-based keywords to describe the degree of
+#'
+#' @param align *Text alignment*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The text in a cell can be aligned though one of the following options:
+#'   `"center"`, `"left"`, `"right"`, or `"justify"`.
+#'
+#' @param v_align *Vertical alignment*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The vertical alignment of the text in the cell can be modified through the
+#'   options `"middle"`, `"top"`, or `"bottom"`.
+#'
+#' @param stretch *Stretch text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Allows for text to either be condensed or expanded. We can use one of the
+#'   following text-based keywords to describe the degree of
 #'   condensation/expansion: `"ultra-condensed"`, `"extra-condensed"`,
 #'   `"condensed"`, `"semi-condensed"`, `"normal"`, `"semi-expanded"`,
 #'   `"expanded"`, `"extra-expanded"`, or `"ultra-expanded"`. Alternatively, we
 #'   can supply percentage values from `0\%` to `200\%`, inclusive. Negative
 #'   percentage values are not allowed.
-#' @param decorate Allows for text decoration effect to be applied. Here, we can
-#'   use `"overline"`, `"line-through"`, or `"underline"`.
-#' @param transform Allows for the transformation of text. Options are
-#'   `"uppercase"`, `"lowercase"`, or `"capitalize"`.
-#' @param whitespace A white-space preservation option. By default, runs of
-#'   white-space will be collapsed into single spaces but several options exist
-#'   to govern how white-space is collapsed and how lines might wrap at
-#'   soft-wrap opportunities. The keyword options are `"normal"`, `"nowrap"`,
-#'   `"pre"`, `"pre-wrap"`, `"pre-line"`, and `"break-spaces"`.
-#' @param indent The indentation of the text. Can be provided as a number that
-#'   is assumed to represent `px` values (or could be wrapped in the [px()])
-#'   helper function. Alternatively, this can be given as a percentage (easily
-#'   constructed with [pct()]).
+#'
+#' @param decorate *Decorate text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Allows for text decoration effect to be applied. Here, we can use
+#'   `"overline"`, `"line-through"`, or `"underline"`.
+#'
+#' @param transform *Transform text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Allows for the transformation of text. Options are `"uppercase"`,
+#'   `"lowercase"`, or `"capitalize"`.
+#'
+#' @param whitespace *White-space options*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A white-space preservation option. By default, runs of white-space will be
+#'   collapsed into single spaces but several options exist to govern how
+#'   white-space is collapsed and how lines might wrap at soft-wrap
+#'   opportunities. The options are `"normal"`, `"nowrap"`, `"pre"`,
+#'   `"pre-wrap"`, `"pre-line"`, and `"break-spaces"`.
+#'
+#' @param indent *Text indentation*
+#'
+#'   `scalar<numeric|integer|character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The indentation of the text. Can be provided as a number that is assumed to
+#'   represent `px` values (or could be wrapped in the [px()]) helper function.
+#'   Alternatively, this can be given as a percentage (easily constructed with
+#'   [pct()]).
 #'
 #' @return A list object of class `cell_styles`.
 #'
@@ -2243,12 +2469,21 @@ cell_style_to_html.cell_text <- function(style) {
 #' cells. Specifically, the call to `cell_fill()` should be bound to the
 #' `styles` argument of [tab_style()].
 #'
-#' @param color The fill color. If nothing is provided, then `"#D3D3D3"` (light
-#'   gray) will be used as a default.
-#' @param alpha An optional alpha transparency value for the `color` as single
-#'   value in the range of `0` (fully transparent) to `1` (fully opaque). If not
-#'   provided the fill color will either be fully opaque or use alpha
-#'   information from the color value if it is supplied in the #RRGGBBAA format.
+#' @param color *Cell fill color*
+#'
+#'   `scalar<character>` --- *default:* `"#D3D3D3"`
+#'
+#'   If nothing is provided for `color` then `"#D3D3D3"` (light gray) will be
+#'   used as a default.
+#'
+#' @param alpha *Transparency value*
+#'
+#'   `scalar<numeric|integer>(0>=val>=1)` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional alpha transparency value for the `color` as single value in the
+#'   range of `0` (fully transparent) to `1` (fully opaque). If not provided the
+#'   fill color will either be fully opaque or use alpha information from the
+#'   color value if it is supplied in the `#RRGGBBAA` format.
 #'
 #' @return A list object of class `cell_styles`.
 #'
@@ -2336,16 +2571,36 @@ cell_style_to_html.cell_fill <- function(style) {
 #' With that selection, the `color`, `style`, and `weight` of the selected
 #' borders can then be modified.
 #'
-#' @param sides The border sides to be modified. Options include `"left"`,
+#' @param sides *Border sides*
+#'
+#'   `vector<character>` --- *default:* `"all"`
+#'
+#'   The border sides to be modified. Options include `"left"`,
 #'   `"right"`, `"top"`, and `"bottom"`. For all borders surrounding the
 #'   selected cells, we can use the `"all"` option.
-#' @param color,style,weight The border color, style, and weight. The `color`
-#'   can be defined with a color name or with a hexadecimal color code. The
-#'   default `color` value is `"#000000"` (black). The `style` can be one of
-#'   either `"solid"` (the default), `"dashed"`, `"dotted"`, `"hidden"`, or
-#'   `"double"`. The `weight` of the border lines is to be given in pixel values
-#'   (the [px()] helper function is useful for this. The default value for
-#'   `weight` is `"1px"`. Borders for any defined `sides` can be removed by
+#'
+#' @param color *Border color*
+#'
+#'   `scalar<character>|NULL` --- *default:* `"#000000"`
+#'
+#'   The border `color` can be defined with a color name or with a hexadecimal
+#'   color code. The default `color` value is `"#000000"` (black). Borders for any
+#'   defined `sides` can be removed by supplying `NULL` here.
+#'
+#' @param style *Border line style*
+#'
+#'   `scalar<character>|NULL` --- *default:* `"solid"`
+#'
+#'   The border `style` can be one of either `"solid"` (the default),
+#'   `"dashed"`, `"dotted"`, `"hidden"`, or `"double"`. Borders for any
+#'   defined `sides` can be removed by supplying `NULL` here.
+#'
+#' @param weight *Border weight*
+#'
+#'   `scalar<character>|NULL` --- *default:* `px(1)`
+#'
+#'   The default value for `weight` is `"1px"` and higher values will become
+#'   more visually prominent. Borders for any defined `sides` can be removed by
 #'   supplying `NULL` to any of `color`, `style`, or `weight`.
 #'
 #' @return A list object of class `cell_styles`.
@@ -2553,12 +2808,22 @@ cell_style_structure <- function(name, obj, subclass = name) {
 #' functions from the **scales** package (all of which have a `palette`
 #' argument).
 #'
-#' @param colors A vector of colors that will undergo an adjustment in
-#'   luminance. Each color value provided must either be a color name (in the
-#'   set of colors provided by `grDevices::colors()`) or a hexadecimal string in
-#'   the form of "#RRGGBB" or "#RRGGBBAA".
-#' @param steps A positive or negative factor by which the luminance will be
-#'   adjusted. Must be a number between `-2.0` and `2.0`.
+#' @param colors *Color vector*
+#'
+#'   `vector<character>` --- **required**
+#'
+#'   This is the vector of colors that will undergo an adjustment in luminance.
+#'   Each color value provided must either be a color name (in the set of colors
+#'   provided by `grDevices::colors()`) or a hexadecimal string in the form of
+#'   "#RRGGBB" or "#RRGGBBAA".
+#'
+#' @param steps *Adjustment level*
+#'
+#'   `scalar<numeric|integer>(-2>=val>=2)` --- **required**
+#'
+#'   A positive or negative factor by which the luminance of colors in the
+#'   `colors` vector will be adjusted. Must be a number between `-2.0` and
+#'   `2.0`.
 #'
 #' @return A vector of color values.
 #'
@@ -2669,7 +2934,12 @@ adjust_luminance <- function(
 #' character-based ID value argument of variable length (the default is 10
 #' letters).
 #'
-#' @param n The number of lowercase letters to use for the random ID.
+#' @param n *Number of letters*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `10`
+#'
+#'   The `n` argument defines the number of lowercase letters to use for the
+#'   random ID.
 #'
 #' @return A character vector containing a single, random ID.
 #'
@@ -2707,8 +2977,11 @@ latex_special_chars <- c(
 #' `escape_latex()` function will transform a character vector so that it is
 #' safe to use within LaTeX tables.
 #'
-#' @param text A character vector containing the text that is to be
-#'   LaTeX-escaped.
+#' @param text *LaTeX text*
+#'
+#'   `vector<character>` --- **required**
+#'
+#'   A character vector containing the text that is to be LaTeX-escaped.
 #'
 #' @return A character vector.
 #'
@@ -2826,7 +3099,11 @@ gt_latex_dependencies <- function() {
 #' of [cell_text()] (used with [tab_style()]). To get a helpful listing of fonts
 #' that work well in tables, use the [info_google_fonts()] function.
 #'
-#' @param name The complete name of a font available in *Google Fonts*.
+#' @param name *Google Font name*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The complete name of a font available in *Google Fonts*.
 #'
 #' @return An object of class `font_css`.
 #'
@@ -2995,8 +3272,12 @@ default_fonts <- function() {
 #' function). If using [opt_table_font()] we can invoke this function in its
 #' `stack` argument.
 #'
-#' @param name A keyword from the set of `"system-ui"`, `"transitional"`,
-#'   `"old-style"`, `"humanist"`, `"geometric-humanist"`,
+#' @param name *Name of font stack*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The name of a font stack. Must be drawn from the set of `"system-ui"`,
+#'   `"transitional"`, `"old-style"`, `"humanist"`, `"geometric-humanist"`,
 #'   `"classical-humanist"`, `"neo-grotesque"`, `"monospace-slab-serif"`,
 #'   `"monospace-code"`, `"industrial"`, `"rounded-sans"`, `"slab-serif"`,
 #'   `"antique"`, `"didone"`, and `"handwritten"`.
diff --git a/R/image.R b/R/image.R
index 5bbe55d64b..f31d0f1917 100644
--- a/R/image.R
+++ b/R/image.R
@@ -45,8 +45,18 @@
 #' where a height of `30px` is a default height chosen to work well within the
 #' heights of most table rows.
 #'
-#' @param url A url that resolves to an image file.
-#' @param height The absolute height (px) of the image in the table cell.
+#' @param url *An image URL*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   A url that resolves to an image file.
+#'
+#' @param height *Height of image*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `30`
+#'
+#'   The absolute height of the image in the table cell (in `"px"` units). By
+#'   default, this is set to `"30px"`.
 #'
 #' @return A character object with an HTML fragment that can be placed inside of
 #'   a cell.
@@ -169,8 +179,18 @@ web_image <- function(
 #' where a height of `30px` is a default height chosen to work well within the
 #' heights of most table rows.
 #'
-#' @param filename A path to an image file.
-#' @param height The absolute height (px) of the image in the table cell.
+#' @param filename *Path to image file*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   A local path to an image file on disk.
+#'
+#' @param height *Height of image*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `30`
+#'
+#'   The absolute height of the image in the table cell (in `"px"` units). By
+#'   default, this is set to `"30px"`.
 #'
 #' @return A character object with an HTML fragment that can be placed inside of
 #'   a cell.
@@ -257,13 +277,28 @@ local_image <- function(
 #' the plot (the default `aspect_ratio` is `1.0`) and this is useful for
 #' elongating any given plot to fit better within the table construct.
 #'
-#' @param plot_object A ggplot plot object.
-#' @param height The absolute height (px) of the image in the table cell.
-#' @param aspect_ratio The plot's final aspect ratio. Where the height of the
-#'   plot is fixed using the `height` argument, the `aspect_ratio`
-#'   will either compress (`aspect_ratio` < `1.0`) or expand
-#'   (`aspect_ratio` > `1.0`) the plot horizontally. The default value
-#'   of `1.0` will neither compress nor expand the plot.
+#' @param plot_object *A ggplot plot object*
+#'
+#'   `obj:<ggplot>` --- **required**
+#'
+#'   A `ggplot` plot object.
+#'
+#' @param height *Height of image*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `100`
+#'
+#'   The absolute height of the output image in the table cell (in `"px"`
+#'   units). By default, this is set to `"100px"`.
+#'
+#' @param aspect_ratio *The final aspect ratio of plot*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1.0`
+#'
+#'   This is the plot's final aspect ratio. Where the height of the plot is
+#'   fixed using the `height` argument, the `aspect_ratio` will either compress
+#'   (`aspect_ratio` < `1.0`) or expand (`aspect_ratio` > `1.0`) the plot
+#'   horizontally. The default value of `1.0` will neither compress nor expand
+#'   the plot.
 #'
 #' @return A character object with an HTML fragment that can be placed inside of
 #'   a cell.
@@ -374,8 +409,12 @@ ggplot_image <- function(
 #' is an SVG file. This function is most useful when paired with [local_image()]
 #' since we test various sizes of the test image within that function.
 #'
-#' @param type The type of the image, which can either be `png` (the default) or
-#'   `svg`.
+#' @param type *The image type*
+#'
+#'   `singl-kw:[png|svg]` --- *default:* `"png"`
+#'
+#'   The type of image to produce here can either be `"png"` (the default) or
+#'   `"svg"`.
 #'
 #' @return A character vector with a single path to an image file.
 #'
diff --git a/R/info_tables.R b/R/info_tables.R
index 0449def2f9..cc75f62882 100644
--- a/R/info_tables.R
+++ b/R/info_tables.R
@@ -255,14 +255,23 @@ info_time_style <- function() {
 #' filter currencies in the info table to just the set beginning with the
 #' supplied letter.
 #'
-#' @param type The type of currency information provided. Can either be `code`
-#'   where currency information corresponding to 3-letter currency codes is
-#'   provided, or `symbol` where currency info for common currency names (e.g.,
-#'   dollar, pound, yen, etc.) is returned.
-#' @param begins_with Providing a single letter will filter currencies to only
-#'   those that begin with that letter in their currency code. The default
-#'   (`NULL`) will produce a table with all currencies displayed. This option
-#'   only constrains the information table where `type == "code"`.
+#' @param type *Type of currency*
+#'
+#'   `singl-kw:[code|symbol]` --- *default:* `"code"`
+#'
+#'   The type of currency information provided. Can either be `code` where
+#'   currency information corresponding to 3-letter currency codes is provided,
+#'   or `symbol` where currency info for common currency names (e.g., dollar,
+#'   pound, yen, etc.) is returned.
+#'
+#' @param begins_with *Show currencies beginning with a specific letter*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Providing a single letter will filter currencies to only those that begin
+#'   with that letter in their currency code. The default (`NULL`) will produce
+#'   a table with all currencies displayed. This option only constrains the
+#'   information table where `type == "code"`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -427,9 +436,13 @@ info_currencies <- function(
 #' locales in the info table to just the set that begins with the supplied
 #' letter.
 #'
-#' @param begins_with Providing a single letter will filter locales to only
-#'   those that begin with that letter in their base locale ID. The default
-#'   (`NULL`) will produce a table with all locales displayed.
+#' @param begins_with *Show locales beginning with a specific letter*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Providing a single letter will filter locales to only those that begin
+#'   with that letter in their locale ID. The default (`NULL`) will produce
+#'   a table with all locales displayed
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -557,6 +570,7 @@ info_locales <- function(begins_with = NULL) {
 #' color palettes available in **paletteer**.
 #'
 #' @details
+#'
 #' The palettes displayed are organized by package and by palette name. These
 #' values are required when obtaining a palette (as a vector of hexadecimal
 #' colors), from the the `paletteer::paletteer_d()` function. Once we are
@@ -592,10 +606,14 @@ info_locales <- function(begins_with = NULL) {
 #' \item **yarrr**, 21 palettes
 #' }
 #'
-#' @param color_pkgs A vector of color packages that determines which sets of
-#'   palettes should be displayed in the information table. If this is
-#'   `NULL` (the default) then all of the discrete palettes from all of the
-#'   color packages represented in **paletteer** will be displayed.
+#' @param color_pkgs *Filter to specific color packages*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A vector of color packages that determines which sets of palettes should be
+#'   displayed in the information table. If this is `NULL` (the default) then
+#'   all of the discrete palettes from all of the color packages represented in
+#'   **paletteer** will be displayed.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/modify_columns.R b/R/modify_columns.R
index a8bb4e97db..d6f43b6267 100644
--- a/R/modify_columns.R
+++ b/R/modify_columns.R
@@ -32,15 +32,32 @@
 #' allow **gt** to automatically choose the alignment of each column based on
 #' the data type (with the `auto` option).
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param align The alignment type. This can be any of `"center"`, `"left"`, or
-#'   `"right"` for center-, left-, or right-alignment. Alternatively, the
-#'   `"auto"` option (the default), will automatically align values in columns
-#'   according to the data type (see the Details section for specifics on which
-#'   alignments are applied).
-#' @param columns The columns for which the alignment should be applied. By
-#'   default this is set to `everything()` which means that the chosen alignment
-#'   affects all columns.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param align *Alignment type*
+#'
+#'   `singl-kw:[auto|left|center|right]` --- *default:* `"auto"`
+#'
+#'   This can be any of `"center"`, `"left"`, or `"right"` for center-, left-,
+#'   or right-alignment. Alternatively, the `"auto"` option (the default), will
+#'   automatically align values in columns according to the data type (see the
+#'   Details section for specifics on which alignments are applied).
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the alignment should be applied. Can either be a
+#'   series of column names provided in [c()], a vector of column indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. By default this is set to [everything()]
+#'   which means that the chosen alignment affects all columns.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -183,21 +200,44 @@ determine_which_character_number <- function(
 #' number of columns (the function will skip over columns that don't require
 #' this type of alignment).
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param columns The columns for which the alignment should be applied. By
-#'   default this is set to `everything()` which means that the chosen alignment
-#'   affects all columns.
-#' @param dec_mark The character used as a decimal mark in the numeric values to
-#'   be aligned. If a locale value was used when formatting the numeric values
-#'   then `locale` is better to use and it will override any value here in
-#'   `dec_mark`.
-#' @param locale An optional locale ID that can be used to obtain the type of
-#'   decimal mark used in the numeric values to be aligned. Examples include
-#'   `"en"` for English (United States) and `"fr"` for French (France). The use
-#'   of a valid locale ID will override any value provided in `dec_mark`. We can
-#'   use the [info_locales()] function as a useful reference for all of the
-#'   locales that are supported. Any `locale` value provided here will override
-#'   any global locale setting performed in [gt()]'s own `locale` argument.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which decimal alignment should be applied. Can either be a
+#'   series of column names provided in [c()], a vector of column indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. By default this is set to [everything()]
+#'   which means that decimal alignment will be attempted on all columns.
+#'
+#' @param dec_mark *Decimal mark*
+#'
+#'   `scalar<character>` --- *default:* `"."`
+#'
+#'   The character used as a decimal mark in the numeric values to be aligned.
+#'   If a locale value was used when formatting the numeric values then `locale`
+#'   is better to use and it will override any value here in `dec_mark`.
+#'
+#' @param locale *Locale identifier*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional locale identifier that can be used to obtain the type of
+#'   decimal mark used in the numeric values to be aligned (according to the
+#'   locale's formatting rules). Examples include `"en"` for English (United
+#'   States) and `"fr"` for French (France). We can use the [info_locales()]
+#'   function as a useful reference for all of the locales that are supported. A
+#'   locale ID can be also set in the initial [gt()] function call (where it
+#'   would be used automatically by any function with a `locale` argument) but a
+#'   `locale` value provided here will override that global locale.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -401,21 +441,35 @@ align_to_char <- function(x, align_at = ".") {
 #' left-hand side defines the target columns and the right-hand side is a single
 #' dimension.
 #'
-#' @param .data A table object that is created using the [gt()] function.
-#' @param ... Expressions for the assignment of column widths for the table
-#'   columns in `.data`. Two-sided formulas (e.g, `<LHS> ~ <RHS>`) can be used,
-#'   where the left-hand side corresponds to selections of columns and the
-#'   right-hand side evaluates to single-length character values in the form
-#'   `{##}px` (i.e., pixel dimensions); the [px()] helper function is best used
-#'   for this purpose. Column names should be enclosed in [c()]. The
-#'   column-based select helpers [starts_with()], [ends_with()], [contains()],
-#'   [matches()], [one_of()], and [everything()] can be used in the LHS.
-#'   Subsequent expressions that operate on the columns assigned previously will
-#'   result in overwriting column width values (both in the same `cols_width()`
-#'   call and across separate calls). All other columns can be assigned a
-#'   default width value by using `everything()` on the left-hand
-#'   side.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
+#' @param .data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Column width assignments*
+#'
+#'   `<multiple expressions>` --- **required** (or, use `.list`)
+#'
+#'   Expressions for the assignment of column widths for the table columns in
+#'   `.data`. Two-sided formulas (e.g, `<LHS> ~ <RHS>`) can be used, where the
+#'   left-hand side corresponds to selections of columns and the right-hand side
+#'   evaluates to single-length character values in the form `{##}px` (i.e.,
+#'   pixel dimensions); the [px()] helper function is best used for this
+#'   purpose. Column names should be enclosed in [c()]. The column-based select
+#'   helpers [starts_with()], [ends_with()], [contains()], [matches()],
+#'   [one_of()], and [everything()] can be used in the LHS. Subsequent
+#'   expressions that operate on the columns assigned previously will result in
+#'   overwriting column width values (both in the same `cols_width()` call and
+#'   across separate calls). All other columns can be assigned a default width
+#'   value by using `everything()` on the left-hand side.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- **required** (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -570,21 +624,40 @@ cols_width <- function(
 #' one or more columns and we even have the option to use the [md()] or [html()]
 #' helper functions for rendering column labels from Markdown or using HTML.
 #'
-#' @param .data A table object that is created using the [gt()] function.
-#' @param ... Expressions for the assignment of column labels for the table
-#'   columns in `.data`. Two-sided formulas (e.g., `<LHS> ~ <RHS>`) can be used,
-#'   where the left-hand side corresponds to selections of columns and the
-#'   right-hand side evaluates to single-length values for the label to apply.
-#'   Column names should be enclosed in [c()]. Select helpers like
-#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()], and
-#'   [everything()] can be used in the LHS. Named arguments are also valid as
-#'   input for simple mappings of column name to label text; they should be of
-#'   the form `<column name> = <label>`. Subsequent expressions that operate on
-#'   the columns assigned previously will result in overwriting column width
-#'   values.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
-#' @param .fn An option to specify a function that will be applied to all of the
-#'   provided label values.
+#' @param .data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Column label assignments*
+#'
+#'   `<multiple expressions>` --- **required** (or, use `.list`)
+#'
+#'   Expressions for the assignment of column labels for the table columns in
+#'   `.data`. Two-sided formulas (e.g., `<LHS> ~ <RHS>`) can be used, where the
+#'   left-hand side corresponds to selections of columns and the right-hand side
+#'   evaluates to single-length values for the label to apply. Column names
+#'   should be enclosed in [c()]. Select helpers like [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], and [everything()]
+#'   can be used in the LHS. Named arguments are also valid as input for simple
+#'   mappings of column name to label text; they should be of the form `<column
+#'   name> = <label>`. Subsequent expressions that operate on the columns
+#'   assigned previously will result in overwriting column width values.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- **required** (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .fn *Function to apply*
+#'
+#'   `function` --- *default:* `NULL` (`optional`)
+#'
+#'   An option to specify a function that will be applied to all of the provided
+#'   label values.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -595,7 +668,7 @@ cols_width <- function(
 #' a tibble or data frame must be unique whereas column labels in **gt** have
 #' no requirement for uniqueness (which is useful for labeling columns as, say,
 #' measurement units that may be repeated several times---usually under
-#' different spanner column labels). Thus, we can still easily distinguish
+#' different spanner labels). Thus, we can still easily distinguish
 #' between columns in other **gt** function calls (e.g., in all of the
 #' `fmt*()` functions) even though we may lose distinguishability in column
 #' labels once they have been relabeled.
@@ -677,14 +750,13 @@ cols_width <- function(
 #' Using a subset of the [`towny`] dataset, we can create an interesting **gt**
 #' table. First, only certain columns are selected from the dataset, some
 #' filtering of rows is done, rows are sorted, and then only the first 10 rows
-#' are kept. When introduced to [gt()], we apply some spanner column labels
-#' through two calls of [tab_spanner()] all the table's columns. Below those
-#' spanners, we want to label the columns by the years of interest. Using
-#' `cols_label()` and select expressions on the left side of the formulas, we
-#' can easily relabel multiple columns with common label text. Note that we
-#' cannot use an `=` sign in any of the expressions within `cols_label()`;
-#' because the left-hand side is not a single column name, we must use formula
-#' syntax (i.e., with the `~`).
+#' are kept. When introduced to [gt()], we apply some spanner labels through two
+#' calls of [tab_spanner()] all the table's columns. Below those spanners, we
+#' want to label the columns by the years of interest. Using `cols_label()` and
+#' select expressions on the left side of the formulas, we can easily relabel
+#' multiple columns with common label text. Note that we cannot use an `=` sign
+#' in any of the expressions within `cols_label()`; because the left-hand side
+#' is not a single column name, we must use formula syntax (i.e., with the `~`).
 #'
 #' ```r
 #' towny |>
@@ -835,13 +907,25 @@ cols_label <- function(
 #' function (e.g., `function(x) tools::toTitleCase(x)`).
 #'
 #' @inheritParams fmt_number
-#' @param columns The column names to which the function or function call in
-#'   `fn` should be applied. By default this is set as `everything()` which
-#'   select every column in the table.
-#' @param fn The function or function call to be applied to the column labels.
-#'   This can take the form of a bare function (e.g., `tools::toTitleCase`), a
-#'   function call as a RHS formula (e.g., `~ tools::toTitleCase(.)`), or an
-#'   anonymous function as in `function(x) tools::toTitleCase(x)`.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the column-labeling operations should be applied. Can
+#'   either be a series of column names provided in [c()], a vector of column
+#'   indices, or a select helper function. Examples of select helper functions
+#'   include [starts_with()], [ends_with()], [contains()], [matches()],
+#'   [one_of()], [num_range()], and [everything()].
+#'
+#' @param fn *Function to apply*
+#'
+#'   `function|formula` --- **required**
+#'
+#'   The function or function call to be applied to the column labels. This can
+#'   take the form of a bare function (e.g., `tools::toTitleCase`), a function
+#'   call as a RHS formula (e.g., `~ tools::toTitleCase(.)`), or an anonymous
+#'   function as in `function(x) tools::toTitleCase(x)`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -849,13 +933,13 @@ cols_label <- function(
 #'
 #' It's important to note that while columns can be freely relabeled, we
 #' continue to refer to columns by their original column names. Column names in
-#' a tibble or data frame must be unique whereas column labels in **gt** have
-#' no requirement for uniqueness (which is useful for labeling columns as, say,
+#' a tibble or data frame must be unique whereas column labels in **gt** have no
+#' requirement for uniqueness (which is useful for labeling columns as, say,
 #' measurement units that may be repeated several times---usually under
-#' different spanner column labels). Thus, we can still easily distinguish
-#' between columns in other **gt** function calls (e.g., in all of the
-#' `fmt*()` functions) even though we may lose distinguishability in column
-#' labels once they have been relabeled.
+#' different spanner labels). Thus, we can still easily distinguish between
+#' columns in other **gt** function calls (e.g., in all of the `fmt*()`
+#' functions) even though we may lose distinguishability in column labels once
+#' they have been relabeled.
 #'
 #' @section Examples:
 #'
@@ -1031,10 +1115,27 @@ cols_label_with <- function(
 #' in the table.
 #'
 #' @inheritParams cols_align
-#' @param columns The column names to move to as a group to a different
-#'   position. The order of the remaining columns will be preserved.
-#' @param after A column name used to anchor the insertion of the moved columns.
-#'   All of the moved columns will be placed to the right of this column.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the moving operations should be applied. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. The columns move as a group to a
+#'   different position. The order of the remaining columns will be preserved.
+#'
+#' @param after *Column used as anchor*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column used to anchor the insertion of the moved columns. All of the
+#'   moved columns will be placed to the right of this column. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1155,9 +1256,18 @@ cols_move <- function(
 #' table).
 #'
 #' @inheritParams cols_align
-#' @param columns The column names to move to the left-most side of the table.
-#'   The order in which columns are provided will be preserved (as is the case
-#'   with the remaining columns).
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the moving operations should be applied. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. The columns move as a group to the
+#'   left-most side of the table. The order of the remaining columns will be
+#'   preserved.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1266,9 +1376,18 @@ cols_move_to_start <- function(
 #' preserved (same with the ordering of all other columns in the table).
 #'
 #' @inheritParams cols_align
-#' @param columns The column names to move to the right-most side of the table.
-#'   The order in which columns are provided will be preserved (as is the case
-#'   with the remaining columns).
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the moving operations should be applied. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. The columns move as a group to the
+#'   right-most side of the table. The order of the remaining columns will be
+#'   preserved.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1376,8 +1495,16 @@ cols_move_to_end <- function(
 #' of those columns is not necessary.
 #'
 #' @inheritParams cols_align
-#' @param columns The column names to hide from the output display table. Values
-#'   provided that do not correspond to column names will be disregarded.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to hide in the output display table. Can either be a series of
+#'   column names provided in [c()], a vector of column indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1493,8 +1620,16 @@ cols_hide <- function(
 #' reveal one or more of those.
 #'
 #' @inheritParams cols_align
-#' @param columns The column names to unhide from the output display table.
-#'   Values provided that do not correspond to column names will be disregarded.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to unhide in the output display table. Can either be a series
+#'   of column names provided in [c()], a vector of column indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1600,28 +1735,54 @@ cols_unhide <- function(
 #' formatting of values in different columns will be preserved upon merging.
 #'
 #' @inheritParams cols_align
-#' @param columns The columns that will participate in the merging process. The
-#'   first column name provided will be the target column (i.e., undergo
-#'   mutation) and the other columns will serve to provide input.
-#' @param hide_columns Any column names provided here will have their state
-#'   changed to `hidden` (via internal use of [cols_hide()] if they aren't
-#'   already hidden. This is convenient if the shared purpose of these specified
-#'   columns is only to provide string input to the target column. To suppress
-#'   any hiding of columns, `FALSE` can be used here.
-#' @param rows Rows that will participate in the merging process. Providing
-#'   [everything()] (the default) results in all rows in `columns` undergoing
-#'   merging. Alternatively, we can supply a vector of row identifiers within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use a standalone predicate expression to filter down to the
-#'   rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
-#' @param pattern A formatting pattern that specifies the arrangement of the
-#'   `column` values and any string literals. The pattern uses numbers (within
-#'   `{ }`) that correspond to the indices of columns provided in `columns`. If
-#'   two columns are provided in `columns` and we would like to combine the cell
-#'   data onto the first column, `"{1} {2}"` could be used. If a pattern isn't
-#'   provided then a space-separated pattern that includes all `columns` will be
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The columns for which the merging operations should be applied. The first
+#'   column resolved will be the target column (i.e., undergo mutation) and the
+#'   other columns will serve to provide input. Can either be a series of column
+#'   names provided in [c()], a vector of column indices, or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()]. A vector is recommended because in that case we are
+#'   absolutely certain about the order of columns, and, that order information
+#'   is needed for this and other arguments.
+#'
+#' @param hide_columns *Subset of `columns` to hide*
+#'
+#'   `<column-targeting expression>|FALSE` --- *default:* `columns[-1]`
+#'
+#'   Any column names provided here will have their state changed to `hidden`
+#'   (via internal use of [cols_hide()]) if they aren't already hidden. This is
+#'   convenient if the shared purpose of these specified columns is only to
+#'   provide string input to the target column. To suppress any hiding of
+#'   columns, `FALSE` can be used here.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   participate in the merging process. The default [everything()] results in
+#'   all rows in `columns` being formatted. Alternatively, we can supply a
+#'   vector of row captions within [c()], a vector of row indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param pattern *Formatting pattern*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A formatting pattern that specifies the arrangement of the `columns` values
+#'   and any string literals. The pattern uses numbers (within `{ }`) that
+#'   correspond to the indices of columns provided in `columns`. If two columns
+#'   are provided in `columns` and we would like to combine the cell data onto
+#'   the first column, `"{1} {2}"` could be used. If a pattern isn't provided
+#'   then a space-separated pattern that includes all `columns` will be
 #'   generated automatically. Further details are provided in the *How the
 #'   `pattern` works* section.
 #'
@@ -1831,33 +1992,59 @@ cols_merge <- function(
 #' in `col_uncert` are hidden from appearing the output table.
 #'
 #' @inheritParams cols_align
-#' @param col_val A single column name that contains the base values. This is
-#'   the column where values will be mutated.
-#' @param col_uncert Either one or two column names that contain the uncertainty
-#'   values. The most common case involves supplying a single column with
-#'   uncertainties; these values will be combined with those in `col_val`. Less
-#'   commonly, lower and upper uncertainty bounds may be different. For that
-#'   case two columns (representing lower and upper uncertainty values away from
-#'   `col_val`, respectively) should be provided. Since we often don't want the
-#'   uncertainty value columns in the output table, we can automatically hide
-#'   any `col_uncert` columns through the `autohide` option.
-#' @param rows Rows that will participate in the merging process. Providing
-#'   [everything()] (the default) results in all rows in `columns` undergoing
-#'   merging. Alternatively, we can supply a vector of row identifiers within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use a standalone predicate expression to filter down to the
-#'   rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
-#' @param sep The separator text that contains the uncertainty mark for a single
+#'
+#' @param col_val *Column to target for base values*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column that contains values for the start of the range. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here.
+#'
+#' @param col_uncert *Column or columns to target for uncertainty values*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The most common case involves supplying a single column with uncertainties;
+#'   these values will be combined with those in `col_val`. Less commonly, the
+#'   lower and upper uncertainty bounds may be different. For that case, two
+#'   columns representing the lower and upper uncertainty values away from
+#'   `col_val`, respectively, should be provided. While select helper functions
+#'   such as [starts_with()] and [ends_with()] can be used for column targeting,
+#'   it's recommended that one or two column names be explicitly provided in a
+#'   vector.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   participate in the merging process. The default [everything()] results in
+#'   all rows in `columns` being formatted. Alternatively, we can supply a
+#'   vector of row captions within [c()], a vector of row indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param sep *Separator text for uncertainties*
+#'
+#'   `scalar<character>` --- *default:* `" +/- "`
+#'
+#'   The separator text that contains the uncertainty mark for a single
 #'   uncertainty value. The default value of `" +/- "` indicates that an
 #'   appropriate plus/minus mark will be used depending on the output context.
 #'   Should you want this special symbol to be taken literally, it can be
 #'   supplied within the [I()] function.
-#' @param autohide An option to automatically hide any columns specified in
-#'   `col_uncert`. Any columns with their state changed to 'hidden' will behave
-#'   the same as before, they just won't be displayed in the finalized table.
-#'   By default, this is set to `TRUE`.
+#'
+#' @param autohide *Automatic hiding of the `col_uncert` column(s)*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to automatically hide any columns specified in `col_uncert`. Any
+#'   columns with their state changed to 'hidden' will behave the same as
+#'   before, they just won't be displayed in the finalized table.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1994,22 +2181,53 @@ cols_merge_uncert <- function(
 #' the output table.
 #'
 #' @inheritParams cols_align
-#' @param col_begin A column that contains values for the start of the range.
-#' @param col_end A column that contains values for the end of the range.
-#' @param rows Rows that will participate in the merging process. Providing
-#'   [everything()] (the default) results in all rows in `columns` undergoing
-#'   merging. Alternatively, we can supply a vector of row identifiers within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use a standalone predicate expression to filter down to the
-#'   rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
-#' @param sep The separator text that indicates the values are ranged. The
-#'   default value of `"--"` indicates that an en dash will be used for the
-#'   range separator. Using `"---"` will be taken to mean that an em dash should
-#'   be used. Should you want these special symbols to be taken literally, they
-#'   can be supplied within the base [I()] function.
-#' @param autohide An option to automatically hide the column specified as
+#'
+#' @param col_begin *Column to target for beginning of range*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column that contains values for the start of the range. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here.
+#'
+#' @param col_end *Column to target for end of range*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column that contains values for the end of the range. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   participate in the merging process. The default [everything()] results in
+#'   all rows in `columns` being formatted. Alternatively, we can supply a
+#'   vector of row captions within [c()], a vector of row indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param sep *Separator text for ranges*
+#'
+#'   `scalar<character>` --- *default:* `"--"`
+#'
+#'   The separator text that indicates the values are ranged. The default value
+#'   of `"--"` will be transformed to an en dash for the range separator. Using
+#'   `"---"` will be taken to mean that an em dash should be used. Should you
+#'   want these special symbols to be taken literally, they can be supplied
+#'   within the base [I()] function.
+#'
+#' @param autohide *Automatic hiding of the `col_end` column*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to automatically hide the column specified as
 #'   `col_end`. Any columns with their state changed to hidden will behave
 #'   the same as before, they just won't be displayed in the finalized table.
 #'
@@ -2171,21 +2389,47 @@ cols_merge_resolver <- function(data, col_begin, col_end, sep) {
 #' specified in `col_pct` is dropped from the output table.
 #'
 #' @inheritParams cols_align
-#' @param col_n A column that contains values for the count component.
-#' @param col_pct A column that contains values for the percentage component.
-#'   This column should be formatted such that percentages are displayed (e.g.,
-#'   with `fmt_percent()`).
-#' @param rows Rows that will participate in the merging process. Providing
-#'   [everything()] (the default) results in all rows in `columns` undergoing
-#'   merging. Alternatively, we can supply a vector of row identifiers within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use a standalone predicate expression to filter down to the
-#'   rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
-#' @param autohide An option to automatically hide the column specified as
-#'   `col_pct`. Any columns with their state changed to hidden will behave
-#'   the same as before, they just won't be displayed in the finalized table.
+#'
+#' @param col_n *Column to target for counts*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column that contains values for the count component. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here.
+#'
+#' @param col_pct *Column to target for percentages*
+#'
+#'   `<column-targeting expression>` --- **required**
+#'
+#'   The column that contains values for the percentage component. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   column targeting, it's recommended that a single column name be used. This
+#'   is to ensure that exactly one column is provided here. This column should
+#'   be formatted such that percentages are displayed (e.g., with
+#'   `fmt_percent()`).
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   participate in the merging process. The default [everything()] results in
+#'   all rows in `columns` being formatted. Alternatively, we can supply a
+#'   vector of row captions within [c()], a vector of row indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param autohide *Automatic hiding of the `col_pct` column*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to automatically hide the column specified as `col_pct`. Any
+#'   columns with their state changed to hidden will behave the same as before,
+#'   they just won't be displayed in the finalized table.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/modify_rows.R b/R/modify_rows.R
index d19e65a25d..704632f140 100644
--- a/R/modify_rows.R
+++ b/R/modify_rows.R
@@ -35,18 +35,23 @@
 #' ordering.
 #'
 #' @inheritParams cols_align
-#' @param groups A character vector of row group ID values corresponding to the
-#'   revised ordering. While this vector must contain valid group ID values, it
-#'   is not required to have all of the row group IDs within it; any omitted
-#'   values will be added to the end while preserving the original ordering.
+#'
+#' @param groups *Specification of row group IDs*
+#'
+#'   `vector<character>` --- **required**
+#'
+#'   A character vector of row group ID values corresponding to the revised
+#'   ordering. While this vector must contain valid group ID values, it is not
+#'   required to have all of the row group IDs within it; any omitted values
+#'   will be added to the end while preserving the original ordering.
 #'
 #' @return An object of class `gt_tbl`.
 #'
 #' @section Examples:
 #'
-#' Use [`exibble`] to create a **gt** table with a stub and with row groups.
-#' Modify the order of the row groups with `row_group_order()`, specifying the
-#' new ordering in `groups`.
+#' Let's use [`exibble`] to create a **gt** table with a stub and with row
+#' groups. We can modify the order of the row groups with `row_group_order()`,
+#' specifying the new ordering in `groups`.
 #'
 #' ```r
 #' exibble |>
diff --git a/R/opts.R b/R/opts.R
index b8e8a9386e..84dc4d4f62 100644
--- a/R/opts.R
+++ b/R/opts.R
@@ -38,12 +38,26 @@
 #' from.
 #'
 #' @inheritParams fmt_number
-#' @param style Six numbered styles are available. Simply provide a number from
-#'   `1` (the default) to `6` to choose a distinct look.
-#' @param color There are six color variations: `"blue"` (the default),
-#'   `"cyan"`, `"pink"`, `"green"`, `"red"`, and `"gray"`.
-#' @param add_row_striping An option to enable row striping in the table body
-#'   for the style chosen. By default, this is `TRUE`.
+#'
+#' @param style *Table style*
+#'
+#'   `scalar<numeric|integer>(1>=val>=6)` --- *default:* `1`
+#'
+#'   Six numbered styles are available. Simply provide a number from `1` (the
+#'   default) to `6` to choose a distinct look.
+#'
+#' @param color *Color variation*
+#'
+#'   `scalar<character>` --- *default:* `"blue"`
+#'
+#'   There are six color variations: `"blue"`, `"cyan"`, `"pink"`, `"green"`,
+#'   `"red"`, and `"gray"`.
+#'
+#' @param add_row_striping *Allow row striping*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to enable row striping in the table body for the `style` chosen.
 #'
 #' @return an object of class `gt_tbl`.
 #'
@@ -208,47 +222,116 @@ get_colorized_params <- function(
 #' - `ihtml.pagination_type`
 #'
 #' @inheritParams fmt_number
-#' @param active The `active` option will either enable or disable interactive
-#'   features for an HTML table. The individual features of an interactive HTML
-#'   table are controlled by the other options.
-#' @param use_pagination This is the option for using pagination controls (below
-#'   the table body). By default, this is `TRUE` and it will allow the use to
-#'   page through table content.
-#' @param use_pagination_info If `use_pagination` is `TRUE` then the
-#'   `use_pagination_info` option can be used to display informational text
-#'   regarding the current page view (this is set to `TRUE` by default).
-#' @param use_sorting This option provides controls for sorting column values.
-#'   By default, this is `TRUE`.
-#' @param use_search The `use_search` option places a search field for globally
-#'   filtering rows to the requested content. By default, this is `FALSE`.
-#' @param use_filters The `use_filters` option places search fields below each
-#'   column header and allows for filtering by column. By default, this is
-#'   `FALSE`.
-#' @param use_resizers This option allows for the interactive resizing of
-#'   columns. By default, this is `FALSE`.
-#' @param use_highlight The `use_highlight` option highlights individual rows
-#'   upon hover. By default, this is `FALSE`.
-#' @param use_compact_mode To reduce vertical padding and thus make the table
-#'   consume less vertical space the `use_compact_mode` option can be used. By
+#'
+#' @param active *Display interactive HTML table*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   The `active` option will either enable or disable interactive features for
+#'   an HTML table. The individual features of an interactive HTML table are
+#'   controlled by the other options.
+#'
+#' @param use_pagination *Display pagination controls*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   This is the option for using pagination controls (below the table body). By
+#'   default, this is `TRUE` and it will allow the use to page through table
+#'   content.
+#'
+#' @param use_pagination_info *Display pagination info*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   If `use_pagination` is `TRUE` then the `use_pagination_info` option can be
+#'   used to display informational text regarding the current page view (this is
+#'   set to `TRUE` by default).
+#'
+#' @param use_sorting *Provide column sorting controls*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   This option provides controls for sorting column values. By default, this
+#'   is `TRUE`.
+#'
+#' @param use_search *Provide a global search field*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   The `use_search` option places a search field for globally filtering rows
+#'   to the requested content. By default, this is `FALSE`.
+#'
+#' @param use_filters *Display filtering fields*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   The `use_filters` option places search fields below each column header and
+#'   allows for filtering by column. By default, this is `FALSE`.
+#'
+#' @param use_resizers *Allow column resizing*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   This option allows for the interactive resizing of columns. By default,
+#'   this is `FALSE`.
+#'
+#' @param use_highlight *Enable row highlighting on hover*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   The `use_highlight` option highlights individual rows upon hover. By
 #'   default, this is `FALSE`.
-#' @param use_text_wrapping The `use_text_wrapping` option controls whether
-#'   text wrapping occurs throughout the table. This is `TRUE` by default and
-#'   with that text will be wrapped to multiple lines. If `FALSE`, text will be
-#'   truncated to a single line.
-#' @param use_page_size_select,page_size_default,page_size_values The
-#'   `use_page_size_select` option lets us display a dropdown menu for the
-#'   number of rows to show per page of data. By default, this is the vector
-#'   `c(10, 25, 50, 100)` which corresponds to options for `10`, `25`, `50`, and
-#'   `100` rows of data per page. To modify these page-size options, provide a
-#'   numeric vector to `page_size_values`. The default page size (initially set
-#'   as `10`) can be modified with `page_size_default` and this works whether or
-#'   not `use_page_size_select` is set to `TRUE`.
-#' @param pagination_type When using pagination the `pagination_type` option
-#'   lets us select between one of three options for the layout of pagination
-#'   controls. The default is `"numbers"`, where a series of page-number buttons
-#'   is presented along with 'previous' and 'next' buttons. The `"jump"` option
-#'   provides an input field with a stepper for the page number. With
-#'   `"simple"`, only the 'previous' and 'next' buttons are displayed.
+#'
+#' @param use_compact_mode *Use compact mode*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   To reduce vertical padding and thus make the table consume less vertical
+#'   space the `use_compact_mode` option can be used. By default, this is
+#'   `FALSE`.
+#'
+#' @param use_text_wrapping *Use text wrapping*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   The `use_text_wrapping` option controls whether text wrapping occurs
+#'   throughout the table. This is `TRUE` by default and with that text will be
+#'   wrapped to multiple lines. If `FALSE`, text will be truncated to a single
+#'   line.
+#'
+#' @param use_page_size_select *Allow for page size selection*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   The `use_page_size_select` option lets us display a dropdown menu for the
+#'   number of rows to show per page of data.
+#'
+#' @param page_size_default *Change the default page size*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `10`
+#'
+#'   The default page size (initially set as `10`) can be modified with
+#'   `page_size_default` and this works whether or not `use_page_size_select` is
+#'   set to `TRUE`.
+#'
+#' @param page_size_values *Set of page-size values*
+#'
+#'   `vector<numeric|integer>` --- *default:* `c(10, 25, 50, 100)`
+#'
+#'   By default, this is the vector `c(10, 25, 50, 100)` which corresponds to
+#'   options for `10`, `25`, `50`, and `100` rows of data per page. To modify
+#'   these page-size options, provide a numeric vector to `page_size_values`.
+#'
+#' @param pagination_type *Change pagination mode*
+#'
+#'   `scalar<character>` --- *default:* `"numbers"`
+#'
+#'   When using pagination the `pagination_type` option lets us select between
+#'   one of three options for the layout of pagination controls. The default is
+#'   `"numbers"`, where a series of page-number buttons is presented along with
+#'   'previous' and 'next' buttons. The `"jump"` option provides an input field
+#'   with a stepper for the page number. With `"simple"`, only the 'previous'
+#'   and 'next' buttons are displayed.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -367,10 +450,15 @@ opt_interactive <- function(
 #' serves as a shortcut for using `tab_options(footnotes.marks = {marks})`
 #'
 #' @inheritParams fmt_number
-#' @param marks Either a character vector of length greater than 1 (that will
-#'   represent the series of marks) or a single keyword that represents a preset
-#'   sequence of marks. The valid keywords are: `"numbers"` (for numeric marks),
-#'   `"letters"` and `"LETTERS"` (for lowercase and uppercase alphabetic marks),
+#'
+#' @param marks *Sequence of footnote marks*
+#'
+#'   `vector<character>` --- *default:* `"numbers"`
+#'
+#'   Either a character vector of length greater than 1 (that will represent the
+#'   series of marks) or a single keyword that represents a preset sequence of
+#'   marks. The valid keywords are: `"numbers"` (for numeric marks), `"letters"`
+#'   and `"LETTERS"` (for lowercase and uppercase alphabetic marks),
 #'   `"standard"` (for a traditional set of four symbol marks), and `"extended"`
 #'   (which adds two more symbols to the standard set).
 #'
@@ -487,10 +575,15 @@ opt_footnote_marks <- function(
 #' `tab_options(footnotes.spec_ftr = {spec})`.
 #'
 #' @inheritParams fmt_number
-#' @param spec_ref,spec_ftr Specification of the footnote marks when behaving as
-#'   footnote references and as marks in the footer section of the table. This
-#'   is a string containing spec characters. The default is the spec string
-#'   `"^i"`, which is superscript text set in italics.
+#'
+#' @param spec_ref,spec_ftr *Specifications for formatting of footnote marks*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Specification of the footnote marks when behaving as footnote references
+#'   and as marks in the footer section of the table. This is a string
+#'   containing spec characters. The default is the spec string `"^i"`, which is
+#'   superscript text set in italics.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -595,8 +688,13 @@ opt_footnote_spec <- function(
 #' `<gt_tbl> |> tab_options(row.striping.include_table_body = TRUE|FALSE)`.
 #'
 #' @inheritParams fmt_number
-#' @param row_striping A logical value to indicate whether row striping should
-#'   be added or removed.
+#'
+#' @param row_striping *Use alternating row stripes*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   A logical value to indicate whether row striping should be added or
+#'   removed.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -668,8 +766,13 @@ opt_row_striping <- function(
 #' convenient shortcut for `<gt_tbl> |> tab_options(heading.align = <align>)`.
 #'
 #' @inheritParams fmt_number
-#' @param align The alignment of the title and subtitle elements in the table
-#' header. Options are `"left"` (the default), `"center"`, or `"right"`.
+#'
+#' @param align *Header alignment*
+#'
+#'   `singl-kw:[left|center|right]` --- *default:* `"left"`
+#'
+#'   The alignment of the title and subtitle elements in the table header.
+#'   Options are `"left"` (the default), `"center"`, or `"right"`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -752,8 +855,13 @@ opt_align_table_header <- function(
 #' - `source_notes.padding`
 #'
 #' @inheritParams fmt_number
-#' @param scale A scale factor by which the vertical padding will be adjusted.
-#'   Must be a number between `0` and `3`.
+#'
+#' @param scale *Scale factor*
+#'
+#'   `scalar<numeric|integer>(0>=val>=3)` --- *default:* `1`
+#'
+#'   A scale factor by which the vertical padding will be adjusted. Must be a
+#'   number between `0` and `3`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -839,8 +947,13 @@ opt_vertical_padding <- function(
 #' - `source_notes.padding.horizontal`
 #'
 #' @inheritParams fmt_number
-#' @param scale A scale factor by which the horizontal padding will be adjusted.
-#'   Must be a number between `0` and `3`.
+#'
+#' @param scale *Scale factor*
+#'
+#'   `scalar<numeric|integer>(0>=val>=3)` --- *default:* `1`
+#'
+#'   A scale factor by which the horizontal padding will be adjusted. Must be a
+#'   number between `0` and `3`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -956,12 +1069,22 @@ get_padding_option_value_list <- function(scale, type) {
 #' pct(80), <location>.font.weight = "bolder")` (for all `locations` selected).
 #'
 #' @inheritParams fmt_number
-#' @param all_caps A logical value to indicate whether the text transformation
-#'   to all caps should be performed (`TRUE`, the default) or reset to default
-#'   values (`FALSE`) for the `locations` targeted.
-#' @param locations Which locations should undergo this text transformation? By
-#'   default it includes all of the `"column_labels"`, the `"stub"`, and the
-#'   `"row_group"` locations. However, we could just choose one or two of those.
+#'
+#' @param all_caps *Use all-caps transformation*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   A logical value to indicate whether the text transformation to all caps
+#'   should be performed (`TRUE`, the default) or reset to default values
+#'   (`FALSE`) for the `locations` targeted.
+#'
+#' @param locations *Locations to target*
+#'
+#'   `mult-kw:[column_labels|stub|row_group]` --- *default:* `c("column_labels", "stub", "row_group")`
+#'
+#'   Which locations should undergo this text transformation? By default it
+#'   includes all of the `"column_labels"`, the `"stub"`, and the `"row_group"`
+#'   locations. However, we could just choose one or two of those.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1067,8 +1190,13 @@ opt_all_caps <- function(
 #' completely lineless table, adding individual lines as needed.
 #'
 #' @inheritParams fmt_number
-#' @param extent The extent to which lines will be visible in the table. Options
-#' are `"all"`, `"none"`, or `"default"`.
+#'
+#' @param extent *Extent of lines added*
+#'
+#'   `singl-kw:[all|none|default]` --- *default:* `"all"`
+#'
+#'   The extent to which lines will be visible in the table. Options are
+#'   `"all"`, `"none"`, or `"default"`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1155,10 +1283,27 @@ opt_table_lines <- function(
 #' will remove any present outline.
 #'
 #' @inheritParams fmt_number
-#' @param style,width,color The style, width, and color properties for the table
-#'   outline. By default, these are `"solid"`, `px(3)` (or, `"3px"`), and
-#'   `"#D3D3D3"`. If `"none"` is used then the outline is removed and any values
-#'   provided for `width` and `color` will be ignored (i.e., not set).
+#'
+#' @param style *Outline style property*
+#'
+#'   `scalar<character>` --- *default:* `"solid"`
+#'
+#'   The style property for the table outline. By default, this is `"solid"`. If
+#'   `"none"` is used then the outline is removed and any values provided for
+#'   `width` and `color` will be ignored (i.e., not set).
+#'
+#' @param width *Outline width value*
+#'
+#'   `scalar<character>` --- *default:* `px(3)`
+#'
+#'   The width property for the table outline. By default, this is `px(3)` (or,
+#'   `"3px"`).
+#'
+#' @param color *Color of outline*
+#'
+#'   `scalar<character>` --- *default:* `"#D3D3D3"`
+#'
+#'   The color of the table outline. By default, this is `"#D3D3D3"`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1279,24 +1424,48 @@ opt_table_outline <- function(
 #' [tab_style_body()] in conjunction with the [cell_text()] helper function.
 #'
 #' @inheritParams fmt_number
-#' @param font One or more font names available as system or web fonts. These
-#'   can be combined with a `c()` or a `list()`. To choose fonts from the
+#'
+#' @param font *Default table fonts*
+#'
+#'   `vector<character>|list|obj:<font_css>` --- *default:* `NULL` (`optional`)
+#'
+#'   One or more font names available as system or web fonts. These can be
+#'   combined with a `c()` or a `list()`. To choose fonts from the
 #'   *Google Fonts* service, we can call the [google_font()] helper function.
-#' @param stack A keyword that represents the name of a font stack (obtained via
-#'   internally via the [system_fonts()] helper function). If provided, this new
-#'   stack will replace any defined fonts and any `font` values will be
-#'   prepended.
-#' @param style An option to modify the text style. Can be one of either
-#'   `"normal"`, `"italic"`, or `"oblique"`.
-#' @param weight Option to set the weight of the font. Can be a text-based
-#'   keyword such as `"normal"`, `"bold"`, `"lighter"`, `"bolder"`, or, a
-#'   numeric value between `1` and `1000`, inclusive. Please note that typefaces
-#'   have varying support for the numeric mapping of weight.
-#' @param add Should this font be added to the beginning of any already-defined
-#'   fonts for the table? By default, this is `TRUE` and is recommended since
-#'   those fonts already present can serve as fallbacks when everything
-#'   specified in `font` is not available. If a `stack` is provided, then `add`
-#'   will automatically set to `FALSE`.
+#'
+#' @param stack *Name of font stack*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A name that is representative of a font stack (obtained via internally via
+#'   the [system_fonts()] helper function). If provided, this new stack will
+#'   replace any defined fonts and any `font` values will be prepended.
+#'
+#' @param style *Text style*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An option to modify the text style. Can be one of either `"normal"`,
+#'   `"italic"`, or `"oblique"`.
+#'
+#' @param weight *Text weight*
+#'
+#'   `scalar<character|numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   Option to set the weight of the font. Can be a text-based keyword such as
+#'   `"normal"`, `"bold"`, `"lighter"`, `"bolder"`, or, a numeric value between
+#'   `1` and `1000`, inclusive. Please note that typefaces have varying support
+#'   for the numeric mapping of weight.
+#'
+#' @param add *Add to existing fonts*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   Should fonts be added to the beginning of any already-defined fonts for the
+#'   table? By default, this is `TRUE` and is recommended since those fonts
+#'   already present can serve as fallbacks when everything specified in `font`
+#'   is not available. If a `stack` is provided, then `add` will automatically
+#'   set to `FALSE`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1487,16 +1656,29 @@ opt_table_font <- function(
 #' as a vector of lines or as a single string.
 #'
 #' @inheritParams fmt_number
-#' @param css The CSS to include as part of the rendered table's `<style>`
-#'   element.
-#' @param add If `TRUE`, the default, the CSS is added to any already-defined
-#'   CSS (typically from previous calls of [opt_table_font()], `opt_css()`, or,
+#'
+#' @param css *CSS declarations*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The CSS to include as part of the rendered table's `<style>` element.
+#'
+#' @param add *Add to existing CSS*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   If `TRUE`, the default, the CSS is added to any already-defined CSS
+#'   (typically from previous calls of [opt_table_font()], `opt_css()`, or,
 #'   directly setting CSS the `table.additional_css` value in [tab_options()]).
 #'   If this is set to `FALSE`, the CSS provided here will replace any
 #'   previously-stored CSS.
-#' @param allow_duplicates When this is `FALSE` (the default), the CSS provided
-#'   here won't be added (provided that `add = TRUE`) if it is seen in the
-#'   already-defined CSS.
+#'
+#' @param allow_duplicates *Allow for CSS duplication*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   When this is `FALSE` (the default), the CSS provided here won't be added
+#'   (provided that `add = TRUE`) if it is seen in the already-defined CSS.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/rows_add.R b/R/rows_add.R
index 9c2e8aaf4c..2451c3a700 100644
--- a/R/rows_add.R
+++ b/R/rows_add.R
@@ -34,29 +34,56 @@
 #' to specify the number of blank (i.e., all `NA`) rows to be inserted into the
 #' table.
 #'
-#' @param .data A table object that is created using the [gt()] function.
-#' @param ... Expressions for the assignment of cell values to the new rows by
-#'   column name in `.data`. Name-value pairs, in the form of `<column> = <value
-#'   vector>` will work, so long as the `<column>` value exists in the table.
-#'   Two-sided formulas with column-resolving expressions (e.g, `<expr> ~ <value
-#'   vector>`) can also be used, where the left-hand side corresponds to
-#'   selections of columns. Column names should be enclosed in [c()] and select
-#'   helpers like [starts_with()], [ends_with()], [contains()], [matches()],
-#'   [one_of()], and [everything()] can be used in the LHS. The length of the
-#'   longest vector in `<value vector>` determines how many new rows will be
-#'   added. Single values in `<value vector>` will be repeated down in cases
-#'   where there are multiple rows to be added.
-#' @param .list Allows for the use of a list as an input alternative to `...`.
-#' @param .before,.after A single row-resolving expression (i.e.,
-#'   **tidyselect**-style expressions like `starts_with()`) or row index can be
-#'   given to either `.before` or `.after`. This specifies where the new rows
-#'   should be positioned among the existing rows in the input data table.
-#'   Importantly, only a single row must be resolved (otherwise, the function
-#'   will be stopped). If nothing is provided for either argument then any new
-#'   rows will be placed at the bottom of the table.
-#' @param .n_empty An option to add empty rows in lieu of rows containing data
-#'   that would otherwise be supplied to `...` or `.list`. If the option is
-#'   taken, provide an integer value here.
+#' @param .data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Cell data assignments*
+#'
+#'   `<multiple expressions>` --- (or, use `.list`)
+#'
+#'   Expressions for the assignment of cell values to the new rows by column
+#'   name in `.data`. Name-value pairs, in the form of
+#'   `<column> = <value vector>` will work, so long as the `<column>` value
+#'   exists in the table. Two-sided formulas with column-resolving expressions
+#'   (e.g, `<expr> ~ <value vector>`) can also be used, where the left-hand side
+#'   corresponds to selections of columns. Column names should be enclosed in
+#'   [c()] and select helpers like [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], and [everything()] can be used in the LHS. The
+#'   length of the longest vector in `<value vector>` determines how many new
+#'   rows will be added. Single values in `<value vector>` will be repeated down
+#'   in cases where there are multiple rows to be added.
+#'
+#' @param .list *Alternative to `...`*
+#'
+#'   `<list of multiple expressions>` --- (or, use `...`)
+#'
+#'   Allows for the use of a list as an input alternative to `...`.
+#'
+#' @param .before,.after *Row used as anchor*
+#'
+#'   `<row-targeting expression>` --- *default:* `NULL` (`optional`)
+#'
+#'   A single row-resolving expression or row index an be given to either
+#'   `.before` or `.after`. The row specifies where the new rows should be
+#'   positioned among the existing rows in the input data table. While select
+#'   helper functions such as [starts_with()] and [ends_with()] can be used for
+#'   row targeting, it's recommended that a single row name or index be used.
+#'   This is to ensure that exactly one row is provided to either of these
+#'   arguments (otherwise, the function will be stopped). If nothing is provided
+#'   for either argument then any new rows will be placed at the bottom of the
+#'   table.
+#'
+#' @param .n_empty *Number of empty rows to add*
+#'
+#'   `scalar<numeric|integer>(val>=0)` --- *default:* `NULL` (`optional`)
+#'
+#'   An option to add empty rows in lieu of rows containing data that would
+#'   otherwise be supplied to `...` or `.list`. If the option is taken, provide
+#'   an integer value here.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/shiny.R b/R/shiny.R
index b83e899714..7212f2eff3 100644
--- a/R/shiny.R
+++ b/R/shiny.R
@@ -41,23 +41,53 @@
 #' is easily by using `install.packages("shiny")`. More information on creating
 #' Shiny apps can be found at the \href{https://shiny.rstudio.com}{Shiny Site}.
 #'
-#' @param expr An expression that creates a **gt** table object. For sake of
-#'   convenience, a data frame or tibble can be used here (it will be
-#'   automatically introduced to [gt()] with its default options).
-#' @param width,height The width and height of the table's container. Either can
-#'   be specified as a single-length character with units of pixels or as a
-#'   percentage. If provided as a single-length numeric vector, it is assumed
-#'   that the value is given in units of pixels. The [px()] and [pct()] helper
-#'   functions can also be used to pass in numeric values and obtain values as
-#'   pixel or percent units.
-#' @param align The alignment of the table in its container. By default, this is
-#'   `"center"`. Other options are `"left"` and `"right"`.
-#' @param env The environment in which to evaluate the `expr`.
-#' @param quoted Is `expr` a quoted expression (with `quote()`)? This is useful
-#'   if you want to save an expression in a variable.
-#' @param outputArgs A list of arguments to be passed through to the implicit
-#'   call to [gt_output()] when `render_gt()` is used in an interactive R
-#'   Markdown document.
+#' @param expr *Expression*
+#'
+#'   `<expression>|obj:<data.frame>|obj:<tbl_df>`
+#'
+#'   An expression that creates a **gt** table object. For sake of convenience,
+#'   a data frame or tibble can be used here (it will be automatically
+#'   introduced to [gt()] with its default options).
+#'
+#' @param width,height *Dimensions of table container*
+#'
+#'   `scalar<numeric|integer|character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The width and height of the table's container. Either can be specified as a
+#'   single-length character vector with units of pixels or as a percentage. If
+#'   provided as a single-length numeric vector, it is assumed that the value is
+#'   given in units of pixels. The [px()] and [pct()] helper functions can also
+#'   be used to pass in numeric values and obtain values as pixel or percent
+#'   units.
+#'
+#' @param align *Table alignment*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The alignment of the table in its container. If `NULL`, the table will be
+#'   center-aligned. Valid options for this are: `"center"`, `"left"`, and
+#'   `"right"`.
+#'
+#' @param env *Evaluation environment*
+#'
+#'   `<environment>` --- *default:* `parent.frame()`
+#'
+#'   The environment in which to evaluate the `expr`.
+#'
+#' @param quoted *Option to `quote()` `expr`*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Is `expr` a quoted expression (with `quote()`)? This is useful if you want
+#'   to save an expression in a variable.
+#'
+#' @param outputArgs *Output arguments*
+#'
+#'   `list` --- *default:* `list()`
+#'
+#'   A list of arguments to be passed through to the implicit call to
+#'   [gt_output()] when `render_gt()` is used in an interactive R Markdown
+#'   document.
 #'
 #' @return An object of class `shiny.render.function`.
 #'
@@ -184,7 +214,11 @@ render_gt <- function(
 #' is easily by using `install.packages("shiny")`. More information on creating
 #' Shiny apps can be found at the \href{https://shiny.rstudio.com}{Shiny Site}.
 #'
-#' @param outputId An output variable from which to read the table.
+#' @param outputId *Shiny output ID*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   An output variable from which to read the table.
 #'
 #' @return An object of class `shiny.tag`.
 #'
@@ -251,4 +285,3 @@ check_shiny <- function() {
 }
 
 #nocov end
-
diff --git a/R/substitution.R b/R/substitution.R
index 219d7606fa..444f18429f 100644
--- a/R/substitution.R
+++ b/R/substitution.R
@@ -32,23 +32,37 @@
 #' `missing_text` argument (where an em dash serves as the default).
 #'
 #' @inheritParams fmt_number
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which substitution operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param missing_text The text to be used in place of `NA` values in the
-#'   rendered table.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param missing_text *Replacement text for `NA` values*
+#'
+#'   `scalar<character>` --- *default:* `"---"`
+#'
+#'   The text to be used in place of `NA` values in the rendered table. We can
+#'   optionally use the [md()] and [html()] functions to style the text as
+#'   Markdown or to retain HTML elements in the text.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -223,23 +237,37 @@ fmt_missing <- function(
 #' replacement through its `zero_text` argument.
 #'
 #' @inheritParams fmt_number
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which substitution operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param zero_text The text to be used in place of zero values in the rendered
-#'   table.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param zero_text *Replacement text for zero values*
+#'
+#'   `scalar<character>` --- *default:* `"nil"`
+#'
+#'   The text to be used in place of zero values in the rendered table. We can
+#'   optionally use the [md()] and [html()] functions to style the text as
+#'   Markdown or to retain HTML elements in the text.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -369,28 +397,51 @@ sub_zero <- function(
 #' to include zero values, use the [sub_zero()] function.
 #'
 #' @inheritParams fmt_number
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which substitution operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param threshold The threshold value with which values should be considered
-#'   small enough for replacement.
-#' @param small_pattern The pattern text to be used in place of the suitably
-#'   small values in the rendered table.
-#' @param sign The sign of the numbers to be considered in the replacement. By
-#'   default, we only consider positive values (`"+"`). The other option (`"-"`)
-#'   can be used to consider only negative values.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param threshold *Threshold value*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `0.01`
+#'
+#'   The threshold value with which values should be considered small enough for
+#'   replacement.
+#'
+#' @param small_pattern *Pattern specification for small values*
+#'
+#'   `scalar<character>` --- *default:* `if (sign == "+") "<{x}" else md("<*abs*(-{x})")`
+#'
+#'   The pattern text to be used in place of the suitably small values in the
+#'   rendered table.
+#'
+#' @param sign *Consider positive or negative values?*
+#'
+#'   `scalar<character>` --- *default:* `"+"`
+#'
+#'   The sign of the numbers to be considered in the replacement. By default, we
+#'   only consider positive values (`"+"`). The other option (`"-"`) can be used
+#'   to consider only negative values.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -621,28 +672,51 @@ sub_small_vals <- function(
 #' considered.
 #'
 #' @inheritParams fmt_number
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which substitution operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param threshold The threshold value with which values should be considered
-#'   large enough for replacement.
-#' @param large_pattern The pattern text to be used in place of the suitably
-#'   large values in the rendered table.
-#' @param sign The sign of the numbers to be considered in the replacement. By
-#'   default, we only consider positive values (`"+"`). The other option (`"-"`)
-#'   can be used to consider only negative values.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param threshold *Threshold value*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `1E12`
+#'
+#'   The threshold value with which values should be considered large enough for
+#'   replacement.
+#'
+#' @param large_pattern *Pattern specification for large values*
+#'
+#'   `scalar<character>` --- *default:* `">={x}"`
+#'
+#'   The pattern text to be used in place of the suitably large values in the
+#'   rendered table.
+#'
+#' @param sign *Consider positive or negative values?*
+#'
+#'   `scalar<character>` --- *default:* `"+"`
+#'
+#'   The sign of the numbers to be considered in the replacement. By default, we
+#'   only consider positive values (`"+"`). The other option (`"-"`) can be used
+#'   to consider only negative values.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -881,40 +955,70 @@ check_sub_fn_sign <- function(sign) {
 #' replacement though value, regex, and custom matching rules.
 #'
 #' @inheritParams fmt_number
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which substitution operations are constrained. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param values The specific value or values that should be replaced with a
-#'   `replacement` value. If `pattern` is also supplied then `values` will be
-#'   ignored.
-#' @param pattern A regex pattern that can target solely those values in
-#'   `character`-based columns. If `values` is also supplied, `pattern` will
-#'   take precedence.
-#' @param fn A supplied function that operates on `x` (the data in a column) and
-#'   should return a logical vector that matches the length of `x` (i.e., number
-#'   of rows in the input table). If either of `values` or `pattern` is also
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param values *Values to match on*
+#'
+#'   `scalar<character|numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   The specific value or values that should be replaced with a `replacement`
+#'   value. If `pattern` is also supplied then `values` will be ignored.
+#'
+#' @param pattern *Regex pattern to match with*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A regex pattern that can target solely those values in `character`-based
+#'   columns. If `values` is also supplied, `pattern` will take precedence.
+#'
+#' @param fn *Function to return logical values*
+#'
+#'   `<function>` --- *default:* `NULL` (`optional`)
+#'
+#'   A supplied function that operates on `x` (the data in a column) and should
+#'   return a logical vector that matches the length of `x` (i.e., number of
+#'   rows in the input table). If either of `values` or `pattern` is also
 #'   supplied, `fn` will take precedence.
-#' @param replacement The replacement value for any cell values matched by
-#'   either `values` or `pattern`. Must be a character or numeric vector of
-#'   length 1.
-#' @param escape An option to escape replacement text according to the final
-#'   output format of the table. For example, if a LaTeX table is to be
-#'   generated then LaTeX escaping would be performed on the replacements during
-#'   rendering. By default this is set to `TRUE` but setting to `FALSE` would be
-#'   useful in the case where replacement text is crafted for a specific output
-#'   format in mind.
+#'
+#' @param replacement *Replacement value for matches*
+#'
+#'   `scalar<character|numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   The replacement value for any cell values matched by either `values` or
+#'   `pattern`. Must be a character or numeric vector of length 1.
+#'
+#' @param escape *Text escaping*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to escape replacement text according to the final output format
+#'   of the table. For example, if a LaTeX table is to be generated then LaTeX
+#'   escaping would be performed on the replacements during rendering. By
+#'   default this is set to `TRUE` but setting to `FALSE` would be useful in the
+#'   case where replacement text is crafted for a specific output format in
+#'   mind.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/summary_rows.R b/R/summary_rows.R
index d6ecd58d6f..698b8545b9 100644
--- a/R/summary_rows.R
+++ b/R/summary_rows.R
@@ -33,42 +33,84 @@
 #' `fmt`.
 #'
 #' @inheritParams fmt_number
-#' @param groups The groups to consider for generation of group-wise summary
-#'   rows. By default this is set to `everything()`, which means that all
-#'   available groups will obtain summary rows. Providing the ID values (in
-#'   quotes) of row groups in `c()` will generate summary rows for those
-#'   specified groups.
-#' @param columns The columns for which the summaries should be calculated. By
-#'   default, this is every column that has data cells (given by
-#'   `everything()`).
-#' @param fns Functions used for aggregations. This can include base functions
-#'   like `mean`, `min`, `max`, `median`, `sd`, or `sum` or any other
-#'   user-defined aggregation function. Multiple functions, each of which would
-#'   generate a different row, are to be supplied within a `list()`. We can
-#'   specify the functions by use of function names in quotes (e.g., `"sum"`),
-#'   as bare functions (e.g., `sum`), or in formula form (e.g.,
-#'   `minimum ~ min(.)`) where the LHS could be used to supply the summary row
-#'   label and id values. More information on this can be found in the
+#'
+#' @param groups *Specification of row group IDs*
+#'
+#'   `<row-group-targeting expression>` --- *default:* `everything()`
+#'
+#'   The row groups to which targeting operations are constrained. Can either be
+#'   a series of row group ID values provided in [c()] or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()]. By default this is set to [everything()], which means that
+#'   all available groups will obtain summary rows.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns for which the summaries should be calculated. Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()].
+#'
+#' @param fns *Aggregation Expressions*
+#'
+#'   `<expression|list of expressions>`
+#'
+#'   Functions used for aggregations. This can include base functions like
+#'   `mean`, `min`, `max`, `median`, `sd`, or `sum` or any other user-defined
+#'   aggregation function. Multiple functions, each of which would generate a
+#'   different row, are to be supplied within a `list()`. We can specify the
+#'   functions by use of function names in quotes (e.g., `"sum"`), as bare
+#'   functions (e.g., `sum`), or in formula form (e.g., `minimum ~ min(.)`)
+#'   where the LHS could be used to supply the summary row label and ID values.
+#'   More information on this can be found in the
 #'   *Aggregation expressions for `fns`* section.
-#' @param fmt Formatting expressions in formula form. The RHS of `~` should
-#'   contain a formatting call (e.g.,
-#'   `~ fmt_number(., decimals = 3, use_seps = FALSE`). Optionally, the LHS
-#'   could contain a group-targeting expression (e.g.,
+#'
+#' @param fmt *Formatting expressions*
+#'
+#'   `<expression|list of expressions>`
+#'
+#'   Formatting expressions in formula form. The RHS of `~` should contain a
+#'   formatting call (e.g., `~ fmt_number(., decimals = 3, use_seps = FALSE`).
+#'   Optionally, the LHS could contain a group-targeting expression (e.g.,
 #'   `"group_a" ~ fmt_number(.)`). More information on this can be found in the
 #'   *Formatting expressions for `fmt`* section.
-#' @param side Should the summary rows be placed at the `"bottom"` (the default)
-#'   or the `"top"` of the row group?
-#' @param missing_text The text to be used in place of `NA` values in summary
-#'   cells with no data outputs.
-#' @param formatter Deprecated, please use `fmt` instead. This was previously
-#'   used as a way to input a formatting function name, which could be any of
-#'   the `fmt_*()` functions available in the package (e.g., [fmt_number()],
-#'   [fmt_percent()], etc.), or a custom function using [fmt()]. The options of
-#'   a formatter can be accessed through `...`.
-#' @param ... Deprecated (along with `formatter`) but otherwise used for
-#'   argument values for a formatting function supplied in `formatter`. For
-#'   example, if using `formatter = fmt_number`, options such as `decimals = 1`,
-#'   `use_seps = FALSE`, and the like can be used here.
+#'
+#' @param side *Side used for placement of summary rows*
+#'
+#'   `singl-kw:[bottom|top]` --- *default:* `"bottom"`
+#'
+#'   Should the summary rows be placed at the `"bottom"` (the default) or the
+#'   `"top"` of the row group?
+#'
+#' @param missing_text *Replacement text for `NA` values*
+#'
+#'   `scalar<character>` --- *default:* `"---"`
+#'
+#'   The text to be used in place of `NA` values in summary cells with no data
+#'   outputs.
+#'
+#' @param formatter *[Deprecated] Formatting function*
+#'
+#'   `<expression>`
+#'
+#'   Deprecated, please use `fmt` instead. This was previously used as a way to
+#'   input a formatting function name, which could be any of the `fmt_*()`
+#'   functions available in the package (e.g., [fmt_number()], [fmt_percent()],
+#'   etc.), or a custom function using [fmt()]. The options of a formatter can
+#'   be accessed through `...`.
+#'
+#' @param ... *[Deprecated] Formatting arguments*
+#'
+#'   `<Named arguments>`
+#'
+#'   Deprecated (along with `formatter`) but otherwise used for argument values
+#'   for a formatting function supplied in `formatter`. For example, if using
+#'   `formatter = fmt_number`, options such as `decimals = 1`, `use_seps =
+#'   FALSE`, and the like can be used here.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -505,8 +547,13 @@ summary_rows <- function(
 #' cells by use of formatting expressions in `fmt`.
 #'
 #' @inheritParams summary_rows
-#' @param side Should the grand summary rows be placed at the `"bottom"` (the
-#'   default) or the `"top"` of the table?
+#'
+#' @param side *Side used for placement of grand summary rows*
+#'
+#'   `singl-kw:[bottom|top]` --- *default:* `"bottom"`
+#'
+#'   Should the grand summary rows be placed at the `"bottom"` (the default) or
+#'   the `"top"` of the table?
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/tab_create_modify.R b/R/tab_create_modify.R
index c980083171..873792140f 100644
--- a/R/tab_create_modify.R
+++ b/R/tab_create_modify.R
@@ -33,11 +33,28 @@
 #' title and subtitle with the [md()] and [html()] helper functions.
 #'
 #' @inheritParams fmt_number
-#' @param title,subtitle Text to be used in the table title and, optionally, for
-#'   the table subtitle. We can elect to use the [md()] and [html()] helper
-#'   functions to style the text as Markdown or to retain HTML elements in the
-#'   text.
-#' @param preheader Optional preheader content that is rendered above the table.
+#'
+#' @param title *Header title*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   Text to be used in the table title. We can elect to use the [md()] and
+#'   [html()] helper functions to style the text as Markdown or to retain HTML
+#'   elements in the text.
+#'
+#' @param subtitle *Header subtitle*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Text to be used in the table subtitle. We can elect to use the [md()] and
+#'   [html()] helper functions to style the text as Markdown or to retain HTML
+#'   elements in the text.
+#'
+#' @param preheader *RTF preheader text*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   Optional preheader content that is rendered above the table for RTF output.
 #'   Can be supplied as a vector of text.
 #'
 #' @return An object of class `gt_tbl`.
@@ -142,7 +159,7 @@ tab_header <- function(
   )
 }
 
-#' Add a spanner column label
+#' Add a spanner label
 #'
 #' @description
 #'
@@ -160,35 +177,72 @@ tab_header <- function(
 #' replacement.
 #'
 #' @inheritParams fmt_number
-#' @param label The text to use for the spanner column label.
-#' @param columns The columns to serve as components of the spanner. Can either
-#'   be a series of column names provided in [c()], a vector of column indices,
-#'   or a helper function focused on selections. The select helper functions
-#'   are: [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'
+#' @param label *Spanner label text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text to use for the spanner label. We can optionally use the [md()] and
+#'   [html()] functions to style the text as Markdown or to retain HTML elements
+#'   in the text.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `NULL` (`optional`)
+#'
+#'   The columns to serve as components of the spanner. Can either be a series
+#'   of column names provided in [c()], a vector of column indices, or a select
+#'   helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
 #'   [num_range()], and [everything()]. This argument works in tandem with the
-#'   `spanner` argument.
-#' @param spanners The spanners that should be spanned over, should they already
-#'   be defined. One or more spanner ID values (in quotes) can be supplied here.
-#'   This argument works in tandem with the `columns` argument.
-#' @param level An explicit level to which the spanner should be placed. If not
-#'   provided, **gt** will choose the level based on the inputs provided within
-#'   `columns` and `spanners`, placing the spanner label where it will fit. The
-#'   first spanner level (right above the column labels) is `1`.
-#' @param id The ID for the spanner column label. When accessing a spanner
-#'   through the `spanners` argument of `tab_spanner()` or
-#'   [cells_column_spanners()] (when using [tab_style()] or [tab_footnote()])
-#'   the `id` value is used as the reference (and not the `label`). If an `id`
-#'   is not explicitly provided here, it will be taken from the `label` value.
-#'   It is advisable to set an explicit `id` value if you plan to access this
-#'   cell in a later function call and the label text is complicated (e.g.,
-#'   contains markup, is lengthy, or both). Finally, when providing an `id`
-#'   value you must ensure that it is unique across all ID values set for column
-#'   spanner labels (the function will stop if `id` isn't unique).
-#' @param gather An option to move the specified `columns` such that they are
-#'   unified under the spanner column label. Ordering of the moved-into-place
-#'   columns will be preserved in all cases. By default, this is set to `TRUE`.
-#' @param replace Should new spanners be allowed to partially or fully replace
-#'   existing spanners? (This is a possibility if setting spanners at an already
+#'   `spanners` argument.
+#'
+#' @param spanners *Spanners to target*
+#'
+#'   `vector<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The spanners that should be spanned over, should they already be defined.
+#'   One or more spanner ID values (in quotes) can be supplied here. This
+#'   argument works in tandem with the `columns` argument.
+#'
+#' @param level *Spanner level for insertion*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   An explicit level to which the spanner should be placed. If not provided,
+#'   **gt** will choose the level based on the inputs provided within `columns`
+#'   and `spanners`, placing the spanner label where it will fit. The first
+#'   spanner level (right above the column labels) is `1`.
+#'
+#' @param id *Spanner ID*
+#'
+#'   `scalar<character>` --- *default:* `label`
+#'
+#'   The ID for the spanner. When accessing a spanner through the `spanners`
+#'   argument of `tab_spanner()` or [cells_column_spanners()] (when using
+#'   [tab_style()] or [tab_footnote()]) the `id` value is used as the reference
+#'   (and not the `label`). If an `id` is not explicitly provided here, it will
+#'   be taken from the `label` value. It is advisable to set an explicit `id`
+#'   value if you plan to access this cell in a later function call and the
+#'   label text is complicated (e.g., contains markup, is lengthy, or both).
+#'   Finally, when providing an `id` value you must ensure that it is unique
+#'   across all ID values set for column spanner labels (the function will stop
+#'   if `id` isn't unique).
+#'
+#' @param gather *Gather columns together*
+#'
+#'   `scalar<logical>` --- *default:* `TRUE`
+#'
+#'   An option to move the specified `columns` such that they are unified under
+#'   the spanner. Ordering of the moved-into-place columns will be preserved in
+#'   all cases. By default, this is set to `TRUE`.
+#'
+#' @param replace *Replace existing spanners*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should new spanners be allowed to partially or fully replace existing
+#'   spanners? (This is a possibility if setting spanners at an already
 #'   populated `level`.) By default, this is set to `FALSE` and an error will
 #'   occur if some replacement is attempted.
 #'
@@ -530,7 +584,7 @@ tab_spanner <- function(
   }
 
   # Check new `id` against existing `id` values across column labels
-  # and spanner column labels and stop if necessary
+  # and spanner labels and stop if necessary
   check_spanner_id_unique(data = data, spanner_id = id)
 
   # Resolve the `column_names` that new spanner will span over
@@ -653,7 +707,7 @@ resolve_spanned_column_names <- function(
 #' @description
 #'
 #' The `cols_spanner_delim()` function can take specially-crafted column names
-#' and generate one or more spanner column labels (along with relabeling the
+#' and generate one or more spanners (along with relabeling the
 #' column labels). This is done by splitting the column name by a specified
 #' delimiter character (this is the `delim`) and placing the fragments from top
 #' to bottom (i.e., higher-level spanners to the column labels). Furthermore,
@@ -677,31 +731,54 @@ resolve_spanned_column_names <- function(
 #' expressions
 #'
 #' @inheritParams tab_spanner
-#' @param delim The delimiter to use to split an input column name. This should
-#'   be a single character (e.g., `"_"`, `"."`, etc.).
-#' @param columns The columns to consider for the splitting, relabeling, and
-#'   spanner setting operations. This can either be a series of column names
-#'   provided in [c()], a vector of column indices, or a helper function
-#'   focused on selections. The select helper functions are: [starts_with()],
-#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
-#'   [everything()]. By default, we consider all columns in the table through
-#'   the use of [everything()].
-#' @param split Should the delimiter splitting occur from the `"last"` instance
-#'   of the `delim` character or from the `"first"`? The default here uses the
-#'   `"last"` keyword, and splitting begins at the last instance of the
-#'   delimiter in the column name. This option only has some consequence when
-#'   there is a `limit` value applied that is lesser than the number of
-#'   delimiter characters for a given column name (i.e., number of splits is not
-#'   the maximum possible number).
-#' @param limit An optional limit to place on the splitting procedure. The
-#'   default `NULL` means that a column name will be split as many times are
-#'   there are delimiter characters. In other words, the default is no limit. If
-#'   an integer value is given to `limit` then splitting will cease at the
+#'
+#' @param delim *Delimiter for splitting*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The delimiter to use to split an input column name. This should be a single
+#'   character (e.g., `"_"`, `"."`, etc.).
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to consider for the splitting, relabeling, and spanner setting
+#'   operations. Can either be a series of column names provided in [c()], a
+#'   vector of column indices, or a select helper function. Examples of select
+#'   helper functions include [starts_with()], [ends_with()], [contains()],
+#'   [matches()], [one_of()], [num_range()], and [everything()]. This argument
+#'   works in tandem with the `spanners` argument.
+#'
+#' @param split *Splitting side*
+#'
+#'   `singl-kw:[last|first]` --- *default:* `"last"`
+#'
+#'   Should the delimiter splitting occur from the `"last"` instance of the
+#'   `delim` character or from the `"first"`? The default here uses the `"last"`
+#'   keyword, and splitting begins at the last instance of the delimiter in the
+#'   column name. This option only has some consequence when there is a `limit`
+#'   value applied that is lesser than the number of delimiter characters for a
+#'   given column name (i.e., number of splits is not the maximum possible
+#'   number).
+#'
+#' @param limit *Limit for splitting*
+#'
+#'   `scalar<numeric|integer|character>` --- *default:* `NULL` (`optional`)
+#'
+#'   An optional limit to place on the splitting procedure. The default `NULL`
+#'   means that a column name will be split as many times are there are
+#'   delimiter characters. In other words, the default means there is no limit.
+#'   If an integer value is given to `limit` then splitting will cease at the
 #'   iteration given by `limit`. This works in tandem with `split` since we can
 #'   adjust the number of splits from either the right side (`split = "last"`)
 #'   or left side (`split = "first"`) of the column name.
-#' @param reverse Should the order of split names be reversed? By default, this
-#'   is `FALSE`.
+#'
+#' @param reverse *Reverse vector of split names*
+#'
+#'   `scalar<logical>` --- *default:* `FALSE`
+#'
+#'   Should the order of split names be reversed? By default, this is `FALSE`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -713,7 +790,7 @@ resolve_spanned_column_names <- function(
 #' well-defined structure. We start with the more general to the left
 #' (`"province"`) and move to the more specific on the right (`"pop"`). If the
 #' columns are in the table in this exact order, then things are in an ideal
-#' state as the eventual spanner column labels will form from this neighboring.
+#' state as the eventual spanner labels will form from this neighboring.
 #' When using `tab_spanner_delim()` here with `delim` set as `"."` we get the
 #' following text fragments:
 #'
@@ -902,7 +979,7 @@ resolve_spanned_column_names <- function(
 #' `v0.2.0.5` (March 31, 2020)
 #'
 #' @seealso [tab_spanner()] to manually create spanners with more control over
-#'   spanner column labels.
+#'   spanner labels.
 #'
 #' @import rlang
 #' @export
@@ -1260,13 +1337,32 @@ str_split_across <- function(
 #' `tab_options(row_group.default_label = "")` can be used.
 #'
 #' @inheritParams fmt_number
-#' @param label The text to use for the row group label.
-#' @param rows The rows to be made components of the row group. Can either be a
-#'   vector of row captions provided in `c()`, a vector of row indices, or a
-#'   helper function focused on selections. The select helper functions are:
-#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()], and
-#'   [everything()].
-#' @param id The ID for the row group. When accessing a row group through
+#'
+#' @param label *Row group label text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text to use for the row group label. We can optionally use the [md()]
+#'   and [html()] functions to style the text as Markdown or to retain HTML
+#'   elements in the text.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- **required**
+#'
+#'   The rows to be made components of the row group. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param id *Row group ID*
+#'
+#'   `scalar<character>` --- *default:* `label`
+#'
+#'   The ID for the row group. When accessing a row group through
 #'   [cells_row_groups()] (when using [tab_style()] or [tab_footnote()]) the
 #'   `id` value is used as the reference (and not the `label`). If an `id` is
 #'   not explicitly provided here, it will be taken from the `label` value. It
@@ -1275,9 +1371,19 @@ str_split_across <- function(
 #'   markup, is lengthy, or both). Finally, when providing an `id` value you
 #'   must ensure that it is unique across all ID values set for row groups (the
 #'   function will stop if `id` isn't unique).
-#' @param others_label This argument is deprecated. Instead use
+#'
+#' @param others_label *[Deprecated] Label for default row group*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   This argument is deprecated. Instead use
 #'   `tab_options(row_group.default_label = <label>)`.
-#' @param group This argument is deprecated. Instead use `label`.
+#'
+#' @param group *[Deprecated] The group label*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   This argument is deprecated. Instead use `label`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1544,9 +1650,14 @@ tab_row_group <- function(
 #' of [html()] for the stubhead label.
 #'
 #' @inheritParams fmt_number
-#' @param label The text to be used as the stubhead label. We can optionally use
-#'   the [md()] and [html()] functions to style the text as Markdown or to
-#'   retain HTML elements in the text.
+#'
+#' @param label *Stubhead label text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text to be used as the stubhead label. We can optionally use the [md()]
+#'   and [html()] functions to style the text as Markdown or to retain HTML
+#'   elements in the text.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1615,18 +1726,29 @@ tab_stubhead <- function(
 #' indentation level, or, employ an indentation directive using keywords.
 #'
 #' @inheritParams fmt_number
-#' @param rows The rows to consider for the indentation change. Can either be a
-#'   vector of row captions provided in `c()`, a vector of row indices, or a
-#'   helper function focused on selections. The select helper functions are:
-#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()], and
-#'   [everything()].
-#' @param indent An indentation directive either as a keyword describing the
-#'   indentation change or as an explicit integer value for directly setting the
-#'   indentation level. The keyword `"increase"` (the default) will increase the
-#'   indentation level by one; `"decrease"` will do the same in the reverse
-#'   direction. The starting indentation level of `0` means no indentation and
-#'   this values serves as a lower bound. The upper bound for indentation is at
-#'   level `5`.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- **required**
+#'
+#'   The rows to consider for the indentation change. The default [everything()]
+#'   results in all rows being targeted. Alternatively, we can supply a vector
+#'   of row captions within [c()], a vector of row indices, or a select helper
+#'   function. Examples of select helper functions include [starts_with()],
+#'   [ends_with()], [contains()], [matches()], [one_of()], [num_range()], and
+#'   [everything()]. We can also use expressions to filter down to the rows we
+#'   need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param indent *Indentation directive*
+#'
+#'   `scalar<character|numeric|integer>` --- *default:* `"increase"`
+#'
+#'   An indentation directive either as a keyword describing the indentation
+#'   change or as an explicit integer value for directly setting the indentation
+#'   level. The keyword `"increase"` (the default) will increase the indentation
+#'   level by one; `"decrease"` will do the same in the reverse direction. The
+#'   starting indentation level of `0` means no indentation and this values
+#'   serves as a lower bound. The upper bound for indentation is at level `5`.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -1789,24 +1911,39 @@ tab_stub_indent <- function(
 #' placement of the footnote mark.
 #'
 #' @inheritParams fmt_number
-#' @param footnote The text to be used in the footnote. We can optionally use
-#'   the [md()] and [html()] functions to style the text as Markdown or to
-#'   retain HTML elements in the footnote text.
-#' @param locations The cell or set of cells to be associated with the footnote.
-#'   Supplying any of the `cells_*()` helper functions is a useful way to target
-#'   the location cells that are associated with the footnote text. These helper
-#'   functions are: [cells_title()], [cells_stubhead()],
-#'   [cells_column_spanners()], [cells_column_labels()], [cells_row_groups()],
-#'   [cells_stub()], [cells_body()], [cells_summary()], [cells_grand_summary()],
+#'
+#' @param footnote *Footnote text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The text to be used in the footnote. We can optionally use the [md()] and
+#'   [html()] functions to style the text as Markdown or to retain HTML elements
+#'   in the footnote text.
+#'
+#' @param locations *Locations to target*
+#'
+#'   `<locations expressions>` --- *default:* `NULL` (`optional`)
+#'
+#'   The cell or set of cells to be associated with the footnote. Supplying any
+#'   of the `cells_*()` helper functions is a useful way to target the location
+#'   cells that are associated with the footnote text. These helper functions
+#'   are: [cells_title()], [cells_stubhead()], [cells_column_spanners()],
+#'   [cells_column_labels()], [cells_row_groups()], [cells_stub()],
+#'   [cells_body()], [cells_summary()], [cells_grand_summary()],
 #'   [cells_stub_summary()], and [cells_stub_grand_summary()]. Additionally, we
 #'   can enclose several `cells_*()` calls within a `list()` if we wish to link
 #'   the footnote text to different types of locations (e.g., body cells, row
 #'   group labels, the table title, etc.).
-#' @param placement Where to affix footnote marks to the table content. Two
-#'   options for this are `"left` or `"right"`, where the placement is either to
-#'   the absolute left or right of the cell content. By default, however, this
-#'   option is set to `"auto"` whereby **gt** will choose a preferred
-#'   left-or-right placement depending on the alignment of the cell content.
+#'
+#' @param placement *Placement of footnote mark*
+#'
+#'   `singl-kw:[auto|right|left]` --- *default:* `"auto"`
+#'
+#'   Where to affix footnote marks to the table content. Two options for this
+#'   are `"left` or `"right"`, where the placement is either to the absolute
+#'   left or right of the cell content. By default, however, this option is set
+#'   to `"auto"` whereby **gt** will choose a preferred left-or-right placement
+#'   depending on the alignment of the cell content.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2432,9 +2569,14 @@ set_footnote.cells_footnotes <- function(
 #' or, if the table is intended for HTML output, we can include HTML formatting.
 #'
 #' @inheritParams fmt_number
-#' @param source_note Text to be used in the source note. We can optionally use
-#'   the [md()] and [html()] functions to style the text as Markdown or to
-#'   retain HTML elements in the text.
+#'
+#' @param source_note *Source note text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   Text to be used in the source note. We can optionally use the [md()] and
+#'   [html()] functions to style the text as Markdown or to retain HTML elements
+#'   in the text.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2490,8 +2632,13 @@ tab_source_note <- function(
 #' in each of these system.
 #'
 #' @inheritParams fmt_number
-#' @param caption The table caption to use for cross-referencing in R Markdown,
-#'   Quarto, or **bookdown**.
+#'
+#' @param caption *Table caption text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The table caption to use for cross-referencing in R Markdown, Quarto, or
+#'   **bookdown**.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -2563,18 +2710,28 @@ tab_caption <- function(
 #' - the cell borders ([cell_borders()])
 #'
 #' @inheritParams fmt_number
-#' @param style The styles to use for the cells at the targeted `locations`. The
+#'
+#' @param style *Style declarations*
+#'
+#'   `<style expressions>` --- **required**
+#'
+#'   The styles to use for the cells at the targeted `locations`. The
 #'   [cell_text()], [cell_fill()], and [cell_borders()] helper functions can be
 #'   used here to more easily generate valid styles. If using more than one
 #'   helper function to define styles, all calls must be enclosed in a [list()].
 #'   Custom CSS declarations can be used for HTML output by including a
 #'   [css()]-based statement as a list item.
-#' @param locations the cell or set of cells to be associated with the style.
-#'   Supplying any of the `cells_*()` helper functions is a useful way to target
-#'   the location cells that are associated with the styling. These helper
-#'   functions are: [cells_title()], [cells_stubhead()],
-#'   [cells_column_spanners()], [cells_column_labels()], [cells_row_groups()],
-#'   [cells_stub()], [cells_body()], [cells_summary()], [cells_grand_summary()],
+#'
+#' @param locations *Locations to target*
+#'
+#'   `<locations expressions>` --- **required**
+#'
+#'   The cell or set of cells to be associated with the style. Supplying any of
+#'   the `cells_*()` helper functions is a useful way to target the location
+#'   cells that are associated with the styling. These helper functions are:
+#'   [cells_title()], [cells_stubhead()], [cells_column_spanners()],
+#'   [cells_column_labels()], [cells_row_groups()], [cells_stub()],
+#'   [cells_body()], [cells_summary()], [cells_grand_summary()],
 #'   [cells_stub_summary()], [cells_stub_grand_summary()], [cells_footnotes()],
 #'   and [cells_source_notes()]. Additionally, we can enclose several
 #'   `cells_*()` calls within a `list()` if we wish to apply styling to
@@ -3149,47 +3306,76 @@ set_style.cells_source_notes <- function(loc, data, style) {
 #' components, the subcomponents, and the element that can adjusted.
 #'
 #' @inheritParams fmt_number
-#' @param table.width The width of the table. Can be specified as a
-#'   single-length character with units of pixels or as a percentage. If
-#'   provided as a single-length numeric vector, it is assumed that the value is
-#'   given in units of pixels. The [px()] and [pct()] helper functions can also
-#'   be used to pass in numeric values and obtain values as pixel or percent
-#'   units.
-#' @param table.layout The value for the `table-layout` CSS style in the HTML
-#'   output context. By default, this is `"fixed"` but another valid option is
+#'
+#' @param table.width *Table width*
+#'
+#'   The table width can be specified as a single-length character with units of
+#'   pixels or as a percentage. If provided as a single-length numeric vector,
+#'   it is assumed that the value is given in units of pixels. The [px()] and
+#'   [pct()] helper functions can also be used to pass in numeric values and
+#'   obtain values as pixel or percent units.
+#'
+#' @param table.layout *The table-layout property*
+#'
+#'   This is the value for the `table-layout` CSS style in the HTML output
+#'   context. By default, this is `"fixed"` but another valid option is
 #'   `"auto"`.
-#' @param table.align The horizontal alignment of the table in its container. By
-#'   default, this is `"center"`. Other options are `"left"` and `"right"`. This
-#'   will automatically set `table.margin.left` and `table.margin.right` to the
-#'   appropriate values.
-#' @param table.margin.left,table.margin.right The size of the margins on the
-#'   left and right of the table within the container. Can be specified as a
-#'   single-length character with units of pixels or as a percentage. If
-#'   provided as a single-length numeric vector, it is assumed that the value is
-#'   given in units of pixels. The [px()] and [pct()] helper functions can also
-#'   be used to pass in numeric values and obtain values as pixel or percent
-#'   units. Using `table.margin.left` or `table.margin.right` will overwrite any
-#'   values set by `table.align`.
+#'
+#' @param table.align *Horizontal alignment of table*
+#'
+#'   The `table.align` option lets us set the horizontal alignment of the table
+#'   in its container. By default, this is `"center"`. Other options are
+#'   `"left"` and `"right"`. This will automatically set `table.margin.left` and
+#'   `table.margin.right` to the appropriate values.
+#'
+#' @param table.margin.left,table.margin.right *Left and right table margins*
+#'
+#'   The size of the margins on the left and right of the table within the
+#'   container can be set with `table.margin.left` and `table.margin.right`. Can
+#'   be specified as a single-length character with units of pixels or as a
+#'   percentage. If provided as a single-length numeric vector, it is assumed
+#'   that the value is given in units of pixels. The [px()] and [pct()] helper
+#'   functions can also be used to pass in numeric values and obtain values as
+#'   pixel or percent units. Using `table.margin.left` or `table.margin.right`
+#'   will overwrite any values set by `table.align`.
+#'
 #' @param table.background.color,heading.background.color,column_labels.background.color,row_group.background.color,stub.background.color,summary_row.background.color,grand_summary_row.background.color,footnotes.background.color,source_notes.background.color
-#'   Background colors for the parent element `table` and the following child
-#'   elements: `heading`, `column_labels`, `row_group`, `stub`, `summary_row`,
-#'   `grand_summary_row`, `footnotes`, and `source_notes`. A color name or a
-#'   hexadecimal color code should be provided.
-#' @param table.additional_css This option can be used to supply an additional
-#'   block of CSS rules to be applied after the automatically generated table
-#'   CSS.
-#' @param table.font.names The names of the fonts used for the table. This is
-#'   a vector of several font names. If the first font isn't available, then
-#'   the next font is tried (and so on).
-#' @param table.font.style The font style for the table. Can be one of either
+#'   *Background colors*
+#'
+#'   These options govern background colors for the parent element `table` and
+#'   the following child elements: `heading`, `column_labels`, `row_group`,
+#'   `stub`, `summary_row`, `grand_summary_row`, `footnotes`, and
+#'   `source_notes`. A color name or a hexadecimal color code should be
+#'   provided.
+#'
+#' @param table.additional_css *Additional CSS*
+#'
+#'   The `table.additional_css` option can be used to supply an additional block
+#'   of CSS rules to be applied after the automatically generated table CSS.
+#'
+#' @param table.font.names *Default table fonts*
+#'
+#'   The names of the fonts used for the table can be supplied through
+#'   `table.font.names`. This is a vector of several font names. If the first
+#'   font isn't available, then the next font is tried (and so on).
+#'
+#' @param table.font.style *Default table font style*
+#'
+#'   This is the default font style for the table. Can be one of either
 #'   `"normal"`, `"italic"`, or `"oblique"`.
+#'
 #' @param table.font.color,table.font.color.light
-#'   The text color used throughout the table. There are two variants:
-#'   `table.font.color` is for text overlaid on lighter background colors, and
-#'   `table.font.color.light` is automatically used when text needs to be
-#'   overlaid on darker background colors. A color name or a hexadecimal color
-#'   code should be provided.
+#'   *Default dark and light text for the table*
+#'
+#'   These options define text colors used throughout the table. There are two
+#'   variants: `table.font.color` is for text overlaid on lighter background
+#'   colors, and `table.font.color.light` is automatically used when text needs
+#'   to be overlaid on darker background colors. A color name or a hexadecimal
+#'   color code should be provided.
+#'
 #' @param table.font.size,heading.title.font.size,heading.subtitle.font.size,column_labels.font.size,row_group.font.size,stub.font.size,footnotes.font.size,source_notes.font.size
+#'   *Table font sizes*
+#'
 #'   The font sizes for the parent text element `table` and the following child
 #'   elements: `heading.title`, `heading.subtitle`, `column_labels`,
 #'   `row_group`, `footnotes`, and `source_notes`. Can be specified as a
@@ -3198,26 +3384,41 @@ set_style.cells_source_notes <- function(loc, data, style) {
 #'   it is assumed that the value is given in units of pixels. The [px()] and
 #'   [pct()] helper functions can also be used to pass in numeric values and
 #'   obtain values as pixel or percentage units.
-#' @param heading.align Controls the horizontal alignment of the heading title
-#'   and subtitle. We can either use `"center"`, `"left"`, or `"right"`.
+#'
+#' @param heading.align *Horizontal alignment in the table header*
+#'
+#'   Controls the horizontal alignment of the heading title and subtitle. We can
+#'   either use `"center"`, `"left"`, or `"right"`.
+#'
 #' @param table.font.weight,heading.title.font.weight,heading.subtitle.font.weight,column_labels.font.weight,row_group.font.weight,stub.font.weight
+#'   *Table font weights*
+#'
 #'   The font weights of the table, `heading.title`, `heading.subtitle`,
 #'   `column_labels`, `row_group`, and `stub` text elements. Can be a text-based
 #'   keyword such as `"normal"`, `"bold"`, `"lighter"`, `"bolder"`, or, a
 #'   numeric value between `1` and `1000`, inclusive. Note that only variable
 #'   fonts may support the numeric mapping of weight.
+#'
 #' @param column_labels.text_transform,row_group.text_transform,stub.text_transform,summary_row.text_transform,grand_summary_row.text_transform
+#'   *Text transforms throughout the table*
+#'
 #'   Options to apply text transformations to the `column_labels`, `row_group`,
 #'   `stub`, `summary_row`, and `grand_summary_row` text elements. Either of the
 #'   `"uppercase"`, `"lowercase"`, or `"capitalize"` keywords can be used.
+#'
 #' @param heading.padding,column_labels.padding,data_row.padding,row_group.padding,summary_row.padding,grand_summary_row.padding,footnotes.padding,source_notes.padding
+#'   *Vertical padding throughout the table*
+#'
 #'   The amount of vertical padding to incorporate in the `heading` (title and
 #'   subtitle), the `column_labels` (this includes the column spanners), the row
 #'   group labels (`row_group.padding`), in the body/stub rows
 #'   (`data_row.padding`), in summary rows (`summary_row.padding` or
 #'   `grand_summary_row.padding`), or in the footnotes and source notes
 #'   (`footnotes.padding` and `source_notes.padding`).
+#'
 #' @param heading.padding.horizontal,column_labels.padding.horizontal,data_row.padding.horizontal,row_group.padding.horizontal,summary_row.padding.horizontal,grand_summary_row.padding.horizontal,footnotes.padding.horizontal,source_notes.padding.horizontal
+#'   *Horizontal padding throughout the table*
+#'
 #'   The amount of horizontal padding to incorporate in the `heading` (title and
 #'   subtitle), the `column_labels` (this includes the column spanners), the row
 #'   group labels (`row_group.padding.horizontal`), in the body/stub rows
@@ -3225,115 +3426,203 @@ set_style.cells_source_notes <- function(loc, data, style) {
 #'   `grand_summary_row.padding.horizontal`), or in the footnotes and source
 #'   notes (`footnotes.padding.horizontal` and
 #'   `source_notes.padding.horizontal`).
+#'
 #' @param table.border.top.style,table.border.top.width,table.border.top.color,table.border.right.style,table.border.right.width,table.border.right.color,table.border.bottom.style,table.border.bottom.width,table.border.bottom.color,table.border.left.style,table.border.left.width,table.border.left.color
+#'   *Top border properties*
+#'
 #'   The style, width, and color properties of the table's absolute top and
 #'   absolute bottom borders.
+#'
 #' @param heading.border.bottom.style,heading.border.bottom.width,heading.border.bottom.color
+#'   *Properties of the header's bottom border*
+#'
 #'   The style, width, and color properties of the header's bottom border. This
 #'   border shares space with that of the `column_labels` location. If the
 #'   `width` of this border is larger, then it will be the visible border.
+#'
 #' @param heading.border.lr.style,heading.border.lr.width,heading.border.lr.color
+#'   *Properties of the header's left and right borders*
+#'
 #'   The style, width, and color properties for the left and right borders of
 #'   the `heading` location.
+#'
 #' @param column_labels.vlines.style,column_labels.vlines.width,column_labels.vlines.color
+#'   *Properties of all vertical lines by the column labels*
+#'
 #'   The style, width, and color properties for all vertical lines ('vlines')
 #'   of the the `column_labels`.
+#'
 #' @param column_labels.border.top.style,column_labels.border.top.width,column_labels.border.top.color
+#'   *Properties of the border above the column labels*
+#'
 #'   The style, width, and color properties for the top border of the
 #'   `column_labels` location. This border shares space with that of the
 #'   `heading` location. If the `width` of this border is larger, then it will
 #'   be the visible border.
+#'
 #' @param column_labels.border.bottom.style,column_labels.border.bottom.width,column_labels.border.bottom.color
+#'   *Properties of the border below the column labels*
+#'
 #'   The style, width, and color properties for the bottom border of the
 #'   `column_labels` location.
+#'
 #' @param column_labels.border.lr.style,column_labels.border.lr.width,column_labels.border.lr.color
+#'   *Properties of the left and right borders next to the column labels*
+#'
 #'   The style, width, and color properties for the left and right borders of
 #'   the `column_labels` location.
-#' @param column_labels.hidden An option to hide the column labels. If providing
-#'   `TRUE` then the entire `column_labels` location won't be seen and the table
-#'   header (if present) will collapse downward.
+#'
+#' @param column_labels.hidden *Hiding all column labels*
+#'
+#'   An option to hide the column labels. If providing `TRUE` then the entire
+#'   `column_labels` location won't be seen and the table header (if present)
+#'   will collapse downward.
+#'
 #' @param row_group.border.top.style,row_group.border.top.width,row_group.border.top.color,row_group.border.bottom.style,row_group.border.bottom.width,row_group.border.bottom.color,row_group.border.left.style,row_group.border.left.width,row_group.border.left.color,row_group.border.right.style,row_group.border.right.width,row_group.border.right.color
+#'   *Border properties associated with the `row_group` location*
+#'
 #'   The style, width, and color properties for all top, bottom, left, and right
 #'   borders of the `row_group` location.
+#'
 #' @param table_body.hlines.style,table_body.hlines.width,table_body.hlines.color,table_body.vlines.style,table_body.vlines.width,table_body.vlines.color
+#'   *Properties of all horizontal and vertical lines in the table body*
+#'
 #'   The style, width, and color properties for all horizontal lines ('hlines')
 #'   and vertical lines ('vlines') in the `table_body`.
+#'
 #' @param table_body.border.top.style,table_body.border.top.width,table_body.border.top.color,table_body.border.bottom.style,table_body.border.bottom.width,table_body.border.bottom.color
+#'   *Properties of top and bottom borders in the table body*
+#'
 #'   The style, width, and color properties for all top and bottom borders of
 #'   the `table_body` location.
+#'
 #' @param stub.border.style,stub.border.width,stub.border.color
+#'   *Properties of the vertical border of the table stub*
+#'
 #'   The style, width, and color properties for the vertical border of the table
 #'   stub.
+#'
 #' @param stub_row_group.font.size,stub_row_group.font.weight,stub_row_group.text_transform,stub_row_group.border.style,stub_row_group.border.width,stub_row_group.border.color
-#'   Options for the row group column in the stub (made possible when using
-#'   `row_group.as_column = TRUE`). The defaults for these options mirror that
-#'   of the `stub.*` variants (except for `stub_row_group.border.width`, which
-#'   is `"1px"` instead of `"2px"`).
-#' @param row_group.default_label An option to set a default row group label for
-#'   any rows not formally placed in a row group named by `group` in any call of
-#'   `tab_row_group()`. If this is set as `NA_character` and there are rows that
-#'   haven't been placed into a row group (where one or more row groups already
-#'   exist), those rows will be automatically placed into a row group without a
-#'   label.
-#' @param row_group.as_column How should row groups be structured? By default,
-#'   they are separate rows that lie above the each of the groups. Setting this
-#'   to `TRUE` will structure row group labels are columns to the far left of
-#'   the table.
-#' @param stub.indent_length The width of each indentation level. By default
-#'   this is `"5px"`.
+#'   *Properties of the row group column in the table stub*
+#'
+#'   Options for the row group column in the table stub (made possible when
+#'   using `row_group.as_column = TRUE`). The defaults for these options mirror
+#'   that of the `stub.*` variants (except for `stub_row_group.border.width`,
+#'   which is `"1px"` instead of `"2px"`).
+#'
+#' @param row_group.default_label *The default row group label*
+#'
+#'   An option to set a default row group label for any rows not formally placed
+#'   in a row group named by `group` in any call of [tab_row_group()]. If this
+#'   is set as `NA_character_` and there are rows that haven't been placed into a
+#'   row group (where one or more row groups already exist), those rows will be
+#'   automatically placed into a row group without a label.
+#'
+#' @param row_group.as_column *Structure row groups with a column*
+#'
+#'   How should row groups be structured? By default, they are separate rows
+#'   that lie above the each of the groups. Setting this to `TRUE` will
+#'   structure row group labels as a separate column in the table stub.
+#'
+#' @param stub.indent_length *Width of each indentation*
+#'
+#'   The width of each indentation level for row labels in the stub. The
+#'   indentation can be set by using [tab_stub_indent()]. By default this is
+#'   `"5px"`.
+#'
 #' @param summary_row.border.style,summary_row.border.width,summary_row.border.color
+#'   *Properties of horizontal borders belonging to summary rows*
+#'
 #'   The style, width, and color properties for all horizontal borders of the
 #'   `summary_row` location.
+#'
 #' @param grand_summary_row.border.style,grand_summary_row.border.width,grand_summary_row.border.color
+#'   *Properties of horizontal borders belonging to grand summary rows*
+#'
 #'   The style, width, and color properties for the top borders of the
 #'   `grand_summary_row` location.
+#'
 #' @param footnotes.border.bottom.style,footnotes.border.bottom.width,footnotes.border.bottom.color
+#'   *Properties of the bottom border belonging to the footnotes*
+#'
 #'   The style, width, and color properties for the bottom border of the
 #'   `footnotes` location.
+#'
 #' @param footnotes.border.lr.style,footnotes.border.lr.width,footnotes.border.lr.color
+#'   *Properties of left and right borders belonging to the footnotes*
+#'
 #'   The style, width, and color properties for the left and right borders of
 #'   the `footnotes` location.
-#' @param footnotes.marks The set of sequential marks used to reference and
-#'   identify each of the footnotes (same input as the [opt_footnote_marks()]
-#'   function). We can supply a vector that represents the series of footnote
-#'   marks. This vector is recycled when its usage goes beyond the length of the
-#'   set. At each cycle, the marks are simply combined (e.g., `*` -> `**` ->
-#'   `***`). The option exists for providing keywords for certain types of
-#'   footnote marks. The keyword `"numbers"` (the default, indicating that we
-#'   want to use numeric marks). We can use lowercase `"letters"` or uppercase
-#'   `"LETTERS"`. There is the option for using a traditional symbol set where
-#'   `"standard"` provides four symbols, and, `"extended"` adds two more
-#'   symbols, making six.
-#' @param footnotes.spec_ref,footnotes.spec_ftr Optional specifications for
-#'   formatting of footnote references (`footnotes.spec_ref`) and their
-#'   associated marks the footer section (`footnotes.spec_ftr`) (same input as
-#'   the [opt_footnote_spec()] function). This is a string containing
-#'   specification control characters. The default is the spec string `"^i"`,
-#'   which is superscript text set in italics. Other control characters that can
-#'   be used are: (1) `"b"` for bold text, and (2) `"("` / `")"` for the
-#'   enclosure of footnote marks in parentheses.
-#' @param footnotes.multiline,source_notes.multiline An option to either put
-#'   footnotes and source notes in separate lines (the default, or `TRUE`) or
-#'   render them as a continuous line of text with `footnotes.sep` providing the
-#'   separator (by default `" "`) between notes.
-#' @param footnotes.sep,source_notes.sep The separating characters between
-#'   adjacent footnotes and source notes in their respective footer sections
-#'   when rendered as a continuous line of text (when
-#'   `footnotes.multiline == FALSE`). The default value is a single space
+#'
+#' @param footnotes.marks *Sequence of footnote marks*
+#'
+#'   The set of sequential marks used to reference and identify each of the
+#'   footnotes (same input as the [opt_footnote_marks()] function). We can
+#'   supply a vector that represents the series of footnote marks. This vector
+#'   is recycled when its usage goes beyond the length of the set. At each
+#'   cycle, the marks are simply combined (e.g., `*` -> `**` -> `***`). The
+#'   option exists for providing keywords for certain types of footnote marks.
+#'   The keyword `"numbers"` (the default, indicating that we want to use
+#'   numeric marks). We can use lowercase `"letters"` or uppercase `"LETTERS"`.
+#'   There is the option for using a traditional symbol set where `"standard"`
+#'   provides four symbols, and, `"extended"` adds two more symbols, making six.
+#'
+#' @param footnotes.spec_ref,footnotes.spec_ftr
+#'   *Specifications for formatting of footnote marks*
+#'
+#'   Optional specifications for formatting of footnote references
+#'   (`footnotes.spec_ref`) and their associated marks the footer section
+#'   (`footnotes.spec_ftr`) (same input as the [opt_footnote_spec()] function).
+#'   This is a string containing specification control characters. The default
+#'   is the spec string `"^i"`, which is superscript text set in italics. Other
+#'   control characters that can be used are: (1) `"b"` for bold text, and (2)
+#'   `"("` / `")"` for the enclosure of footnote marks in parentheses.
+#'
+#' @param footnotes.multiline,source_notes.multiline
+#'   *Typesetting of multiple footnotes and source notes*
+#'
+#'   An option to either put footnotes and source notes in separate lines (the
+#'   default, or `TRUE`) or render them as a continuous line of text with
+#'   `footnotes.sep` providing the separator (by default `" "`) between notes.
+#'
+#' @param footnotes.sep,source_notes.sep
+#'   *Separator characters between adjacent footnotes and source notes*
+#'
+#'   The separating characters between adjacent footnotes and source notes in
+#'   their respective footer sections when rendered as a continuous line of text
+#'   (when `footnotes.multiline == FALSE`). The default value is a single space
 #'   character (`" "`).
+#'
 #' @param source_notes.border.bottom.style,source_notes.border.bottom.width,source_notes.border.bottom.color
+#'   *Properties of the bottom border belonging to the source notes*
+#'
 #'   The style, width, and color properties for the bottom border of the
 #'   `source_notes` location.
+#'
 #' @param source_notes.border.lr.style,source_notes.border.lr.width,source_notes.border.lr.color
+#'   *Properties of left and right borders belonging to the source notes*
+#'
 #'   The style, width, and color properties for the left and right borders of
 #'   the `source_notes` location.
-#' @param row.striping.background_color The background color for striped table
-#'   body rows. A color name or a hexadecimal color code should be provided.
-#' @param row.striping.include_stub An option for whether to include the stub
-#'   when striping rows.
-#' @param row.striping.include_table_body An option for whether to include the
-#'   table body when striping rows.
+#'
+#' @param row.striping.background_color *Background color for row stripes*
+#'
+#'   The background color for striped table body rows. A color name or a
+#'   hexadecimal color code should be provided.
+#'
+#' @param row.striping.include_stub
+#'   *Inclusion of the table stub for row stripes*
+#'
+#'   An option for whether to include the stub when striping rows.
+#'
+#' @param row.striping.include_table_body
+#'   *Inclusion of the table body for row stripes*
+#'
+#'   An option for whether to include the table body when striping rows.
+#'
 #' @param container.width,container.height,container.padding.x,container.padding.y
+#'   *Table container dimensions and padding*
+#'
 #'   The width and height of the table's container, and, the vertical and
 #'   horizontal padding of the table's container. The container width and height
 #'   can be specified with units of pixels or as a percentage. The padding is to
@@ -3341,44 +3630,73 @@ set_style.cells_source_notes <- function(loc, data, style) {
 #'   value, it is assumed that the value is given in units of pixels. The [px()]
 #'   and [pct()] helper functions can also be used to pass in numeric values and
 #'   obtain values as pixel or percent units.
-#' @param container.overflow.x,container.overflow.y Options to enable scrolling
-#'   in the horizontal and vertical directions when the table content overflows
-#'   the container dimensions. Using `TRUE` (the default for both) means that
-#'   horizontal or vertical scrolling is enabled to view the entire table in
-#'   those directions. With `FALSE`, the table may be clipped if the table width
-#'   or height exceeds the `container.width` or `container.height`.
-#' @param ihtml.active The option for displaying an interactive version of an
-#'   HTML table (rather than an otherwise 'static' table). This enables the use
-#'   of controls for pagination, global search, filtering, and sorting. The
-#'   individual features are controlled by the other `table.*` options. By
-#'   default, the pagination (`ihtml.use_pagination`) and sorting
-#'   (`ihtml.use_sorting`) features are enabled. The `ihtml.active` option,
-#'   however, is `FALSE` by default.
-#' @param ihtml.use_pagination,ihtml.use_pagination_info For interactive HTML
-#'   output, the option for using pagination controls (below the table body) can
-#'   be controlled with `ihtml.use_pagination`. By default, this is `TRUE` and
-#'   it will allow the use to page through table content. The informational
-#'   display text regarding the current page can be set with
-#'   `ihtml.use_pagination_info` (which is `TRUE` by default).
-#' @param ihtml.use_sorting For interactive HTML output, the option to provide
-#'   controls for sorting column values. By default, this is `TRUE`.
-#' @param ihtml.use_search For interactive HTML output, an option that places a
-#'   search field for globally filtering rows to the requested content. By
-#'   default, this is `FALSE`.
-#' @param ihtml.use_filters For interactive HTML output, this places search
-#'   fields below each column header and allows for filtering by column. By
+#'
+#' @param container.overflow.x,container.overflow.y *Table container overflow*
+#'
+#'   Options to enable scrolling in the horizontal and vertical directions when
+#'   the table content overflows the container dimensions. Using `TRUE` (the
+#'   default for both) means that horizontal or vertical scrolling is enabled to
+#'   view the entire table in those directions. With `FALSE`, the table may be
+#'   clipped if the table width or height exceeds the `container.width` or
+#'   `container.height`.
+#'
+#' @param ihtml.active *Display interactive HTML table*
+#'
+#'   The option for displaying an interactive version of an HTML table (rather
+#'   than an otherwise 'static' table). This enables the use of controls for
+#'   pagination, global search, filtering, and sorting. The individual features
+#'   are controlled by the other `table.*` options. By default, the pagination
+#'   (`ihtml.use_pagination`) and sorting (`ihtml.use_sorting`) features are
+#'   enabled. The `ihtml.active` option, however, is `FALSE` by default.
+#'
+#' @param ihtml.use_pagination,ihtml.use_pagination_info *Use pagination*
+#'
+#'   For interactive HTML output, the option for using pagination controls
+#'   (below the table body) can be controlled with `ihtml.use_pagination`. By
+#'   default, this is `TRUE` and it will allow the use to page through table
+#'   content. The informational display text regarding the current page can be
+#'   set with `ihtml.use_pagination_info` (which is `TRUE` by default).
+#'
+#' @param ihtml.use_sorting *Provide column sorting controls*
+#'
+#'   For interactive HTML output, the option to provide controls for sorting
+#'   column values. By default, this is `TRUE`.
+#'
+#' @param ihtml.use_search *Provide a global search field*
+#'
+#'   For interactive HTML output, an option that places a search field for
+#'   globally filtering rows to the requested content. By default, this is
+#'   `FALSE`.
+#'
+#' @param ihtml.use_filters *Display filtering fields*
+#'
+#'   For interactive HTML output, this places search fields below each column
+#'   header and allows for filtering by column. By default, this is `FALSE`.
+#'
+#' @param ihtml.use_resizers *Allow column resizing*
+#'
+#'   For interactive HTML output, this allows for interactive resizing of
+#'   columns. By default, this is `FALSE`.
+#'
+#' @param ihtml.use_highlight *Enable row highlighting on hover*
+#'
+#'   For interactive HTML output, this highlights individual rows upon hover. By
 #'   default, this is `FALSE`.
-#' @param ihtml.use_resizers For interactive HTML output, this allows for
-#'   interactive resizing of columns. By default, this is `FALSE`.
-#' @param ihtml.use_highlight For interactive HTML output, this highlights
-#'   individual rows upon hover. By default, this is `FALSE`.
-#' @param ihtml.use_compact_mode For interactive HTML output, an option to
-#'   reduce vertical padding and thus make the table consume less vertical
-#'   space. By default, this is `FALSE`.
-#' @param ihtml.use_text_wrapping For interactive HTML output, an option to
-#'   control text wrapping. By default (`TRUE`), text will be wrapped to
-#'   multiple lines; if `FALSE`, text will be truncated to a single line.
+#'
+#' @param ihtml.use_compact_mode *Use compact mode*
+#'
+#'   For interactive HTML output, an option to reduce vertical padding and thus
+#'   make the table consume less vertical space. By default, this is `FALSE`.
+#'
+#' @param ihtml.use_text_wrapping *Use text wrapping*
+#'
+#'   For interactive HTML output, an option to control text wrapping. By default
+#'   (`TRUE`), text will be wrapped to multiple lines; if `FALSE`, text will be
+#'   truncated to a single line.
+#'
 #' @param ihtml.use_page_size_select,ihtml.page_size_default,ihtml.page_size_values
+#'   *Change page size properties*
+#'
 #'   For interactive HTML output, `ihtml.use_page_size_select` provides the
 #'   option to display a dropdown menu for the number of rows to show per page
 #'   of data. By default, this is the vector `c(10, 25, 50, 100)` which
@@ -3387,40 +3705,76 @@ set_style.cells_source_notes <- function(loc, data, style) {
 #'   `ihtml.page_size_values`. The default page size (initially set as `10`) can
 #'   be modified with `ihtml.page_size_default` and this works whether or not
 #'   `ihtml.use_page_size_select` is set to `TRUE`.
-#' @param ihtml.pagination_type For interactive HTML output and when using
-#'   pagination, one of three options for presentation pagination controls. The
-#'   default is `"numbers"`, where a series of page-number buttons is presented
-#'   along with 'previous' and 'next' buttons. The `"jump"` option provides an
-#'   input field with a stepper for the page number. With `"simple"`, only the
-#'   'previous' and 'next' buttons are displayed.
-#' @param page.orientation For RTF output, this provides an two options for page
+#'
+#' @param ihtml.pagination_type *Change pagination mode*
+#'
+#'   For interactive HTML output and when using pagination, one of three options
+#'   for presentation pagination controls. The default is `"numbers"`, where a
+#'   series of page-number buttons is presented along with 'previous' and 'next'
+#'   buttons. The `"jump"` option provides an input field with a stepper for the
+#'   page number. With `"simple"`, only the 'previous' and 'next' buttons are
+#'   displayed.
+#'
+#' @param page.orientation *Set RTF page orientation*
+#'
+#'   For RTF output, this provides an two options for page
 #'   orientation: `"portrait"` (the default) and `"landscape"`.
-#' @param page.numbering Within RTF output, should page numbering be displayed?
-#'   By default, this is set to `FALSE` but if `TRUE` then page numbering text
-#'   will be added to the document header.
-#' @param page.header.use_tbl_headings If `TRUE` then RTF output tables will
-#'   migrate all table headings (including the table title and all column
-#'   labels) to the page header. This page header content will repeat across
-#'   pages. By default, this is `FALSE`.
-#' @param page.footer.use_tbl_notes If `TRUE` then RTF output tables will
-#'   migrate all table footer content (this includes footnotes and source notes)
-#'   to the page footer. This page footer content will repeat across pages. By
-#'   default, this is `FALSE`.
-#' @param page.width,page.height The page width and height in the standard
-#'   portrait orientation. This is for RTF table output and the default
-#'   values (in inches) are `8.5in` and `11.0in`.
+#'
+#' @param page.numbering *Enable RTF page numbering*
+#'
+#'   Within RTF output, should page numbering be displayed? By default, this is
+#'   set to `FALSE` but if `TRUE` then page numbering text will be added to the
+#'   document header.
+#'
+#' @param page.header.use_tbl_headings
+#'
+#'   *Place table headings in RTF page header*
+#'
+#'   If `TRUE` then RTF output tables will migrate all table headings (including
+#'   the table title and all column labels) to the page header. This page header
+#'   content will repeat across pages. By default, this is `FALSE`.
+#'
+#' @param page.footer.use_tbl_notes
+#'
+#'   *Place table footer in RTF page footer*
+#'
+#'   If `TRUE` then RTF output tables will migrate all table footer content
+#'   (this includes footnotes and source notes) to the page footer. This page
+#'   footer content will repeat across pages. By default, this is `FALSE`.
+#'
+#' @param page.width,page.height
+#'
+#'   *Set RTF page dimensions*
+#'
+#'   The page width and height in the standard portrait orientation. This is for
+#'   RTF table output and the default values (in inches) are `8.5in` and
+#'   `11.0in`.
+#'
 #' @param page.margin.left,page.margin.right,page.margin.top,page.margin.bottom
+#'
+#'   *Set RTF page margins*
+#'
 #'   For RTF table output, these options correspond to the left, right, top, and
 #'   bottom page margins. The default values for each of these is `1.0in`.
-#' @param page.header.height,page.footer.height The heights of the page header
-#'   and footer for RTF table outputs. Default values for both are `0.5in`.
-#' @param quarto.use_bootstrap,quarto.disable_processing When rendering a **gt**
-#'   table with Quarto, the table can undergo transformations to support
-#'   advanced Quarto features. Setting `quarto.use_bootstrap` to `TRUE` (`FALSE`
-#'   by default) will allow Quarto to add Bootstrap classes to the table,
-#'   allowing those styles to permeate the table. Quarto performs other
-#'   alterations as well but they can all be deactivated with
-#'   `quarto.disable_processing = TRUE` (this option is `FALSE` by default).
+#'
+#' @param page.header.height,page.footer.height
+#'
+#'   *Set RTF page header and footer distances*
+#'
+#'   The heights of the page header and footer for RTF table outputs. Default
+#'   values for both are `0.5in`.
+#'
+#' @param quarto.use_bootstrap,quarto.disable_processing
+#'
+#'   *Modify Quarto properties*
+#'
+#'   When rendering a **gt** table with Quarto, the table can undergo
+#'   transformations to support advanced Quarto features. Setting
+#'   `quarto.use_bootstrap` to `TRUE` (`FALSE` by default) will allow Quarto to
+#'   add Bootstrap classes to the table, allowing those styles to permeate the
+#'   table. Quarto performs other alterations as well but they can all be
+#'   deactivated with `quarto.disable_processing = TRUE` (this option is `FALSE`
+#'   by default).
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/tab_remove.R b/R/tab_remove.R
index 75cb5c7146..42ec29cf48 100644
--- a/R/tab_remove.R
+++ b/R/tab_remove.R
@@ -11,7 +11,12 @@
 #' the table not contain a header. This function is safe to use even if there is
 #' no header part in the input `gt_tbl` object.
 #'
-#' @param data A table object of class `gt_tbl`.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -80,7 +85,12 @@ rm_header <- function(data) {
 #' the table not contain any content in the stubhead. This function is safe to
 #' use even if there is no stubhead label in the input `gt_tbl` object.
 #'
-#' @param data A table object of class `gt_tbl`.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -150,17 +160,31 @@ rm_stubhead <- function(data) {
 #' so long as select helpers (such as the default `everything()`) are used
 #' instead of explicit ID values.
 #'
-#' @param data A table object of class `gt_tbl`.
-#' @param spanners A specification of which spanner column labels should be
-#'   removed. Those to be removed can be given as a vector of spanner ID values
-#'   (every spanner column label has one, either set by the user or by **gt**
-#'   when using [tab_spanner_delim()]). A select helper can also be used and, by
-#'   default, this is `everything()` (whereby all spanner column labels will be
-#'   removed).
-#' @param levels Instead of removing spanner column labels by ID values, entire
-#'   levels of spanners can instead be removed. Supply a numeric vector of level
-#'   values (the first level is `1`) and, if they are present, they will be
-#'   removed. Any input given to `level` will mean that `spanners` is ignored.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param spanners *Spanners to remove*
+#'
+#'   `<spanner-targeting expression>` --- *default:* `everything()`
+#'
+#'   A specification of which spanner column labels should be removed. Those to
+#'   be removed can be given as a vector of spanner ID values (every spanner
+#'   column label has one, either set by the user or by **gt** when using
+#'   [tab_spanner_delim()]). A select helper can also be used and, by default,
+#'   this is `everything()` (whereby all spanner column labels will be removed).
+#'
+#' @param levels *Spanner levels to remove*
+#'
+#'   `scalar<numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   Instead of removing spanner column labels by ID values, entire levels of
+#'   spanners can instead be removed. Supply a numeric vector of level values
+#'   (the first level is `1`) and, if they are present, they will be removed.
+#'   Any input given to `level` will mean that `spanners` is ignored.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -348,12 +372,22 @@ rm_spanners <- function(
 #' (such as the default `everything()`) are used instead of explicit integer
 #' values.
 #'
-#' @param data A table object of class `gt_tbl`.
-#' @param footnotes A specification of which footnotes should be removed.
-#'   The footnotes to be removed can be given as a vector of integer values
-#'   (they are stored as integer positions, in order of creation, starting at
-#'   `1`). A select helper can also be used and, by default, this is
-#'   `everything()` (whereby all footnotes will be removed).
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param footnotes *Footnotes to remove*
+#'
+#'   `scalar<numeric|integer>|everything()` --- *default:* `everything()`
+#'
+#'   A specification of which footnotes should be removed. The footnotes to be
+#'   removed can be given as a vector of integer values (they are stored as
+#'   integer positions, in order of creation, starting at `1`). A select helper
+#'   can also be used and, by default, this is `everything()` (whereby all
+#'   footnotes will be removed).
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -510,12 +544,22 @@ rm_footnotes <- function(
 #' helpers (such as the default `everything()`) are used instead of explicit
 #' integer values.
 #'
-#' @param data A table object of class `gt_tbl`.
-#' @param source_notes A specification of which source notes should be removed.
-#'   The source notes to be removed can be given as a vector of integer values
-#'   (they are stored as integer positions, in order of creation, starting at
-#'   `1`). A select helper can also be used and, by default, this is
-#'   `everything()` (whereby all source notes will be removed).
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param source_notes *Source notes to remove*
+#'
+#'   `scalar<numeric|integer>|everything()` --- *default:* `everything()`
+#'
+#'   A specification of which source notes should be removed. The source notes
+#'   to be removed can be given as a vector of integer values (they are stored
+#'   as integer positions, in order of creation, starting at `1`). A select
+#'   helper can also be used and, by default, this is `everything()` (whereby
+#'   all source notes will be removed).
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -648,7 +692,12 @@ rm_source_notes <- function(
 #' the table not have a caption at all. This function is safe to use even if
 #' there is no table caption set in the input `gt_tbl` object.
 #'
-#' @param data A table object of class `gt_tbl`.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/tab_style_body.R b/R/tab_style_body.R
index 7aa746b0c8..af4bc59c10 100644
--- a/R/tab_style_body.R
+++ b/R/tab_style_body.R
@@ -24,46 +24,84 @@
 #' - the cell borders ([cell_borders()])
 #'
 #' @inheritParams fmt_number
-#' @param style The styles to use for the targeted cells. The [cell_text()],
-#'   [cell_fill()], and [cell_borders()] helper functions can be used here to
-#'   more easily generate valid styles. If using more than one helper function
-#'   to define styles, all calls must be enclosed in a [list()]. Custom CSS
-#'   declarations can be used for HTML output by including a [css()]-based
-#'   statement as a list item.
-#' @param columns Optional columns for constraining the targeting process.
-#'   Providing [everything()] (the default) results in cells in all `columns`
-#'   being targeting (this can be limited by `rows` however). Can either be a
-#'   series of column names provided in [c()], a vector of column indices, or a
-#'   helper function focused on selections. The select helper functions are:
+#'
+#' @param style *Style declarations*
+#'
+#'   `<style expressions>` --- **required**
+#'
+#'   The styles to use for the targeted cells. The [cell_text()], [cell_fill()],
+#'   and [cell_borders()] helper functions can be used here to more easily
+#'   generate valid styles. If using more than one helper function to define
+#'   styles, all calls must be enclosed in a [list()]. Custom CSS declarations
+#'   can be used for HTML output by including a [css()]-based statement as a
+#'   list item.
+#'
+#' @param columns *Columns to target*
+#'
+#'   `<column-targeting expression>` --- *default:* `everything()`
+#'
+#'   The columns to which the targeting operations are constrained.  Can either
+#'   be a series of column names provided in [c()], a vector of column indices,
+#'   or a select helper function. Examples of select helper functions include
 #'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
-#'   [num_range()], and [everything()].
-#' @param rows Optional rows for constraining the targeting process. Providing
-#'   [everything()] (the default) results in all rows in `columns` being
-#'   targeted. Alternatively, we can supply a vector of row captions within
-#'   [c()], a vector of row indices, or a helper function focused on selections.
-#'   The select helper functions are: [starts_with()], [ends_with()],
-#'   [contains()], [matches()], [one_of()], [num_range()], and [everything()].
-#'   We can also use expressions to filter down to the rows we need (e.g.,
-#'   `[colname_1] > 100 & [colname_2] < 50`).
-#' @param values The specific value or values that should be targeted for
-#'   styling. If `pattern` is also supplied then `values` will be ignored.
-#' @param pattern A regex pattern that can target solely those values in
-#'   `character`-based columns. If `values` is also supplied, `pattern` will
-#'   take precedence.
-#' @param fn A supplied function that operates on each cell of each column
-#'   specified through `columns` and `rows`. The function should be fashioned
-#'   such that a single logical value is returned. If either of `values` or
-#'   `pattern` is also supplied, `fn` will take precedence.
-#' @param targets A vector of styling target keywords to contain or expand the
-#'   target of each cell. By default, this is a vector just containing `"cell"`.
-#'   However, the keywords `"row"` and `"column"` may be used separately or in
-#'   combination to style the target cells' associated rows or columns.
-#' @param extents A vector of locations to project styling. By default, this is
-#'   a vector just containing `"body"`, whereby styled rows or columns
-#'   (facilitated via inclusion of the `"row"` and `"column"` keywords in
-#'   `targets`) will not permeate into the stub. The additional keyword `"stub"`
-#'   may be used alone or in conjunction with `"body"` to project or expand the
-#'   styling into the stub.
+#'   [num_range()], and [everything()]. This argument works in tandem with the
+#'   `spanners` argument.
+#'
+#' @param rows *Rows to target*
+#'
+#'   `<row-targeting expression>` --- *default:* `everything()`
+#'
+#'   In conjunction with `columns`, we can specify which of their rows should
+#'   form a constraint for targeting operations. The default [everything()]
+#'   results in all rows in `columns` being formatted. Alternatively, we can
+#'   supply a vector of row captions within [c()], a vector of row indices, or a
+#'   select helper function. Examples of select helper functions include
+#'   [starts_with()], [ends_with()], [contains()], [matches()], [one_of()],
+#'   [num_range()], and [everything()]. We can also use expressions to filter
+#'   down to the rows we need (e.g., `[colname_1] > 100 & [colname_2] < 50`).
+#'
+#' @param values *Values for targeting*
+#'
+#'   `vector<character|numeric|integer>` --- *default:* `NULL` (`optional`)
+#'
+#'   The specific value or values that should be targeted for styling. If
+#'   `pattern` is also supplied then `values` will be ignored.
+#'
+#' @param pattern *Regex pattern for targeting*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   A regex pattern that can target solely those values in `character`-based
+#'   columns. If `values` is also supplied, `pattern` will take precedence.
+#'
+#' @param fn *Function to return logical values*
+#'
+#'   `<function>` --- *default:* `NULL` (`optional`)
+#'
+#'   A supplied function that operates on each cell of each column specified
+#'   through `columns` and `rows`. The function should be fashioned such that a
+#'   single logical value is returned. If either of `values` or `pattern` is
+#'   also supplied, `fn` will take precedence.
+#'
+#' @param targets *Styling targets*
+#'
+#'   `vector<character>` --- *default:* `"cell"`
+#'
+#'   A vector of styling target keywords to contain or expand the target of each
+#'   cell. By default, this is a vector just containing `"cell"`. However, the
+#'   keywords `"row"` and `"column"` may be used separately or in combination to
+#'   style the target cells' associated rows or columns.
+#'
+#' @param extents *Styling extents*
+#'
+#'   `vector<character>` --- *default:* `"body"`
+#'
+#'   A vector of locations to project styling. By default, this is a vector just
+#'   containing `"body"`, whereby styled rows or columns (facilitated via
+#'   inclusion of the `"row"` and `"column"` keywords in `targets`) will not
+#'   permeate into the stub. The additional keyword `"stub"` may be used alone
+#'   or in conjunction with `"body"` to project or expand the styling into the
+#'   stub.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/R/text_transform.R b/R/text_transform.R
index f4c1dea6a1..96cf4d229f 100644
--- a/R/text_transform.R
+++ b/R/text_transform.R
@@ -32,16 +32,35 @@
 #' that is done, the remaining two values to supply are for the regex pattern
 #' (`pattern`) and the replacement for all matched text (`replacement`).
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param pattern A regex pattern used to target text fragments in the cells
-#'   resolved in locations.
-#' @param replacement The replacement text for any matched text fragments.
-#' @param locations The cell or set of cells to be associated with the text
-#'   transformation. Only the [cells_body()], [cells_stub()],
-#'   [cells_row_groups()], [cells_column_labels()], and
-#'   [cells_column_spanners()] helper functions can be used here. We can enclose
-#'   several of these calls within a `list()` if we wish to make the
-#'   transformation happen at different locations.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param pattern *Regex pattern to match with*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   A regex pattern used to target text fragments in the cells resolved in
+#'   locations.
+#'
+#' @param replacement *Replacement text*
+#'
+#'   `scalar<character>` --- **required**
+#'
+#'   The replacement text for any matched text fragments.
+#'
+#' @param locations *Locations to target*
+#'
+#'   `<locations expressions>` --- *default:* `cells_body()`
+#'
+#'   The cell or set of cells to be associated with the text transformation.
+#'   Only the [cells_body()], [cells_stub()], [cells_row_groups()],
+#'   [cells_column_labels()], and [cells_column_spanners()] helper functions can
+#'   be used here. We can enclose several of these calls within a `list()` if we
+#'   wish to make the transformation happen at different locations.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -120,20 +139,38 @@ text_replace <- function(
 #' vector of length one (i.e., either `TRUE` or `FALSE`). To refer to the values
 #' undergoing transformation, you need to use the `x` variable.
 #'
-#' @param .data A table object that is created using the [gt()] function.
-#' @param ... A sequence of two-sided formulas. The left hand side (LHS)
+#' @param .data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Matching expressions*
+#'
+#'   `<multiple expressions>` --- **required**
+#'
+#'   A sequence of two-sided formulas. The left hand side (LHS)
 #'   determines which values match this case. The right hand side (RHS) provides
 #'   the replacement text (it must resolve to a value of the `character` class).
 #'   The LHS inputs must evaluate to logical vectors.
-#' @param .default The replacement text to use when cell values aren't matched
-#'   by any of the LHS inputs. If `NULL`, the default, no replacement text will
-#'   be used.
-#' @param .locations The cell or set of cells to be associated with the text
-#'   transformation. Only the [cells_body()], [cells_stub()],
-#'   [cells_row_groups()], [cells_column_labels()], and
-#'   [cells_column_spanners()] helper functions can be used here. We can enclose
-#'   several of these calls within a `list()` if we wish to make the
-#'   transformation happen at different locations.
+#'
+#' @param .default *Default replacement text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The replacement text to use when cell values aren't matched by any of the
+#'   LHS inputs. If `NULL`, the default, no replacement text will be used.
+#'
+#' @param .locations *Locations to target*
+#'
+#'   `<locations expressions>` --- *default:* `cells_body()`
+#'
+#'   The cell or set of cells to be associated with the text transformation.
+#'   Only the [cells_body()], [cells_stub()], [cells_row_groups()],
+#'   [cells_column_labels()], and [cells_column_spanners()] helper functions can
+#'   be used here. We can enclose several of these calls within a `list()` if we
+#'   wish to make the transformation happen at different locations.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -251,28 +288,51 @@ text_case_when <- function(
 #' those strings. This can be changed to a partial matching and replacement
 #' strategy with the alternate option.
 #'
-#' @param .data A table object that is created using the [gt()] function.
-#' @param ... A sequence of two-sided formulas matching this general
-#'   construction: `<old_text> ~ <new_text>`. The left hand side (LHS)
-#'   determines which values to match on and it can be any length (allowing for
-#'   `new_text` to replace different values of `old_text`). The right hand side
-#'   (RHS) provides the replacement text (it must resolve to a single value of
-#'   the `character` class).
-#' @param .default The replacement text to use when cell values aren't matched
-#'   by any of the LHS inputs. If `NULL`, the default, no replacement text will
-#'   be used.
-#' @param .replace A choice in how the matching is to be done. The default
-#'   `"all"` means that the `old_text` (on the LHS of formulas given in `...`)
-#'   must match the cell text *completely*. With that option, the replacement
-#'   will completely replace that matched text. With `"partial"`, the match will
-#'   occur in all substrings of `old_text`. In this way, the replacements will
-#'   act on those matched substrings.
-#' @param .locations The cell or set of cells to be associated with the text
-#'   transformation. Only the [cells_body()], [cells_stub()],
-#'   [cells_row_groups()], [cells_column_labels()], and
-#'   [cells_column_spanners()] helper functions can be used here. We can enclose
-#'   several of these calls within a `list()` if we wish to make the
-#'   transformation happen at different locations.
+#' @param .data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param ... *Matching expressions*
+#'
+#'   `<multiple expressions>` --- **required**
+#'
+#'   A sequence of two-sided formulas matching this general construction:
+#'   `<old_text> ~ <new_text>`. The left hand side (LHS) determines which values
+#'   to match on and it can be any length (allowing for `new_text` to replace
+#'   different values of `old_text`). The right hand side (RHS) provides the
+#'   replacement text (it must resolve to a single value of the `character`
+#'   class).
+#'
+#' @param .default *Default replacement text*
+#'
+#'   `scalar<character>` --- *default:* `NULL` (`optional`)
+#'
+#'   The replacement text to use when cell values aren't matched by any of the
+#'   LHS inputs. If `NULL`, the default, no replacement text will be used.
+#'
+#' @param .replace *Method for text replacement*
+#'
+#'   `singl-kw:[all|partial]` --- *default:* `"all"`
+#'
+#'   A choice in how the matching is to be done. The default `"all"` means that
+#'   the `old_text` (on the LHS of formulas given in `...`) must match the cell
+#'   text *completely*. With that option, the replacement will completely
+#'   replace that matched text. With `"partial"`, the match will occur in all
+#'   substrings of `old_text`. In this way, the replacements will act on those
+#'   matched substrings.
+#'
+#' @param .locations *Locations to target*
+#'
+#'   `<locations expressions>` --- *default:* `cells_body()`
+#'
+#'   The cell or set of cells to be associated with the text transformation.
+#'   Only the [cells_body()], [cells_stub()], [cells_row_groups()],
+#'   [cells_column_labels()], and [cells_column_spanners()] helper functions can
+#'   be used here. We can enclose several of these calls within a `list()` if we
+#'   wish to make the transformation happen at different locations.
 #'
 #' @return An object of class `gt_tbl`.
 #'
@@ -442,16 +502,29 @@ text_case_match <- function(
 #' character vector of the same length as the input. Using the construction
 #' `function(x) { .. }` for the function is recommended.
 #'
-#' @param data A table object that is created using the [gt()] function.
-#' @param fn The function to use for text transformation. It should include `x`
-#'   as an argument and return a character vector of the same length as the
-#'   input `x`.
-#' @param locations The cell or set of cells to be associated with the text
-#'   transformation. Only the [cells_body()], [cells_stub()],
-#'   [cells_row_groups()], [cells_column_labels()], and
-#'   [cells_column_spanners()] helper functions can be used here. We can enclose
-#'   several of these calls within a `list()` if we wish to make the
-#'   transformation happen at different locations.
+#' @param data *The gt table data object*
+#'
+#'   `obj:<gt_tbl>` --- **required**
+#'
+#'   This is the **gt** table object that is commonly created through use of the
+#'   [gt()] function.
+#'
+#' @param fn *Function for text transformation*
+#'
+#'   `<function>` --- **required**
+#'
+#'   The function to use for text transformation. It should include `x` as an
+#'   argument and return a character vector of the same length as the input `x`.
+#'
+#' @param locations *Locations to target*
+#'
+#'   `<locations expressions>` --- *default:* `cells_body()`
+#'
+#'   The cell or set of cells to be associated with the text transformation.
+#'   Only the [cells_body()], [cells_stub()], [cells_row_groups()],
+#'   [cells_column_labels()], and [cells_column_spanners()] helper functions can
+#'   be used here. We can enclose several of these calls within a `list()` if we
+#'   wish to make the transformation happen at different locations.
 #'
 #' @return An object of class `gt_tbl`.
 #'
diff --git a/man/adjust_luminance.Rd b/man/adjust_luminance.Rd
index ff36ea7689..17b6f33fb5 100644
--- a/man/adjust_luminance.Rd
+++ b/man/adjust_luminance.Rd
@@ -7,13 +7,22 @@
 adjust_luminance(colors, steps)
 }
 \arguments{
-\item{colors}{A vector of colors that will undergo an adjustment in
-luminance. Each color value provided must either be a color name (in the
-set of colors provided by \code{grDevices::colors()}) or a hexadecimal string in
-the form of "#RRGGBB" or "#RRGGBBAA".}
+\item{colors}{\emph{Color vector}
 
-\item{steps}{A positive or negative factor by which the luminance will be
-adjusted. Must be a number between \code{-2.0} and \code{2.0}.}
+\verb{vector<character>} --- \strong{required}
+
+This is the vector of colors that will undergo an adjustment in luminance.
+Each color value provided must either be a color name (in the set of colors
+provided by \code{grDevices::colors()}) or a hexadecimal string in the form of
+"#RRGGBB" or "#RRGGBBAA".}
+
+\item{steps}{\emph{Adjustment level}
+
+\verb{scalar<numeric|integer>(-2>=val>=2)} --- \strong{required}
+
+A positive or negative factor by which the luminance of colors in the
+\code{colors} vector will be adjusted. Must be a number between \code{-2.0} and
+\code{2.0}.}
 }
 \value{
 A vector of color values.
diff --git a/man/as.data.frame.gt_tbl.Rd b/man/as.data.frame.gt_tbl.Rd
index 1643ef1049..d9f74f591a 100644
--- a/man/as.data.frame.gt_tbl.Rd
+++ b/man/as.data.frame.gt_tbl.Rd
@@ -7,9 +7,19 @@
 \method{as.data.frame}{gt_tbl}(x, ...)
 }
 \arguments{
-\item{x}{An object of class \code{gt_tbl}.}
+\item{x}{\emph{The gt table data object}
 
-\item{...}{Any additional parameters.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Optional parameters}
+
+\verb{<multiple expressions>} --- (\code{optional})
+
+Anything provided here in \code{...} will be passed to internal function calls
+that can consume it.}
 }
 \description{
 This facilitates conversion of the \code{gt_tbl} object to a data frame.
diff --git a/man/as_latex.Rd b/man/as_latex.Rd
index e64c1f2e26..c5a8e2aa18 100644
--- a/man/as_latex.Rd
+++ b/man/as_latex.Rd
@@ -7,7 +7,12 @@
 as_latex(data)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \description{
 Get the LaTeX content from a \code{gt_tbl} object as a \code{knit_asis} object. This
diff --git a/man/as_raw_html.Rd b/man/as_raw_html.Rd
index 3b7c56f669..ef194b097b 100644
--- a/man/as_raw_html.Rd
+++ b/man/as_raw_html.Rd
@@ -7,12 +7,21 @@
 as_raw_html(data, inline_css = TRUE)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{inline_css}{An option to supply styles to table elements as inlined CSS
-styles. This is useful when including the table HTML as part of an HTML
-email message body, since inlined styles are largely supported in email
-clients over using CSS in a \verb{<style>} block.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{inline_css}{\emph{Use inline CSS}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to supply styles to table elements as inlined CSS styles. This is
+useful when including the table HTML as part of an HTML email message body,
+since inlined styles are largely supported in email clients over using CSS
+in a \verb{<style>} block.}
 }
 \description{
 Get the HTML content from a \code{gt_tbl} object as a single-element character
diff --git a/man/as_rtf.Rd b/man/as_rtf.Rd
index e4067b8fe2..d15c091e6b 100644
--- a/man/as_rtf.Rd
+++ b/man/as_rtf.Rd
@@ -14,20 +14,39 @@ as_rtf(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{gt()} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{incl_open, incl_close}{Options that govern whether the opening or
-closing \code{"{"} and \code{"}"} should be included. By default, both options are
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{incl_open, incl_close}{\emph{Include opening/closing braces}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Options that govern whether the opening or closing \code{"{"} and \code{"}"} should
+be included. By default, both options are \code{TRUE}.}
+
+\item{incl_header}{\emph{Include RTF header}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the RTF header be included in the output? By default, this is
 \code{TRUE}.}
 
-\item{incl_header}{Should the RTF header be included in the output? By
-default, this is \code{TRUE}.}
+\item{incl_page_info}{\emph{Include RTF page information}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the RTF output include directives for the document pages? This is
+\code{TRUE} by default.}
+
+\item{incl_body}{\emph{Include RTF body}
 
-\item{incl_page_info}{Should the RTF output include directives for the
-document pages? This is \code{TRUE} by default.}
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{incl_body}{An option to include the body of RTF document. By
-default, this is \code{TRUE}.}
+An option to include the body of RTF document. By default, this is \code{TRUE}.}
 }
 \description{
 Get the RTF content from a \code{gt_tbl} object as as a single-element character
diff --git a/man/as_word.Rd b/man/as_word.Rd
index dd832a8720..1ce2b8ef2c 100644
--- a/man/as_word.Rd
+++ b/man/as_word.Rd
@@ -14,26 +14,49 @@ as_word(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{gt()} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{align}{An option for table alignment. Can either be \code{"center"} (the
-default), \code{"left"}, or \code{"right"}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{caption_location}{Determines where the caption should be positioned.
-This can either be \code{"top"} (the default), \code{"bottom"}, or \code{"embed"}.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{caption_align}{Determines the alignment of the caption. This is
+\item{align}{\emph{Table alignment}
+
+\verb{scalar<character>} --- \emph{default:} \code{"center"}
+
+An option for table alignment. Can either be \code{"center"}, \code{"left"}, or
+\code{"right"}.}
+
+\item{caption_location}{\emph{Caption location}
+
+\verb{singl-kw:[top|bottom|embed]} --- \emph{default:} \code{"top"}
+
+Determines where the caption should be positioned. This can either be
+\code{"top"}, \code{"bottom"}, or \code{"embed"}.}
+
+\item{caption_align}{\emph{Caption alignment}
+
+Determines the alignment of the caption. This is
 either \code{"left"} (the default), \code{"center"}, or \code{"right"}. This option is
 only used when \code{caption_location} is not set as \code{"embed"}.}
 
-\item{split}{A \code{TRUE} or \code{FALSE} (the default) value that indicates whether
-to activate the Word option \verb{Allow row to break across pages}.}
+\item{split}{\emph{Allow splitting}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that indicates whether to activate the Word option
+\verb{Allow row to break across pages}.}
+
+\item{keep_with_next}{\emph{Keeping rows together}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{keep_with_next}{A \code{TRUE} (the default) or \code{FALSE} value that indicates
-whether a table should use Word option \verb{keep rows together}.}
+A logical value that indicates whether a table should use Word option
+\verb{keep rows together}.}
 }
 \description{
-Get the Open Office XML table tag content from a \code{gt_tbl} object as as a
+Get the Open Office XML table tag content from a \code{gt_tbl} object as a
 single-element character vector.
 }
 \section{Examples}{
diff --git a/man/cell_borders.Rd b/man/cell_borders.Rd
index 1319a2fa82..a43741dc55 100644
--- a/man/cell_borders.Rd
+++ b/man/cell_borders.Rd
@@ -7,17 +7,36 @@
 cell_borders(sides = "all", color = "#000000", style = "solid", weight = px(1))
 }
 \arguments{
-\item{sides}{The border sides to be modified. Options include \code{"left"},
+\item{sides}{\emph{Border sides}
+
+\verb{vector<character>} --- \emph{default:} \code{"all"}
+
+The border sides to be modified. Options include \code{"left"},
 \code{"right"}, \code{"top"}, and \code{"bottom"}. For all borders surrounding the
 selected cells, we can use the \code{"all"} option.}
 
-\item{color, style, weight}{The border color, style, and weight. The \code{color}
-can be defined with a color name or with a hexadecimal color code. The
-default \code{color} value is \code{"#000000"} (black). The \code{style} can be one of
-either \code{"solid"} (the default), \code{"dashed"}, \code{"dotted"}, \code{"hidden"}, or
-\code{"double"}. The \code{weight} of the border lines is to be given in pixel values
-(the \code{\link[=px]{px()}} helper function is useful for this. The default value for
-\code{weight} is \code{"1px"}. Borders for any defined \code{sides} can be removed by
+\item{color}{\emph{Border color}
+
+\verb{scalar<character>|NULL} --- \emph{default:} \code{"#000000"}
+
+The border \code{color} can be defined with a color name or with a hexadecimal
+color code. The default \code{color} value is \code{"#000000"} (black). Borders for any
+defined \code{sides} can be removed by supplying \code{NULL} here.}
+
+\item{style}{\emph{Border line style}
+
+\verb{scalar<character>|NULL} --- \emph{default:} \code{"solid"}
+
+The border \code{style} can be one of either \code{"solid"} (the default),
+\code{"dashed"}, \code{"dotted"}, \code{"hidden"}, or \code{"double"}. Borders for any
+defined \code{sides} can be removed by supplying \code{NULL} here.}
+
+\item{weight}{\emph{Border weight}
+
+\verb{scalar<character>|NULL} --- \emph{default:} \code{px(1)}
+
+The default value for \code{weight} is \code{"1px"} and higher values will become
+more visually prominent. Borders for any defined \code{sides} can be removed by
 supplying \code{NULL} to any of \code{color}, \code{style}, or \code{weight}.}
 }
 \value{
diff --git a/man/cell_fill.Rd b/man/cell_fill.Rd
index f349adb442..5ec4a75545 100644
--- a/man/cell_fill.Rd
+++ b/man/cell_fill.Rd
@@ -7,13 +7,21 @@
 cell_fill(color = "#D3D3D3", alpha = NULL)
 }
 \arguments{
-\item{color}{The fill color. If nothing is provided, then \code{"#D3D3D3"} (light
-gray) will be used as a default.}
+\item{color}{\emph{Cell fill color}
 
-\item{alpha}{An optional alpha transparency value for the \code{color} as single
-value in the range of \code{0} (fully transparent) to \code{1} (fully opaque). If not
-provided the fill color will either be fully opaque or use alpha
-information from the color value if it is supplied in the #RRGGBBAA format.}
+\verb{scalar<character>} --- \emph{default:} \code{"#D3D3D3"}
+
+If nothing is provided for \code{color} then \code{"#D3D3D3"} (light gray) will be
+used as a default.}
+
+\item{alpha}{\emph{Transparency value}
+
+\verb{scalar<numeric|integer>(0>=val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional alpha transparency value for the \code{color} as single value in the
+range of \code{0} (fully transparent) to \code{1} (fully opaque). If not provided the
+fill color will either be fully opaque or use alpha information from the
+color value if it is supplied in the \verb{#RRGGBBAA} format.}
 }
 \value{
 A list object of class \code{cell_styles}.
diff --git a/man/cell_text.Rd b/man/cell_text.Rd
index 92ff2a06d8..9e2a366e27 100644
--- a/man/cell_text.Rd
+++ b/man/cell_text.Rd
@@ -20,55 +20,102 @@ cell_text(
 )
 }
 \arguments{
-\item{color}{The text color.}
+\item{color}{\emph{Text color}
 
-\item{font}{The font or collection of fonts (subsequent font names are) used
-as fallbacks.}
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{size}{The size of the font. Can be provided as a number that is assumed
-to represent \code{px} values (or could be wrapped in the \code{\link[=px]{px()}}) helper
-function. We can also use one of the following absolute size keywords:
-\code{"xx-small"}, \code{"x-small"}, \code{"small"}, \code{"medium"}, \code{"large"}, \code{"x-large"},
-or \code{"xx-large"}.}
+The text color can be modified through the \code{color} argument.}
 
-\item{align}{The text alignment. Can be one of either \code{"center"}, \code{"left"},
-\code{"right"}, or \code{"justify"}.}
+\item{font}{\emph{Font (or collection of fonts) used for text}
 
-\item{v_align}{The vertical alignment of the text in the cell. Options are
-\code{"middle"}, \code{"top"}, or \code{"bottom"}.}
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{style}{The text style. Can be one of either \code{"normal"}, \code{"italic"}, or
-\code{"oblique"}.}
+The font or collection of fonts (subsequent font names are) used as
+fallbacks.}
 
-\item{weight}{The weight of the font. Can be a text-based keyword such as
+\item{size}{\emph{Text size}
+
+\verb{scalar<numeric|integer|character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The size of the font. Can be provided as a number that is assumed to
+represent \code{px} values (or could be wrapped in the \code{\link[=px]{px()}}) helper function.
+We can also use one of the following absolute size keywords: \code{"xx-small"},
+\code{"x-small"}, \code{"small"}, \code{"medium"}, \code{"large"}, \code{"x-large"}, or
+\code{"xx-large"}.}
+
+\item{align}{\emph{Text alignment}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The text in a cell can be aligned though one of the following options:
+\code{"center"}, \code{"left"}, \code{"right"}, or \code{"justify"}.}
+
+\item{v_align}{\emph{Vertical alignment}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The vertical alignment of the text in the cell can be modified through the
+options \code{"middle"}, \code{"top"}, or \code{"bottom"}.}
+
+\item{style}{\emph{Text style}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Can be one of either \code{"normal"}, \code{"italic"}, or \code{"oblique"}.}
+
+\item{weight}{\emph{Font weight}
+
+\verb{scalar<character|numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The weight of the font can be modified thorough a text-based option such as
 \code{"normal"}, \code{"bold"}, \code{"lighter"}, \code{"bolder"}, or, a numeric value between
 \code{1} and \code{1000}, inclusive. Note that only variable fonts may support the
 numeric mapping of weight.}
 
-\item{stretch}{Allows for text to either be condensed or expanded. We can use
-one of the following text-based keywords to describe the degree of
+\item{stretch}{\emph{Stretch text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Allows for text to either be condensed or expanded. We can use one of the
+following text-based keywords to describe the degree of
 condensation/expansion: \code{"ultra-condensed"}, \code{"extra-condensed"},
 \code{"condensed"}, \code{"semi-condensed"}, \code{"normal"}, \code{"semi-expanded"},
 \code{"expanded"}, \code{"extra-expanded"}, or \code{"ultra-expanded"}. Alternatively, we
 can supply percentage values from \verb{0\\\%} to \verb{200\\\%}, inclusive. Negative
 percentage values are not allowed.}
 
-\item{decorate}{Allows for text decoration effect to be applied. Here, we can
-use \code{"overline"}, \code{"line-through"}, or \code{"underline"}.}
+\item{decorate}{\emph{Decorate text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Allows for text decoration effect to be applied. Here, we can use
+\code{"overline"}, \code{"line-through"}, or \code{"underline"}.}
+
+\item{transform}{\emph{Transform text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Allows for the transformation of text. Options are \code{"uppercase"},
+\code{"lowercase"}, or \code{"capitalize"}.}
+
+\item{whitespace}{\emph{White-space options}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A white-space preservation option. By default, runs of white-space will be
+collapsed into single spaces but several options exist to govern how
+white-space is collapsed and how lines might wrap at soft-wrap
+opportunities. The options are \code{"normal"}, \code{"nowrap"}, \code{"pre"},
+\code{"pre-wrap"}, \code{"pre-line"}, and \code{"break-spaces"}.}
 
-\item{transform}{Allows for the transformation of text. Options are
-\code{"uppercase"}, \code{"lowercase"}, or \code{"capitalize"}.}
+\item{indent}{\emph{Text indentation}
 
-\item{whitespace}{A white-space preservation option. By default, runs of
-white-space will be collapsed into single spaces but several options exist
-to govern how white-space is collapsed and how lines might wrap at
-soft-wrap opportunities. The keyword options are \code{"normal"}, \code{"nowrap"},
-\code{"pre"}, \code{"pre-wrap"}, \code{"pre-line"}, and \code{"break-spaces"}.}
+\verb{scalar<numeric|integer|character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{indent}{The indentation of the text. Can be provided as a number that
-is assumed to represent \code{px} values (or could be wrapped in the \code{\link[=px]{px()}})
-helper function. Alternatively, this can be given as a percentage (easily
-constructed with \code{\link[=pct]{pct()}}).}
+The indentation of the text. Can be provided as a number that is assumed to
+represent \code{px} values (or could be wrapped in the \code{\link[=px]{px()}}) helper function.
+Alternatively, this can be given as a percentage (easily constructed with
+\code{\link[=pct]{pct()}}).}
 }
 \value{
 A list object of class \code{cell_styles}.
diff --git a/man/cells_body.Rd b/man/cells_body.Rd
index 2b8bfc261d..42e29ca1b8 100644
--- a/man/cells_body.Rd
+++ b/man/cells_body.Rd
@@ -7,9 +7,28 @@
 cells_body(columns = everything(), rows = everything())
 }
 \arguments{
-\item{columns}{The names of the columns that are to be targeted.}
+\item{columns}{\emph{Columns to target}
 
-\item{rows}{The names of the rows that are to be targeted.}
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which targeting operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_body} and \code{location_cells}.
diff --git a/man/cells_column_labels.Rd b/man/cells_column_labels.Rd
index a2d73fa904..15e043bdbf 100644
--- a/man/cells_column_labels.Rd
+++ b/man/cells_column_labels.Rd
@@ -7,7 +7,15 @@
 cells_column_labels(columns = everything())
 }
 \arguments{
-\item{columns}{The names of the column labels that are to be targeted.}
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which targeting operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 }
 \value{
 A list object with the classes \code{cells_column_labels} and
diff --git a/man/cells_column_spanners.Rd b/man/cells_column_spanners.Rd
index 2fbe1381f6..f62d882753 100644
--- a/man/cells_column_spanners.Rd
+++ b/man/cells_column_spanners.Rd
@@ -7,7 +7,14 @@
 cells_column_spanners(spanners = everything())
 }
 \arguments{
-\item{spanners}{The names of the spanners that are to be targeted.}
+\item{spanners}{\emph{Specification of spanner IDs}
+
+\verb{<spanner-targeting expression>} --- \emph{default:} \code{everything()}
+
+The spanners to which targeting operations are constrained. Can either be a
+series of spanner ID values provided in \code{\link[=c]{c()}} or a select helper function.
+Examples of select helper functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
+\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 }
 \value{
 A list object with the classes \code{cells_column_spanners} and
diff --git a/man/cells_grand_summary.Rd b/man/cells_grand_summary.Rd
index b2abf59de7..e60fa7c804 100644
--- a/man/cells_grand_summary.Rd
+++ b/man/cells_grand_summary.Rd
@@ -7,9 +7,28 @@
 cells_grand_summary(columns = everything(), rows = everything())
 }
 \arguments{
-\item{columns}{The names of the columns that are to be targeted.}
+\item{columns}{\emph{Columns to target}
 
-\item{rows}{The names of the rows that are to be targeted.}
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which targeting operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_grand_summary} and
diff --git a/man/cells_group.Rd b/man/cells_group.Rd
index d64a905378..b87bbcbb04 100644
--- a/man/cells_group.Rd
+++ b/man/cells_group.Rd
@@ -7,7 +7,15 @@
 cells_group(groups = everything())
 }
 \arguments{
-\item{groups}{The names of the row groups that are to be targeted.}
+\item{groups}{\emph{Specification of row group IDs}
+
+\verb{<row-group-targeting expression>} --- \emph{default:} \code{everything()}
+
+The row groups to which targeting operations are constrained. Can either be
+a series of row group ID values provided in \code{\link[=c]{c()}} or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}.}
 }
 \description{
 Location helper for targeting row groups (deprecated)
diff --git a/man/cells_row_groups.Rd b/man/cells_row_groups.Rd
index 150ff4c96e..d1c20e251c 100644
--- a/man/cells_row_groups.Rd
+++ b/man/cells_row_groups.Rd
@@ -7,7 +7,15 @@
 cells_row_groups(groups = everything())
 }
 \arguments{
-\item{groups}{The names of the row groups that are to be targeted.}
+\item{groups}{\emph{Specification of row group IDs}
+
+\verb{<row-group-targeting expression>} --- \emph{default:} \code{everything()}
+
+The row groups to which targeting operations are constrained. Can either be
+a series of row group ID values provided in \code{\link[=c]{c()}} or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}.}
 }
 \value{
 A list object with the classes \code{cells_row_groups} and
diff --git a/man/cells_stub.Rd b/man/cells_stub.Rd
index 7888087d0c..7c200cded2 100644
--- a/man/cells_stub.Rd
+++ b/man/cells_stub.Rd
@@ -7,7 +7,17 @@
 cells_stub(rows = everything())
 }
 \arguments{
-\item{rows}{The names of the rows that are to be targeted.}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+The rows to which targeting operations are constrained. The default
+\code{\link[=everything]{everything()}} results in all rows in \code{columns} being formatted.
+Alternatively, we can supply a vector of row captions within \code{\link[=c]{c()}}, a
+vector of row indices, or a select helper function. Examples of select
+helper functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use
+expressions to filter down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_stub} and \code{location_cells}.
diff --git a/man/cells_stub_grand_summary.Rd b/man/cells_stub_grand_summary.Rd
index fdaff81c27..a11ed3009a 100644
--- a/man/cells_stub_grand_summary.Rd
+++ b/man/cells_stub_grand_summary.Rd
@@ -7,7 +7,17 @@
 cells_stub_grand_summary(rows = everything())
 }
 \arguments{
-\item{rows}{The names of the rows that are to be targeted.}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+We can specify which rows should be targeted. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_stub_grand_summary} and
diff --git a/man/cells_stub_summary.Rd b/man/cells_stub_summary.Rd
index a38e353209..0a8472bc02 100644
--- a/man/cells_stub_summary.Rd
+++ b/man/cells_stub_summary.Rd
@@ -7,9 +7,28 @@
 cells_stub_summary(groups = everything(), rows = everything())
 }
 \arguments{
-\item{groups}{The names of the groups that are to be targeted.}
+\item{groups}{\emph{Specification of row group IDs}
 
-\item{rows}{The names of the rows that are to be targeted.}
+\verb{<row-group-targeting expression>} --- \emph{default:} \code{everything()}
+
+The row groups to which targeting operations are constrained. Can either be
+a series of row group ID values provided in \code{\link[=c]{c()}} or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{groups}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_stub_summary} and
diff --git a/man/cells_summary.Rd b/man/cells_summary.Rd
index a594d249cb..9746189afd 100644
--- a/man/cells_summary.Rd
+++ b/man/cells_summary.Rd
@@ -11,11 +11,39 @@ cells_summary(
 )
 }
 \arguments{
-\item{groups}{The names of the groups that the summary rows reside in.}
+\item{groups}{\emph{Specification of row group IDs}
 
-\item{columns}{The names of the columns that are to be targeted.}
+\verb{<row-group-targeting expression>} --- \emph{default:} \code{everything()}
 
-\item{rows}{The names of the rows that are to be targeted.}
+The row groups to which targeting operations are constrained. This aids in
+targeting the summary rows that reside in certain row groups. Can either be
+a series of row group ID values provided in \code{\link[=c]{c()}} or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which targeting operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 }
 \value{
 A list object with the classes \code{cells_summary} and \code{location_cells}.
diff --git a/man/cells_title.Rd b/man/cells_title.Rd
index 775254f119..6328854e28 100644
--- a/man/cells_title.Rd
+++ b/man/cells_title.Rd
@@ -7,9 +7,12 @@
 cells_title(groups = c("title", "subtitle"))
 }
 \arguments{
-\item{groups}{We can either specify \code{"title"}, \code{"subtitle"}, or both (the
-default) in a vector to target the title element, the subtitle element, or
-both elements.}
+\item{groups}{\emph{Specification of groups}
+
+\verb{mult-kw:[title|subtitle]} --- \emph{default:} \code{c("title", "subtitle")}
+
+We can either specify \code{"title"}, \code{"subtitle"}, or both (the default) in a
+vector to target the title element, the subtitle element, or both elements.}
 }
 \value{
 A list object of classes \code{cells_title} and \code{location_cells}.
diff --git a/man/cols_align.Rd b/man/cols_align.Rd
index a676b0d00e..0311ee8b22 100644
--- a/man/cols_align.Rd
+++ b/man/cols_align.Rd
@@ -11,17 +11,32 @@ cols_align(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{align}{The alignment type. This can be any of \code{"center"}, \code{"left"}, or
-\code{"right"} for center-, left-, or right-alignment. Alternatively, the
-\code{"auto"} option (the default), will automatically align values in columns
-according to the data type (see the Details section for specifics on which
-alignments are applied).}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{columns}{The columns for which the alignment should be applied. By
-default this is set to \code{everything()} which means that the chosen alignment
-affects all columns.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{align}{\emph{Alignment type}
+
+\verb{singl-kw:[auto|left|center|right]} --- \emph{default:} \code{"auto"}
+
+This can be any of \code{"center"}, \code{"left"}, or \code{"right"} for center-, left-,
+or right-alignment. Alternatively, the \code{"auto"} option (the default), will
+automatically align values in columns according to the data type (see the
+Details section for specifics on which alignments are applied).}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the alignment should be applied. Can either be a
+series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. By default this is set to \code{\link[=everything]{everything()}}
+which means that the chosen alignment affects all columns.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_align_decimal.Rd b/man/cols_align_decimal.Rd
index 79a9946123..8f5d8e4a70 100644
--- a/man/cols_align_decimal.Rd
+++ b/man/cols_align_decimal.Rd
@@ -7,24 +7,44 @@
 cols_align_decimal(data, columns = everything(), dec_mark = ".", locale = NULL)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{columns}{The columns for which the alignment should be applied. By
-default this is set to \code{everything()} which means that the chosen alignment
-affects all columns.}
-
-\item{dec_mark}{The character used as a decimal mark in the numeric values to
-be aligned. If a locale value was used when formatting the numeric values
-then \code{locale} is better to use and it will override any value here in
-\code{dec_mark}.}
-
-\item{locale}{An optional locale ID that can be used to obtain the type of
-decimal mark used in the numeric values to be aligned. Examples include
-\code{"en"} for English (United States) and \code{"fr"} for French (France). The use
-of a valid locale ID will override any value provided in \code{dec_mark}. We can
-use the \code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the
-locales that are supported. Any \code{locale} value provided here will override
-any global locale setting performed in \code{\link[=gt]{gt()}}'s own \code{locale} argument.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which decimal alignment should be applied. Can either be a
+series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. By default this is set to \code{\link[=everything]{everything()}}
+which means that decimal alignment will be attempted on all columns.}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The character used as a decimal mark in the numeric values to be aligned.
+If a locale value was used when formatting the numeric values then \code{locale}
+is better to use and it will override any value here in \code{dec_mark}.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used to obtain the type of
+decimal mark used in the numeric values to be aligned (according to the
+locale's formatting rules). Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_hide.Rd b/man/cols_hide.Rd
index 3ec5707e45..c55905863a 100644
--- a/man/cols_hide.Rd
+++ b/man/cols_hide.Rd
@@ -7,10 +7,22 @@
 cols_hide(data, columns)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to hide from the output display table. Values
-provided that do not correspond to column names will be disregarded.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to hide in the output display table. Can either be a series of
+column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_label.Rd b/man/cols_label.Rd
index dc2ffc7ceb..a4d0c3bb37 100644
--- a/man/cols_label.Rd
+++ b/man/cols_label.Rd
@@ -7,24 +7,39 @@
 cols_label(.data, ..., .list = list2(...), .fn = NULL)
 }
 \arguments{
-\item{.data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{...}{Expressions for the assignment of column labels for the table
-columns in \code{.data}. Two-sided formulas (e.g., \verb{<LHS> ~ <RHS>}) can be used,
-where the left-hand side corresponds to selections of columns and the
-right-hand side evaluates to single-length values for the label to apply.
-Column names should be enclosed in \code{\link[=c]{c()}}. Select helpers like
-\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and
-\code{\link[=everything]{everything()}} can be used in the LHS. Named arguments are also valid as
-input for simple mappings of column name to label text; they should be of
-the form \verb{<column name> = <label>}. Subsequent expressions that operate on
-the columns assigned previously will result in overwriting column width
-values.}
-
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
-
-\item{.fn}{An option to specify a function that will be applied to all of the
-provided label values.}
+\item{.data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Column label assignments}
+
+\verb{<multiple expressions>} --- \strong{required} (or, use \code{.list})
+
+Expressions for the assignment of column labels for the table columns in
+\code{.data}. Two-sided formulas (e.g., \verb{<LHS> ~ <RHS>}) can be used, where the
+left-hand side corresponds to selections of columns and the right-hand side
+evaluates to single-length values for the label to apply. Column names
+should be enclosed in \code{\link[=c]{c()}}. Select helpers like \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and \code{\link[=everything]{everything()}}
+can be used in the LHS. Named arguments are also valid as input for simple
+mappings of column name to label text; they should be of the form \verb{<column name> = <label>}. Subsequent expressions that operate on the columns
+assigned previously will result in overwriting column width values.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- \strong{required} (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
+
+\item{.fn}{\emph{Function to apply}
+
+\code{function} --- \emph{default:} \code{NULL} (\code{optional})
+
+An option to specify a function that will be applied to all of the provided
+label values.}
 }
 \value{
 An object of class \code{gt_tbl}.
@@ -47,7 +62,7 @@ continue to refer to columns by their original column names. Column names in
 a tibble or data frame must be unique whereas column labels in \strong{gt} have
 no requirement for uniqueness (which is useful for labeling columns as, say,
 measurement units that may be repeated several times---usually under
-different spanner column labels). Thus, we can still easily distinguish
+different spanner labels). Thus, we can still easily distinguish
 between columns in other \strong{gt} function calls (e.g., in all of the
 \verb{fmt*()} functions) even though we may lose distinguishability in column
 labels once they have been relabeled.
@@ -128,14 +143,13 @@ will be applied to each label defined in the \code{cols_label()} call).
 Using a subset of the \code{\link{towny}} dataset, we can create an interesting \strong{gt}
 table. First, only certain columns are selected from the dataset, some
 filtering of rows is done, rows are sorted, and then only the first 10 rows
-are kept. When introduced to \code{\link[=gt]{gt()}}, we apply some spanner column labels
-through two calls of \code{\link[=tab_spanner]{tab_spanner()}} all the table's columns. Below those
-spanners, we want to label the columns by the years of interest. Using
-\code{cols_label()} and select expressions on the left side of the formulas, we
-can easily relabel multiple columns with common label text. Note that we
-cannot use an \code{=} sign in any of the expressions within \code{cols_label()};
-because the left-hand side is not a single column name, we must use formula
-syntax (i.e., with the \code{~}).
+are kept. When introduced to \code{\link[=gt]{gt()}}, we apply some spanner labels through two
+calls of \code{\link[=tab_spanner]{tab_spanner()}} all the table's columns. Below those spanners, we
+want to label the columns by the years of interest. Using \code{cols_label()} and
+select expressions on the left side of the formulas, we can easily relabel
+multiple columns with common label text. Note that we cannot use an \code{=} sign
+in any of the expressions within \code{cols_label()}; because the left-hand side
+is not a single column name, we must use formula syntax (i.e., with the \code{~}).
 
 \if{html}{\out{<div class="sourceCode r">}}\preformatted{towny |>
   dplyr::select(
diff --git a/man/cols_label_with.Rd b/man/cols_label_with.Rd
index 1e6fd92c90..c264ae3eec 100644
--- a/man/cols_label_with.Rd
+++ b/man/cols_label_with.Rd
@@ -7,16 +7,31 @@
 cols_label_with(data, columns = everything(), fn)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to which the function or function call in
-\code{fn} should be applied. By default this is set as \code{everything()} which
-select every column in the table.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{fn}{The function or function call to be applied to the column labels.
-This can take the form of a bare function (e.g., \code{tools::toTitleCase}), a
-function call as a RHS formula (e.g., \code{~ tools::toTitleCase(.)}), or an
-anonymous function as in \code{function(x) tools::toTitleCase(x)}.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the column-labeling operations should be applied. Can
+either be a series of column names provided in \code{\link[=c]{c()}}, a vector of column
+indices, or a select helper function. Examples of select helper functions
+include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
+\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{fn}{\emph{Function to apply}
+
+\verb{function|formula} --- \strong{required}
+
+The function or function call to be applied to the column labels. This can
+take the form of a bare function (e.g., \code{tools::toTitleCase}), a function
+call as a RHS formula (e.g., \code{~ tools::toTitleCase(.)}), or an anonymous
+function as in \code{function(x) tools::toTitleCase(x)}.}
 }
 \value{
 An object of class \code{gt_tbl}.
@@ -39,13 +54,13 @@ function (e.g., \code{function(x) tools::toTitleCase(x)}).
 
 It's important to note that while columns can be freely relabeled, we
 continue to refer to columns by their original column names. Column names in
-a tibble or data frame must be unique whereas column labels in \strong{gt} have
-no requirement for uniqueness (which is useful for labeling columns as, say,
+a tibble or data frame must be unique whereas column labels in \strong{gt} have no
+requirement for uniqueness (which is useful for labeling columns as, say,
 measurement units that may be repeated several times---usually under
-different spanner column labels). Thus, we can still easily distinguish
-between columns in other \strong{gt} function calls (e.g., in all of the
-\verb{fmt*()} functions) even though we may lose distinguishability in column
-labels once they have been relabeled.
+different spanner labels). Thus, we can still easily distinguish between
+columns in other \strong{gt} function calls (e.g., in all of the \verb{fmt*()}
+functions) even though we may lose distinguishability in column labels once
+they have been relabeled.
 }
 
 \section{Examples}{
diff --git a/man/cols_merge.Rd b/man/cols_merge.Rd
index 22af1bfc3c..520554b057 100644
--- a/man/cols_merge.Rd
+++ b/man/cols_merge.Rd
@@ -13,33 +13,60 @@ cols_merge(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{columns}{The columns that will participate in the merging process. The
-first column name provided will be the target column (i.e., undergo
-mutation) and the other columns will serve to provide input.}
-
-\item{hide_columns}{Any column names provided here will have their state
-changed to \code{hidden} (via internal use of \code{\link[=cols_hide]{cols_hide()}} if they aren't
-already hidden. This is convenient if the shared purpose of these specified
-columns is only to provide string input to the target column. To suppress
-any hiding of columns, \code{FALSE} can be used here.}
-
-\item{rows}{Rows that will participate in the merging process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} undergoing
-merging. Alternatively, we can supply a vector of row identifiers within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use a standalone predicate expression to filter down to the
-rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{pattern}{A formatting pattern that specifies the arrangement of the
-\code{column} values and any string literals. The pattern uses numbers (within
-\code{{ }}) that correspond to the indices of columns provided in \code{columns}. If
-two columns are provided in \code{columns} and we would like to combine the cell
-data onto the first column, \code{"{1} {2}"} could be used. If a pattern isn't
-provided then a space-separated pattern that includes all \code{columns} will be
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The columns for which the merging operations should be applied. The first
+column resolved will be the target column (i.e., undergo mutation) and the
+other columns will serve to provide input. Can either be a series of column
+names provided in \code{\link[=c]{c()}}, a vector of column indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}. A vector is recommended because in that case we are
+absolutely certain about the order of columns, and, that order information
+is needed for this and other arguments.}
+
+\item{hide_columns}{\emph{Subset of \code{columns} to hide}
+
+\verb{<column-targeting expression>|FALSE} --- \emph{default:} \code{columns[-1]}
+
+Any column names provided here will have their state changed to \code{hidden}
+(via internal use of \code{\link[=cols_hide]{cols_hide()}}) if they aren't already hidden. This is
+convenient if the shared purpose of these specified columns is only to
+provide string input to the target column. To suppress any hiding of
+columns, \code{FALSE} can be used here.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+participate in the merging process. The default \code{\link[=everything]{everything()}} results in
+all rows in \code{columns} being formatted. Alternatively, we can supply a
+vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{pattern}{\emph{Formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A formatting pattern that specifies the arrangement of the \code{columns} values
+and any string literals. The pattern uses numbers (within \code{{ }}) that
+correspond to the indices of columns provided in \code{columns}. If two columns
+are provided in \code{columns} and we would like to combine the cell data onto
+the first column, \code{"{1} {2}"} could be used. If a pattern isn't provided
+then a space-separated pattern that includes all \code{columns} will be
 generated automatically. Further details are provided in the \emph{How the
 \code{pattern} works} section.}
 }
diff --git a/man/cols_merge_n_pct.Rd b/man/cols_merge_n_pct.Rd
index 8f2fa7df3e..78e968b345 100644
--- a/man/cols_merge_n_pct.Rd
+++ b/man/cols_merge_n_pct.Rd
@@ -7,26 +7,53 @@
 cols_merge_n_pct(data, col_n, col_pct, rows = everything(), autohide = TRUE)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{col_n}{A column that contains values for the count component.}
-
-\item{col_pct}{A column that contains values for the percentage component.
-This column should be formatted such that percentages are displayed (e.g.,
-with \code{fmt_percent()}).}
-
-\item{rows}{Rows that will participate in the merging process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} undergoing
-merging. Alternatively, we can supply a vector of row identifiers within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use a standalone predicate expression to filter down to the
-rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{autohide}{An option to automatically hide the column specified as
-\code{col_pct}. Any columns with their state changed to hidden will behave
-the same as before, they just won't be displayed in the finalized table.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{col_n}{\emph{Column to target for counts}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The column that contains values for the count component. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here.}
+
+\item{col_pct}{\emph{Column to target for percentages}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The column that contains values for the percentage component. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here. This column should
+be formatted such that percentages are displayed (e.g., with
+\code{fmt_percent()}).}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+participate in the merging process. The default \code{\link[=everything]{everything()}} results in
+all rows in \code{columns} being formatted. Alternatively, we can supply a
+vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{autohide}{\emph{Automatic hiding of the \code{col_pct} column}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to automatically hide the column specified as \code{col_pct}. Any
+columns with their state changed to hidden will behave the same as before,
+they just won't be displayed in the finalized table.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_merge_range.Rd b/man/cols_merge_range.Rd
index 76c4bf472e..0ca3957cb3 100644
--- a/man/cols_merge_range.Rd
+++ b/man/cols_merge_range.Rd
@@ -14,28 +14,59 @@ cols_merge_range(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{col_begin}{A column that contains values for the start of the range.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{col_end}{A column that contains values for the end of the range.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{rows}{Rows that will participate in the merging process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} undergoing
-merging. Alternatively, we can supply a vector of row identifiers within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use a standalone predicate expression to filter down to the
-rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+\item{col_begin}{\emph{Column to target for beginning of range}
 
-\item{sep}{The separator text that indicates the values are ranged. The
-default value of \code{"--"} indicates that an en dash will be used for the
-range separator. Using \code{"---"} will be taken to mean that an em dash should
-be used. Should you want these special symbols to be taken literally, they
-can be supplied within the base \code{\link[=I]{I()}} function.}
+\verb{<column-targeting expression>} --- \strong{required}
 
-\item{autohide}{An option to automatically hide the column specified as
+The column that contains values for the start of the range. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here.}
+
+\item{col_end}{\emph{Column to target for end of range}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The column that contains values for the end of the range. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+participate in the merging process. The default \code{\link[=everything]{everything()}} results in
+all rows in \code{columns} being formatted. Alternatively, we can supply a
+vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{sep}{\emph{Separator text for ranges}
+
+\verb{scalar<character>} --- \emph{default:} \code{"--"}
+
+The separator text that indicates the values are ranged. The default value
+of \code{"--"} will be transformed to an en dash for the range separator. Using
+\code{"---"} will be taken to mean that an em dash should be used. Should you
+want these special symbols to be taken literally, they can be supplied
+within the base \code{\link[=I]{I()}} function.}
+
+\item{autohide}{\emph{Automatic hiding of the \code{col_end} column}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to automatically hide the column specified as
 \code{col_end}. Any columns with their state changed to hidden will behave
 the same as before, they just won't be displayed in the finalized table.}
 }
diff --git a/man/cols_merge_uncert.Rd b/man/cols_merge_uncert.Rd
index 7e1117ad78..1a3db94f47 100644
--- a/man/cols_merge_uncert.Rd
+++ b/man/cols_merge_uncert.Rd
@@ -14,39 +14,65 @@ cols_merge_uncert(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{col_val}{A single column name that contains the base values. This is
-the column where values will be mutated.}
-
-\item{col_uncert}{Either one or two column names that contain the uncertainty
-values. The most common case involves supplying a single column with
-uncertainties; these values will be combined with those in \code{col_val}. Less
-commonly, lower and upper uncertainty bounds may be different. For that
-case two columns (representing lower and upper uncertainty values away from
-\code{col_val}, respectively) should be provided. Since we often don't want the
-uncertainty value columns in the output table, we can automatically hide
-any \code{col_uncert} columns through the \code{autohide} option.}
-
-\item{rows}{Rows that will participate in the merging process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} undergoing
-merging. Alternatively, we can supply a vector of row identifiers within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use a standalone predicate expression to filter down to the
-rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{sep}{The separator text that contains the uncertainty mark for a single
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{col_val}{\emph{Column to target for base values}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The column that contains values for the start of the range. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here.}
+
+\item{col_uncert}{\emph{Column or columns to target for uncertainty values}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The most common case involves supplying a single column with uncertainties;
+these values will be combined with those in \code{col_val}. Less commonly, the
+lower and upper uncertainty bounds may be different. For that case, two
+columns representing the lower and upper uncertainty values away from
+\code{col_val}, respectively, should be provided. While select helper functions
+such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for column targeting,
+it's recommended that one or two column names be explicitly provided in a
+vector.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+participate in the merging process. The default \code{\link[=everything]{everything()}} results in
+all rows in \code{columns} being formatted. Alternatively, we can supply a
+vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{sep}{\emph{Separator text for uncertainties}
+
+\verb{scalar<character>} --- \emph{default:} \code{" +/- "}
+
+The separator text that contains the uncertainty mark for a single
 uncertainty value. The default value of \code{" +/- "} indicates that an
 appropriate plus/minus mark will be used depending on the output context.
 Should you want this special symbol to be taken literally, it can be
 supplied within the \code{\link[=I]{I()}} function.}
 
-\item{autohide}{An option to automatically hide any columns specified in
-\code{col_uncert}. Any columns with their state changed to 'hidden' will behave
-the same as before, they just won't be displayed in the finalized table.
-By default, this is set to \code{TRUE}.}
+\item{autohide}{\emph{Automatic hiding of the \code{col_uncert} column(s)}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to automatically hide any columns specified in \code{col_uncert}. Any
+columns with their state changed to 'hidden' will behave the same as
+before, they just won't be displayed in the finalized table.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_move.Rd b/man/cols_move.Rd
index 07c7c53252..8b8eb8239b 100644
--- a/man/cols_move.Rd
+++ b/man/cols_move.Rd
@@ -7,13 +7,33 @@
 cols_move(data, columns, after)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to move to as a group to a different
-position. The order of the remaining columns will be preserved.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{after}{A column name used to anchor the insertion of the moved columns.
-All of the moved columns will be placed to the right of this column.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the moving operations should be applied. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. The columns move as a group to a
+different position. The order of the remaining columns will be preserved.}
+
+\item{after}{\emph{Column used as anchor}
+
+\verb{<column-targeting expression>} --- \strong{required}
+
+The column used to anchor the insertion of the moved columns. All of the
+moved columns will be placed to the right of this column. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+column targeting, it's recommended that a single column name be used. This
+is to ensure that exactly one column is provided here.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_move_to_end.Rd b/man/cols_move_to_end.Rd
index 473c33f970..c52fb79616 100644
--- a/man/cols_move_to_end.Rd
+++ b/man/cols_move_to_end.Rd
@@ -7,11 +7,24 @@
 cols_move_to_end(data, columns)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to move to the right-most side of the table.
-The order in which columns are provided will be preserved (as is the case
-with the remaining columns).}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the moving operations should be applied. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. The columns move as a group to the
+right-most side of the table. The order of the remaining columns will be
+preserved.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_move_to_start.Rd b/man/cols_move_to_start.Rd
index d712b6c2eb..d58ae7e47d 100644
--- a/man/cols_move_to_start.Rd
+++ b/man/cols_move_to_start.Rd
@@ -7,11 +7,24 @@
 cols_move_to_start(data, columns)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to move to the left-most side of the table.
-The order in which columns are provided will be preserved (as is the case
-with the remaining columns).}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the moving operations should be applied. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. The columns move as a group to the
+left-most side of the table. The order of the remaining columns will be
+preserved.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_unhide.Rd b/man/cols_unhide.Rd
index ca2d2f2cfe..038aeb5661 100644
--- a/man/cols_unhide.Rd
+++ b/man/cols_unhide.Rd
@@ -7,10 +7,22 @@
 cols_unhide(data, columns)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The column names to unhide from the output display table.
-Values provided that do not correspond to column names will be disregarded.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to unhide in the output display table. Can either be a series
+of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/cols_width.Rd b/man/cols_width.Rd
index 863a29cbcb..9b0f8f93eb 100644
--- a/man/cols_width.Rd
+++ b/man/cols_width.Rd
@@ -7,23 +7,35 @@
 cols_width(.data, ..., .list = list2(...))
 }
 \arguments{
-\item{.data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{...}{Expressions for the assignment of column widths for the table
-columns in \code{.data}. Two-sided formulas (e.g, \verb{<LHS> ~ <RHS>}) can be used,
-where the left-hand side corresponds to selections of columns and the
-right-hand side evaluates to single-length character values in the form
-\verb{\{##\}px} (i.e., pixel dimensions); the \code{\link[=px]{px()}} helper function is best used
-for this purpose. Column names should be enclosed in \code{\link[=c]{c()}}. The
-column-based select helpers \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
-\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and \code{\link[=everything]{everything()}} can be used in the LHS.
-Subsequent expressions that operate on the columns assigned previously will
-result in overwriting column width values (both in the same \code{cols_width()}
-call and across separate calls). All other columns can be assigned a
-default width value by using \code{everything()} on the left-hand
-side.}
-
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
+\item{.data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Column width assignments}
+
+\verb{<multiple expressions>} --- \strong{required} (or, use \code{.list})
+
+Expressions for the assignment of column widths for the table columns in
+\code{.data}. Two-sided formulas (e.g, \verb{<LHS> ~ <RHS>}) can be used, where the
+left-hand side corresponds to selections of columns and the right-hand side
+evaluates to single-length character values in the form \verb{\{##\}px} (i.e.,
+pixel dimensions); the \code{\link[=px]{px()}} helper function is best used for this
+purpose. Column names should be enclosed in \code{\link[=c]{c()}}. The column-based select
+helpers \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
+\code{\link[=one_of]{one_of()}}, and \code{\link[=everything]{everything()}} can be used in the LHS. Subsequent
+expressions that operate on the columns assigned previously will result in
+overwriting column width values (both in the same \code{cols_width()} call and
+across separate calls). All other columns can be assigned a default width
+value by using \code{everything()} on the left-hand side.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- \strong{required} (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/currency.Rd b/man/currency.Rd
index 7f489dc17e..3a3bb2b920 100644
--- a/man/currency.Rd
+++ b/man/currency.Rd
@@ -7,10 +7,18 @@
 currency(..., .list = list2(...))
 }
 \arguments{
-\item{...}{One or more named arguments using output contexts as the names and
+\item{...}{\emph{Currency symbols by output context}
+
+\verb{<named arguments>} --- \strong{required} (or, use \code{.list})
+
+One or more named arguments using output contexts as the names and
 currency symbol text as the values.}
 
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- \strong{required} (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
 }
 \value{
 A list object of class \code{gt_currency}.
diff --git a/man/data_color.Rd b/man/data_color.Rd
index cb8f81f4f0..a18a2ed537 100644
--- a/man/data_color.Rd
+++ b/man/data_color.Rd
@@ -28,95 +28,185 @@ data_color(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{columns, rows}{The columns and rows to which cell data color operations
-are constrained.}
-
-\item{direction}{Should the color computations be performed column-wise or
-row-wise? By default this is set with the \code{"column"} keyword and colors
-will be applied down columns. The alternative option with the \code{"row"}
-keyword ensures that the color mapping works across rows.}
-
-\item{target_columns}{For indirect column coloring treatments, we can supply
-the columns that will receive the styling. The necessary precondition is
-that we must use \code{direction = "column"}. If \code{columns} resolves to a single
-column then we may use one or more columns in \code{target_columns}. If on the
-other hand \code{columns} resolves to multiple columns, then \code{target_columns}
-must resolve to the same multiple.}
-
-\item{method}{A method for computing color based on the data within body
-cells. Can be \code{"auto"} (the default), \code{"numeric"}, \code{"bin"}, \code{"quantile"},
-or \code{"factor"}. The \code{"auto"} method will automatically choose the
-\code{"numeric"} method for numerical input data or the \code{"factor"} method for
-any non-numeric inputs.}
-
-\item{palette}{A vector of color names, the name of an \strong{RColorBrewer}
-palette, the name of a \strong{viridis} palette, or a discrete palette
-accessible from the \strong{paletteer} package using the \verb{<package>::<palette>}
-syntax (e.g., \code{"wesanderson::IsleofDogs1"}). If providing a vector of
-colors as a palette, each color value provided must either be a color name
-(Only R/X11 color names or CSS 3.0 color names) or a hexadecimal string in
-the form of \code{"#RRGGBB"} or \code{"#RRGGBBAA"}. If nothing is provided here, the
-default R color palette is used (i.e., the colors from \code{palette()}).}
-
-\item{domain}{The possible values that can be mapped. For the \code{"numeric"} and
-\code{"bin"} methods, this can be a numeric range specified with a length of two
-vector. Representative numeric data is needed for the \code{"quantile"} method
-and categorical data must be used for the \code{"factor"} method. If \code{NULL} (the
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which cell data color operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for cell data color operations. The default
+\code{\link[=everything]{everything()}} results in all rows in \code{columns} being formatted.
+Alternatively, we can supply a vector of row captions within \code{\link[=c]{c()}}, a
+vector of row indices, or a select helper function. Examples of select
+helper functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use
+expressions to filter down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{direction}{\emph{Color computation direction}
+
+\verb{singl-kw:[column|row]} --- \emph{default:} \code{"column"}
+
+Should the color computations be performed column-wise or row-wise? By
+default this is set with the \code{"column"} keyword and colors will be applied
+down columns. The alternative option with the \code{"row"} keyword ensures that
+the color mapping works across rows.}
+
+\item{target_columns}{\emph{Indirect columns to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{NULL} \code{optional}
+
+For indirect column coloring treatments, we can supply the columns that
+will receive the styling. The necessary precondition is that we must use
+\code{direction = "column"}. If \code{columns} resolves to a single column then we
+may use one or more columns in \code{target_columns}. If on the other hand
+\code{columns} resolves to multiple columns, then \code{target_columns} must resolve
+to the same multiple.}
+
+\item{method}{\emph{Color computation method}
+
+\verb{singl-kw:[auto|numeric|bin|quantile|factor]} --- \emph{default:} \code{"auto"}
+
+A method for computing color based on the data within body cells. Can be
+\code{"auto"} (the default), \code{"numeric"}, \code{"bin"}, \code{"quantile"}, or \code{"factor"}.
+The \code{"auto"} method will automatically choose the \code{"numeric"} method for
+numerical input data or the \code{"factor"} method for any non-numeric inputs.}
+
+\item{palette}{\emph{Color palette}
+
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A vector of color names, the name of an \strong{RColorBrewer} palette, the name
+of a \strong{viridis} palette, or a discrete palette accessible from the
+\strong{paletteer} package using the \verb{<package>::<palette>} syntax (e.g.,
+\code{"wesanderson::IsleofDogs1"}). If providing a vector of colors as a
+palette, each color value provided must either be a color name (Only R/X11
+color names or CSS 3.0 color names) or a hexadecimal string in the form of
+\code{"#RRGGBB"} or \code{"#RRGGBBAA"}. If nothing is provided here, the default R
+color palette is used (i.e., the colors from \code{palette()}).}
+
+\item{domain}{\emph{Value domain}
+
+\verb{vector<numeric|integer|character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The possible values that can be mapped. For the \code{"numeric"} and \code{"bin"}
+methods, this can be a numeric range specified with a length of two vector.
+Representative numeric data is needed for the \code{"quantile"} method and
+categorical data must be used for the \code{"factor"} method. If \code{NULL} (the
 default value), the values in each column or row (depending on \code{direction})
 value will represent the domain.}
 
-\item{bins}{For \code{method = "bin"} this can either be a numeric vector of two
-or more unique cut points, or, a single numeric value (greater than or
-equal to \code{2}) giving the number of intervals into which the domain values
-are to be cut. By default, this is \code{8}.}
+\item{bins}{\emph{Specification of bin number}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{8}
 
-\item{quantiles}{For \code{method = "quantile"} this is the number of equal-size
-quantiles to use. By default, this is set to \code{4}.}
+For \code{method = "bin"} this can either be a numeric vector of two or more
+unique cut points, or, a single numeric value (greater than or equal to
+\code{2}) giving the number of intervals into which the domain values are to be
+cut. By default, this is \code{8}.}
 
-\item{levels}{For \code{method = "factor"} this allows for an alternate way of
-specifying levels. If anything is provided here then any value supplied to
-\code{domain} will be ignored. This should be a character vector of unique
-values.}
+\item{quantiles}{\emph{Specification of quantile number}
 
-\item{ordered}{For \code{method = "factor"}, setting this to \code{TRUE} means that the
-vector supplied to \code{domain} will be treated as being in the correct order
-if that vector needs to be coerced to a factor. By default, this is
-\code{FALSE}.}
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{4}
 
-\item{na_color}{The color to use for missing values. By default (with
-\code{na_color = NULL}) gray, \code{"#808080"}, will be used.}
+For \code{method = "quantile"} this is the number of equal-size quantiles to
+use. By default, this is set to \code{4}.}
 
-\item{alpha}{An optional, fixed alpha transparency value that will be applied
-to all of the \code{colors} provided (regardless of whether a color palette was
-directly supplied or generated through a color mapping function).}
+\item{levels}{\emph{Specification of factor levels}
 
-\item{reverse}{Should the colors computed operate in reverse order?
-If \code{TRUE} then colors that normally change from red to blue will change in
-the opposite direction. By default, this is \code{FALSE}.}
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{fn}{A color-mapping function. The function should be able to take a
-vector of data values as input and return an equal-length vector of color
-values. The \verb{col_*()} functions provided in the \strong{scales} package (i.e.,
+For \code{method = "factor"} this allows for an alternate way of specifying
+levels. If anything is provided here then any value supplied to \code{domain}
+will be ignored. This should be a character vector of unique values.}
+
+\item{ordered}{\emph{Use an ordered factor}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+For \code{method = "factor"}, setting this to \code{TRUE} means that the vector
+supplied to \code{domain} will be treated as being in the correct order if that
+vector needs to be coerced to a factor. By default, this is \code{FALSE}.}
+
+\item{na_color}{\emph{Default color for \code{NA} values}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The color to use for missing values. By default (with \code{na_color = NULL}),
+the color gray (\code{"#808080"}) will be used. This option has no effect if
+providing a color-mapping function to \code{fn}.}
+
+\item{alpha}{\emph{Transparency value}
+
+\verb{scalar<numeric|integer>(0>=val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional, fixed alpha transparency value that will be applied to all of
+the \code{colors} provided (regardless of whether a color palette was directly
+supplied or generated through a color mapping function).}
+
+\item{reverse}{\emph{Reverse order of computed colors}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the colors computed operate in the reverse order? If \code{TRUE} then
+colors that normally change from red to blue will change in the opposite
+direction.}
+
+\item{fn}{\emph{Color-mapping function}
+
+\code{function} --- \emph{default:} \code{NULL} (\code{optional})
+
+A color-mapping function. The function should be able to take a vector of
+data values as input and return an equal-length vector of color values. The
+\verb{col_*()} functions provided in the \strong{scales} package (i.e.,
 \code{\link[scales:col_numeric]{scales::col_numeric()}}, \code{\link[scales:col_numeric]{scales::col_bin()}}, and \code{\link[scales:col_numeric]{scales::col_factor()}})
 can be invoked here with options, as those functions themselves return a
 color-mapping function.}
 
-\item{apply_to}{Which style element should the colors be applied to? Options
-include the cell background (the default, given as \code{"fill"}) or the cell
-text (\code{"text"}).}
+\item{apply_to}{\emph{How to apply color}
+
+\verb{singl-kw:[fill|text]} --- \emph{default:} \code{"fill"}
+
+Which style element should the colors be applied to? Options include the
+cell background (the default, given as \code{"fill"}) or the cell text
+(\code{"text"}).}
+
+\item{autocolor_text}{\emph{Automatically recolor text}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to let \strong{gt} modify the coloring of text within cells undergoing
+background coloring. This will result in better text-to-background color
+contrast. By default, this is set to \code{TRUE}.}
+
+\item{contrast_algo}{\emph{Color contrast algorithm choice}
+
+\verb{singl-kw:[apca|wcag]} --- \emph{default:} \code{"apca"}
+
+The color contrast algorithm to use when \code{autocolor_text = TRUE}. By
+default this is \code{"apca"} (Accessible Perceptual Contrast Algorithm) and the
+alternative to this is \code{"wcag"} (Web Content Accessibility Guidelines).}
 
-\item{autocolor_text}{An option to let \strong{gt} modify the coloring of text
-within cells undergoing background coloring. This will result in better
-text-to-background color contrast. By default, this is set to \code{TRUE}.}
+\item{colors}{\emph{\link{Deprecated} Color mapping function}
 
-\item{contrast_algo}{The color contrast algorithm to use when
-\code{autocolor_text = TRUE}. By default this is \code{"apca"} (Accessible Perceptual
-Contrast Algorithm) and the alternative to this is \code{"wcag"} (Web Content
-Accessibility Guidelines).}
+\code{function} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{colors}{Deprecated. Use the \code{fn} argument instead to provide a
+This argument is deprecated. Use the \code{fn} argument instead to provide a
 \strong{scales}-based color-mapping function. If providing a palette, use the
 \code{palette} argument.}
 }
diff --git a/man/escape_latex.Rd b/man/escape_latex.Rd
index 1eda57fcfa..29e0a5ab74 100644
--- a/man/escape_latex.Rd
+++ b/man/escape_latex.Rd
@@ -7,8 +7,11 @@
 escape_latex(text)
 }
 \arguments{
-\item{text}{A character vector containing the text that is to be
-LaTeX-escaped.}
+\item{text}{\emph{LaTeX text}
+
+\verb{vector<character>} --- \strong{required}
+
+A character vector containing the text that is to be LaTeX-escaped.}
 }
 \value{
 A character vector.
diff --git a/man/extract_cells.Rd b/man/extract_cells.Rd
index 0f24b5af4c..04ede2b4fc 100644
--- a/man/extract_cells.Rd
+++ b/man/extract_cells.Rd
@@ -12,27 +12,43 @@ extract_cells(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{columns}{The columns containing the cells to extract. Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
-\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
-\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to limit the extraction of cells. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-formatted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for extraction. The default \code{\link[=everything]{everything()}} results in all
+rows in \code{columns} being formatted. Alternatively, we can supply a vector of
+row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A vector of cell data extracted from a \strong{gt} table.
diff --git a/man/extract_summary.Rd b/man/extract_summary.Rd
index 30f5c719a9..d27f20d8cf 100644
--- a/man/extract_summary.Rd
+++ b/man/extract_summary.Rd
@@ -7,7 +7,12 @@
 extract_summary(data)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \value{
 A list of data frames containing summary data.
diff --git a/man/fmt.Rd b/man/fmt.Rd
index c63842a892..d2d119a888 100644
--- a/man/fmt.Rd
+++ b/man/fmt.Rd
@@ -7,27 +7,47 @@
 fmt(data, columns = everything(), rows = everything(), compat = NULL, fns)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{compat}{\emph{Formatting compatibility}
+
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional vector that provides the compatible classes for the formatting.
+By default this is \code{NULL}.}
 
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+\item{fns}{\emph{Formatting functions}
 
-\item{compat}{An optional vector that provides the compatible classes for the
-formatter. By default this is \code{NULL}.}
+\verb{function|list of functions} --- \strong{required}
 
-\item{fns}{Either a single formatting function or a named list of functions.}
+Either a single formatting function or a named list of functions.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_auto.Rd b/man/fmt_auto.Rd
index 51dfa3c632..c2427329dc 100644
--- a/man/fmt_auto.Rd
+++ b/man/fmt_auto.Rd
@@ -14,37 +14,63 @@ fmt_auto(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{scope}{The scope of automatic formatting. By default this includes
-\code{"numbers"}-type values and \code{"currency"}-type values though the scope can
-be reduced to a single type of value to format.}
-
-\item{lg_num_pref}{The preference toward either scientific notation for very
-small and very large values (\code{"sci"}, the default option), or, suffixed
-numbers (\code{"suf"}, for large values only).}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{scope}{\emph{Scope of automatic formatting}
+
+\verb{mult-kw:[numbers|currency]} --- \emph{default:} \code{c("numbers", "currency")}
+
+By default, the function will format both \code{"numbers"}-type values and
+\code{"currency"}-type values though the scope can be reduced to a single type
+of value to format.}
+
+\item{lg_num_pref}{\emph{Large-number preference}
+
+\verb{singl-kw:[sci|suf]} --- \emph{default:} \code{"sci"}
+
+When large numbers are present, there can be a fixed preference toward how
+they are formatted. Choices are scientific notation for very small and very
+large values (\code{"sci"}), or, the use of suffixed numbers (\code{"suf"}, for large
+values only).}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_bins.Rd b/man/fmt_bins.Rd
index 348b80181f..731b811a05 100644
--- a/man/fmt_bins.Rd
+++ b/man/fmt_bins.Rd
@@ -13,31 +13,51 @@ fmt_bins(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{sep}{The separator text that indicates the values are ranged. The
-default value of \code{"--"} indicates that an en dash will be used for the
-range separator. Using \code{"---"} will be taken to mean that an em dash should
-be used. Should you want these special symbols to be taken literally, they
-can be supplied within the base \code{\link[=I]{I()}} function.}
-
-\item{fmt}{Formatting expressions in formula form. The RHS of \code{~} should
-contain a formatting call (e.g.,
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{sep}{\emph{Separator between values}
+
+\verb{scalar<character>} --- \emph{default:} \code{"--"}
+
+The separator text that indicates the values are ranged. The default value
+of \code{"--"} indicates that an en dash will be used for the range separator.
+Using \code{"---"} will be taken to mean that an em dash should be used. Should
+you want these special symbols to be taken literally, they can be supplied
+within the base \code{\link[=I]{I()}} function.}
+
+\item{fmt}{\emph{Formatting expressions}
+
+\verb{<single expression>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional formatting expression in formula form. If used, the RHS of \code{~}
+should contain a formatting call (e.g.,
 \verb{~ fmt_number(., decimals = 3, use_seps = FALSE}).}
 }
 \value{
diff --git a/man/fmt_bytes.Rd b/man/fmt_bytes.Rd
index 40e56d3040..e5d973ab53 100644
--- a/man/fmt_bytes.Rd
+++ b/man/fmt_bytes.Rd
@@ -23,71 +23,140 @@ fmt_bytes(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{standard}{The way to express large byte sizes.}
-
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{1}.}
-
-\item{n_sigfig}{A option to format numbers to \emph{n} significant figures. By
-default, this is \code{NULL} and thus number values will be formatted according
-to the number of decimal places set via \code{decimals}. If opting to format
-according to the rules of significant figures, \code{n_sigfig} must be a number
-greater than or equal to \code{1}. Any values passed to the \code{decimals} and
-\code{drop_trailing_zeros} arguments will be ignored.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive numbers
-(effectively showing a sign for all numbers except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the units. The default of \code{TRUE} uses a space character for separation.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{standard}{\emph{Standard used to express byte sizes}
+
+\verb{singl-kw:[decimal|binary]} --- \emph{default:} \code{"decimal"}
+
+The form of expressing large byte sizes is divided between: (1) decimal
+units (powers of 1000; e.g., \code{"kB"} and \code{"MB"}), and (2) binary units
+(powers of 1024; e.g., \code{"KiB"} and \code{"MiB"}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{1}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}.}
+
+\item{n_sigfig}{\emph{Number of significant figures}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+A option to format numbers to \emph{n} significant figures. By default, this is
+\code{NULL} and thus number values will be formatted according to the number of
+decimal places set via \code{decimals}. If opting to format according to the
+rules of significant figures, \code{n_sigfig} must be a number greater than or
+equal to \code{1}. Any values passed to the \code{decimals} and \code{drop_trailing_zeros}
+arguments will be ignored.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive numbers (effectively showing
+a sign for all numbers except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.}
+
+\item{incl_space}{\emph{Include a space between the value and the units}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option for whether to include a space between the value and the units.
+The default is to use a space character for separation.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_currency.Rd b/man/fmt_currency.Rd
index ac925449dd..d780f81faa 100644
--- a/man/fmt_currency.Rd
+++ b/man/fmt_currency.Rd
@@ -27,24 +27,40 @@ fmt_currency(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{currency}{The currency to use for the numeric value. This input can be
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{currency}{\emph{Currency to use}
+
+\verb{scalar<character>|obj:<gt_currency>} --- \emph{default:} \code{"USD"}
+
+The currency to use for the numeric value. This input can be
 supplied as a 3-letter currency code (e.g., \code{"USD"} for U.S. Dollars,
 \code{"EUR"} for the Euro currency). Use \code{\link[=info_currencies]{info_currencies()}} to get an
 information table with all of the valid currency codes and examples of
@@ -59,90 +75,165 @@ currency, where the string could vary across output contexts. For example,
 using \code{currency(html = "&fnof;", default = "f")} would give us a suitable
 glyph for the Dutch guilder in an HTML output table, and it would simply be
 the letter "f" in all other output contexts). Please note that \code{decimals}
-will default to \code{2} when using the \code{\link[=currency]{currency()}} helper function.
+will default to \code{2} when using the \code{\link[=currency]{currency()}} helper function.}
+
+\item{use_subunits}{\emph{Show or hide currency subunits}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option for whether the subunits portion of a currency value should be
+displayed. For example, with an input value of \code{273.81}, the default
+formatting will produce \code{"$273.81"}. Removing the subunits (with
+\code{use_subunits = FALSE}) will give us \code{"$273"}.}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-If nothing is provided to \code{currency} then \code{"USD"} (U.S. dollars) will be
-used.}
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
 
-\item{use_subunits}{An option for whether the subunits portion of a currency
-value should be displayed. By default, this is \code{TRUE}.}
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
 
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
 
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
+\item{suffixing}{\emph{Specification for large-number suffixing}
 
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
+transformation and \code{TRUE} will apply thousands (\code{"K"}), millions (\code{"M"}),
+billions (\code{"B"}), and trillions (\code{"T"}) suffixes after automatic value
+scaling.
 
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
-transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
-billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
 that any value provided to \code{scale_by} will be ignored.
 
 If using \code{system = "ind"} then the default suffix set provided by
-\code{suffixing = TRUE} will be \code{c(NA, "L", "Cr")}. This doesn't apply suffixes
-to the thousands range, but does express values in lakhs and crores.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{placement}{The placement of the currency symbol. This can be either be
-\code{left} (the default) or \code{right}.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the currency symbol. The default is to not introduce a space character.}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{suffixing = TRUE} will be the equivalent of \code{c(NA, "L", "Cr")}. This
+doesn't apply suffixes to the thousands range, but does express values in
+\emph{lakhs} and \emph{crores}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{placement}{\emph{Currency symbol placement}
+
+\verb{scalar<character>} --- \emph{default:} \code{"left"}
+
+The placement of the currency symbol. This can be either be \code{left} (as
+in \code{"$450"}) or \code{right} (which yields \code{"450$"}).}
+
+\item{incl_space}{\emph{Include a space between the value and the currency symbol}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option for whether to include a space between the value and the currency
+symbol. The default is to not introduce a space character.}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_date.Rd b/man/fmt_date.Rd
index de424c380f..dca9aab411 100644
--- a/man/fmt_date.Rd
+++ b/man/fmt_date.Rd
@@ -14,37 +14,63 @@ fmt_date(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{date_style}{The date style to use. By default this is \code{"iso"} which
-corresponds to ISO 8601 date formatting. The other date styles can be
-viewed using \code{\link[=info_date_style]{info_date_style()}}.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{date_style}{\emph{Predefined style for dates}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=41)} --- \emph{default:} \code{"iso"}
+
+The date style to use. By default this is the short name \code{"iso"} which
+corresponds to ISO 8601 date formatting. There are 41 date styles in total
+and their short names can be viewed using \code{\link[=info_date_style]{info_date_style()}}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_datetime.Rd b/man/fmt_datetime.Rd
index edab441bac..0cb25783d8 100644
--- a/man/fmt_datetime.Rd
+++ b/man/fmt_datetime.Rd
@@ -18,56 +18,99 @@ fmt_datetime(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{date_style}{The date style to use. By default this is \code{"iso"} which
-corresponds to ISO 8601 date formatting. The other date styles can be
-viewed using \code{\link[=info_date_style]{info_date_style()}}.}
-
-\item{time_style}{The time style to use. By default this is \code{"iso"} which
-corresponds to how times are formatted within ISO 8601 datetime values. The
-other time styles can be viewed using \code{\link[=info_time_style]{info_time_style()}}.}
-
-\item{sep}{The separator string to use between the date and time components.
-By default, this is a single space character (\code{" "}). Only used when not
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{date_style}{\emph{Predefined style for dates}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=41)} --- \emph{default:} \code{"iso"}
+
+The date style to use. By default this is the short name \code{"iso"} which
+corresponds to ISO 8601 date formatting. There are 41 date styles in total
+and their short names can be viewed using \code{\link[=info_date_style]{info_date_style()}}.}
+
+\item{time_style}{\emph{Predefined style for times}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=25)} --- \emph{default:} \code{"iso"}
+
+The time style to use. By default this is the short name \code{"iso"} which
+corresponds to how times are formatted within ISO 8601 datetime values.
+There are 25 time styles in total and their short names can be viewed using
+\code{\link[=info_time_style]{info_time_style()}}.}
+
+\item{sep}{\emph{Separator between date and time components}
+
+\verb{scalar<character>} --- \emph{default:} \code{" "}
+
+The separator string to use between the date and time components. By
+default, this is a single space character (\code{" "}). Only used when not
 specifying a \code{format} code.}
 
-\item{format}{An optional formatting string used for generating custom
-dates/times. If used then the arguments governing preset styles
-(\code{date_style} and \code{time_style}) will be ignored in favor of formatting via
-the \code{format} string.}
+\item{format}{\emph{Date/time formatting string}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional formatting string used for generating custom dates/times. If
+used then the arguments governing preset styles (\code{date_style} and
+\code{time_style}) will be ignored in favor of formatting via the \code{format}
+string.}
 
-\item{tz}{The time zone for printing dates/times (i.e., the output). The
+\item{tz}{\emph{Time zone}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The time zone for printing dates/times (i.e., the output). The
 default of \code{NULL} will preserve the time zone of the input data in the
 output. If providing a time zone, it must be one that is recognized by the
 user's operating system (a vector of all valid \code{tz} values can be produced
 with \code{\link[=OlsonNames]{OlsonNames()}}).}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_duration.Rd b/man/fmt_duration.Rd
index 5f540be99d..594aaf2dd4 100644
--- a/man/fmt_duration.Rd
+++ b/man/fmt_duration.Rd
@@ -22,92 +22,150 @@ fmt_duration(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{input_units}{If one or more selected columns contains numeric values, a
-keyword must be provided for \code{input_units} for \strong{gt} to determine how
-those values are to be interpreted in terms of duration. The accepted units
-are: \code{"seconds"}, \code{"minutes"}, \code{"hours"}, \code{"days"}, and \code{"weeks"}.}
-
-\item{output_units}{Controls the output time units. The default, \code{NULL},
-means that \strong{gt} will automatically choose time units based on the input
-duration value. To control which time units are to be considered for output
-(before trimming with \code{trim_zero_units}) we can specify a vector of one or
-more of the following keywords: \code{"weeks"}, \code{"days"}, \code{"hours"},
-\code{"minutes"}, or \code{"seconds"}.}
-
-\item{duration_style}{A choice of four formatting styles for the output
-duration values. With \code{"narrow"} (the default style), duration values will
-be formatted with single letter time-part units (e.g., 1.35 days will be
-styled as \verb{"1d 8h 24m}). With \code{"wide"}, this example value will be expanded
-to \code{"1 day 8 hours 24 minutes"} after formatting. The \code{"colon-sep"} style
-will put days, hours, minutes, and seconds in the \code{"([D]/)[HH]:[MM]:[SS]"}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{input_units}{\emph{Declaration of duration units for numerical values}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+If one or more selected columns contains numeric values (not \code{difftime}
+values, which contain the duration units), a keyword must be provided for
+\code{input_units} for \strong{gt} to determine how those values are to be
+interpreted in terms of duration. The accepted units are: \code{"seconds"},
+\code{"minutes"}, \code{"hours"}, \code{"days"}, and \code{"weeks"}.}
+
+\item{output_units}{\emph{Choice of output units}
+
+\verb{mult-kw:[weeks|days|hours|minutes|seconds]} --- \emph{default:} \code{NULL} (\code{optional})
+
+Controls the output time units. The default, \code{NULL}, means that \strong{gt} will
+automatically choose time units based on the input duration value. To
+control which time units are to be considered for output (before trimming
+with \code{trim_zero_units}) we can specify a vector of one or more of the
+following keywords: \code{"weeks"}, \code{"days"}, \code{"hours"}, \code{"minutes"}, or
+\code{"seconds"}.}
+
+\item{duration_style}{\emph{Style for representing duration values}
+
+\verb{singl-kw:[narrow|wide|colon-sep|iso]} --- \emph{default:} \code{"narrow"}
+
+A choice of four formatting styles for the output duration values. With
+\code{"narrow"} (the default style), duration values will be formatted with
+single letter time-part units (e.g., 1.35 days will be styled as
+\code{"1d 8h 24m"}). With \code{"wide"}, this example value will be expanded to
+\code{"1 day 8 hours 24 minutes"} after formatting. The \code{"colon-sep"} style will
+put days, hours, minutes, and seconds in the \code{"([D]/)[HH]:[MM]:[SS]"}
 format. The \code{"iso"} style will produce a value that conforms to the ISO
 8601 rules for duration values (e.g., 1.35 days will become \code{"P1DT8H24M"}).}
 
-\item{trim_zero_units}{Provides methods to remove output time units that have
-zero values. By default this is \code{TRUE} and duration values that might
-otherwise be formatted as \code{"0w 1d 0h 4m 19s"} with
-\code{trim_zero_units = FALSE} are instead displayed as \code{"1d 4m 19s"}. Aside
-from using \code{TRUE}/\code{FALSE} we could provide a vector of keywords for more
-precise control. These keywords are: (1) \code{"leading"}, to omit all leading
-zero-value time units (e.g., \code{"0w 1d"} -> \code{"1d"}), (2) \code{"trailing"}, to
-omit all trailing zero-value time units (e.g., \code{"3d 5h 0s"} -> \code{"3d 5h"}),
-and \code{"internal"}, which removes all internal zero-value time units (e.g.,
-\code{"5d 0h 33m"} -> \code{"5d 33m"}).}
-
-\item{max_output_units}{If \code{output_units} is \code{NULL}, where the output time
-units are unspecified and left to \strong{gt} to handle, a numeric value
-provided for \code{max_output_units} will be taken as the maximum number of time
-units to display in all output time duration values. By default, this is
-\code{NULL} and all possible time units will be displayed. This option has no
-effect when \code{duration_style = "colon-sep"} (only \code{output_units} can be used
-to customize that type of duration output).}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative value will
-display a minus sign.}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\item{trim_zero_units}{\emph{Trimming of zero values}
+
+\verb{scalar<logical>|mult-kw:[leading|trailing|internal]} --- \emph{default:} \code{TRUE}
+
+Provides methods to remove output time units that have zero values. By
+default this is \code{TRUE} and duration values that might otherwise be
+formatted as \code{"0w 1d 0h 4m 19s"} with \code{trim_zero_units = FALSE} are instead
+displayed as \code{"1d 4m 19s"}. Aside from using \code{TRUE}/\code{FALSE} we could
+provide a vector of keywords for more precise control. These keywords are:
+(1) \code{"leading"}, to omit all leading zero-value time units (e.g., \code{"0w 1d"}
+-> \code{"1d"}), (2) \code{"trailing"}, to omit all trailing zero-value time units
+(e.g., \code{"3d 5h 0s"} -> \code{"3d 5h"}), and \code{"internal"}, which removes all
+internal zero-value time units (e.g., \code{"5d 0h 33m"} -> \code{"5d 33m"}).}
+
+\item{max_output_units}{\emph{Maximum number of time units to display}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+If \code{output_units} is \code{NULL}, where the output time units are unspecified
+and left to \strong{gt} to handle, a numeric value provided for
+\code{max_output_units} will be taken as the maximum number of time units to
+display in all output time duration values. By default, this is \code{NULL} and
+all possible time units will be displayed. This option has no effect when
+\code{duration_style = "colon-sep"} (only \code{output_units} can be used to
+customize that type of duration output).}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. By
+default only negative values will display a minus sign.}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_engineering.Rd b/man/fmt_engineering.Rd
index 3e07ed1bad..ec3604cc9a 100644
--- a/man/fmt_engineering.Rd
+++ b/man/fmt_engineering.Rd
@@ -21,61 +21,120 @@ fmt_engineering(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
 
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.}
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied.}
 
-\item{exp_style}{Style of formatting to use for the engineering notation
-formatting. By default this is \code{"x10n"} but other options include using
-a single letter (e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to
-signal a minimum digit width of one, or \code{"low-ten"} for using a stylized
-\code{"10"} marker.}
+\item{exp_style}{\emph{Style declaration for exponent formatting}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\verb{scalar<character>} --- \emph{default:} \code{"x10n"}
 
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
+Style of formatting to use for the scientific notation formatting. By
+default this is \code{"x10n"} but other options include using a single letter
+(e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to signal a
+minimum digit width of one, or \code{"low-ten"} for using a stylized \code{"10"}
+marker.}
 
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
+\item{pattern}{\emph{Specification of the formatting pattern}
 
-\item{force_sign_m, force_sign_n}{Should the plus sign be shown for positive
-values of the mantissa (first component) or the exponent? This would
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign_m, force_sign_n}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the plus sign be shown for positive values of the mantissa (first
+component, \code{force_sign_m}) or the exponent (\code{force_sign_n})? This would
 effectively show a sign for all values except zero on either of those
 numeric components of the notation. If so, use \code{TRUE} for either one of
 these options. The default for both is \code{FALSE}, where only negative numbers
 will display a sign.}
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_flag.Rd b/man/fmt_flag.Rd
index eb70cf5347..a369981ce2 100644
--- a/man/fmt_flag.Rd
+++ b/man/fmt_flag.Rd
@@ -14,32 +14,56 @@ fmt_flag(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{height}{\emph{Height of flag}
+
+\verb{scalar<character>} --- \emph{default:} \code{"1em"}
 
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+The absolute height of the flag icon in the table cell. By default, this is
+set to \code{"1em"}.}
 
-\item{height}{The absolute height of the flag icon in the table cell. By
-default, this is set to \code{"1em"}.}
+\item{sep}{\emph{Separator between flags}
 
-\item{sep}{In the output of flag icons within a body cell, \code{sep} provides the
+\verb{scalar<character>} --- \emph{default:} \code{" "}
+
+In the output of flag icons within a body cell, \code{sep} provides the
 separator between each icon. By default, this is a single space character
 (\code{" "}).}
 
-\item{use_title}{An option to display a tooltip for the country name when
-hovering over the flag icon. By default this is \code{TRUE}.}
+\item{use_title}{\emph{Display country name on hover}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to display a tooltip for the country name (in English) when
+hovering over the flag icon.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_fraction.Rd b/man/fmt_fraction.Rd
index d5a5c31129..f4a814b976 100644
--- a/man/fmt_fraction.Rd
+++ b/man/fmt_fraction.Rd
@@ -19,65 +19,112 @@ fmt_fraction(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{accuracy}{The type of fractions to generate. This can either be one of
-the keywords \code{"low"}, \code{"med"}, or \code{"high"} (to generate fractions with
-denominators of up to 1, 2, or 3 digits, respectively) or an integer value
-greater than zero to obtain fractions with a fixed denominator (\code{2} yields
-halves, \code{3} is for thirds, \code{4} is quarters, etc.). For the latter option,
-using \code{simplify = TRUE} will simplify fractions where possible (e.g., \code{2/4}
-will be simplified as \code{1/2}). By default, the \code{"low"} option is used.}
-
-\item{simplify}{If choosing to provide a numeric value for \code{accuracy}, the
-option to simplify the fraction (where possible) can be taken with \code{TRUE}
-(the default). With \code{FALSE}, denominators in fractions will be fixed to the
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{accuracy}{\emph{Accuracy of fractions}
+
+\verb{singl-kw:[low|med|high]|scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{"low"}
+
+The type of fractions to generate. This can either be one of the keywords
+\code{"low"}, \code{"med"}, or \code{"high"} (to generate fractions with denominators of
+up to 1, 2, or 3 digits, respectively) or an integer value greater than
+zero to obtain fractions with a fixed denominator (\code{2} yields halves, \code{3}
+is for thirds, \code{4} is quarters, etc.). For the latter option, using
+\code{simplify = TRUE} will simplify fractions where possible (e.g., \code{2/4} will
+be simplified as \code{1/2}). By default, the \code{"low"} option is used.}
+
+\item{simplify}{\emph{Simplify the fraction}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+If choosing to provide a numeric value for \code{accuracy}, the option to
+simplify the fraction (where possible) can be taken with \code{TRUE} (the
+default). With \code{FALSE}, denominators in fractions will be fixed to the
 value provided in \code{accuracy}.}
 
-\item{layout}{For HTML output, the \code{"inline"} layout is the default. This
-layout places the numerals of the fraction on the baseline and uses a
-standard slash character. The \code{"diagonal"} layout will generate fractions
-that are typeset with raised/lowered numerals and a virgule.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\item{layout}{\emph{Layout of fractions in HTML output}
+
+\verb{singl-kw:[inline|diagonal]} --- \emph{default:} \code{"inline"}
+
+For HTML output, the \code{"inline"} layout is the default. This layout places
+the numerals of the fraction on the baseline and uses a standard slash
+character. The \code{"diagonal"} layout will generate fractions that are typeset
+with raised/lowered numerals and a virgule.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_image.Rd b/man/fmt_image.Rd
index 8bd9f64c26..9c07ff8578 100644
--- a/man/fmt_image.Rd
+++ b/man/fmt_image.Rd
@@ -16,37 +16,70 @@ fmt_image(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{height}{\emph{Height of image}
 
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+\verb{scalar<character>} --- \emph{default:} \code{"1em"}
 
-\item{height}{The absolute height of the image in the table cell. By default,
-this is set to \code{"1em"}.}
+The absolute height of the image in the table cell. By default, this is set
+to \code{"1em"}.}
 
-\item{sep}{In the output of images within a body cell, \code{sep} provides the
-separator between each image.}
+\item{sep}{\emph{Separator between images}
 
-\item{path}{An optional path to local image files (this is combined with all
+\verb{scalar<character>} --- \emph{default:} \code{" "}
+
+In the output of images within a body cell, \code{sep} provides the separator
+between each image.}
+
+\item{path}{\emph{Path to image files}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional path to local image files (this is combined with all
 filenames).}
 
-\item{file_pattern}{The pattern to use for mapping input values in the body
-cells to the names of the graphics files.}
+\item{file_pattern}{\emph{File pattern specification}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+The pattern to use for mapping input values in the body cells to the names
+of the graphics files. The string supplied should use \code{"{x}"} in the
+pattern to map filename fragments to input strings.}
+
+\item{encode}{\emph{Use Base64 encoding}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{encode}{The option to always use Base64 encoding for image paths that
-are determined to be local. By default, this is \code{TRUE}.}
+The option to always use Base64 encoding for image paths that are
+determined to be local. By default, this is \code{TRUE}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_index.Rd b/man/fmt_index.Rd
index 1904d5aed0..2fa1a82517 100644
--- a/man/fmt_index.Rd
+++ b/man/fmt_index.Rd
@@ -15,43 +15,72 @@ fmt_index(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{case}{Should resulting index characters be rendered as uppercase
-(\code{"upper"}) or lowercase (\code{"lower"}) letters? By default, this is set to
-\code{"upper"}.}
-
-\item{index_algo}{The indexing algorithm for handling the recycling of the
-index character set. By default, the \code{"repeat"} option is used where
-characters are doubled, tripled, and so on, when moving past the character
-set limit. The alternative is the \code{"excel"} option, where Excel-based
-column naming is adapted and used here (e.g., \verb{[..., Y, Z, AA, AB, ...]}).}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{case}{\emph{Use uppercase or lowercase letters}
+
+\verb{singl-kw:[upper|lower]} --- \emph{default:} \code{"upper"}
+
+Should the resulting index characters be rendered as uppercase (\code{"upper"})
+or lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
+
+\item{index_algo}{\emph{Indexing algorithm}
+
+\verb{singl-kw:[repeat|excel]} --- \emph{default:} \code{"repeat"}
+
+The indexing algorithm handles the recycling of the index character set. By
+default, the \code{"repeat"} option is used where characters are doubled,
+tripled, and so on, when moving past the character set limit. The
+alternative is the \code{"excel"} option, where Excel-based column naming is
+adapted and used here (e.g., \verb{[..., Y, Z, AA, AB, ...]}).}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_integer.Rd b/man/fmt_integer.Rd
index aa200fa16f..3cf7d692f8 100644
--- a/man/fmt_integer.Rd
+++ b/man/fmt_integer.Rd
@@ -20,79 +20,140 @@ fmt_integer(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
-
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
-
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{2M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
+
+\item{suffixing}{\emph{Specification for large-number suffixing}
+
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
+
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{2M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
 transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
 billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
-that any value provided to \code{scale_by} will be ignored.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+that any value provided to \code{scale_by} will be ignored.
+
+If using \code{system = "ind"} then the default suffix set provided by
+\code{suffixing = TRUE} will be the equivalent of \code{c(NA, "L", "Cr")}. This
+doesn't apply suffixes to the thousands range, but does express values in
+\emph{lakhs} and \emph{crores}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_markdown.Rd b/man/fmt_markdown.Rd
index 8514d25772..6880587f76 100644
--- a/man/fmt_markdown.Rd
+++ b/man/fmt_markdown.Rd
@@ -12,27 +12,43 @@ fmt_markdown(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{md_engine}{The engine preference for Markdown rendering. By default,
-this is set to \code{"markdown"} where \strong{gt} will use the \strong{markdown} package
-for Markdown conversion to HTML and LaTeX. The other option is
-\code{"commonmark"} and with that the \strong{commonmark} package will be used.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{md_engine}{\emph{Choice of Markdown engine}
+
+\verb{singl-kw:[markdown|commonmark]} --- \emph{default:} \code{"markdown"}
+
+The engine preference for Markdown rendering. By default, this is set to
+\code{"markdown"} where \strong{gt} will use the \strong{markdown} package for Markdown
+conversion to HTML and LaTeX. The other option is \code{"commonmark"} and with
+that the \strong{commonmark} package will be used.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_missing.Rd b/man/fmt_missing.Rd
index 10a4dfb7d1..6ac609dcf5 100644
--- a/man/fmt_missing.Rd
+++ b/man/fmt_missing.Rd
@@ -12,22 +12,34 @@ fmt_missing(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
 
 \item{missing_text}{The text to be used in place of \code{NA} values in the
 rendered table.}
diff --git a/man/fmt_number.Rd b/man/fmt_number.Rd
index 35e02bafae..ebe7074060 100644
--- a/man/fmt_number.Rd
+++ b/man/fmt_number.Rd
@@ -25,103 +25,187 @@ fmt_number(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
-
-\item{n_sigfig}{A option to format numbers to \emph{n} significant figures. By
-default, this is \code{NULL} and thus number values will be formatted according
-to the number of decimal places set via \code{decimals}. If opting to format
-according to the rules of significant figures, \code{n_sigfig} must be a number
-greater than or equal to \code{1}. Any values passed to the \code{decimals} and
-\code{drop_trailing_zeros} arguments will be ignored.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
-
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
-
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
-transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
-billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{n_sigfig}{\emph{Number of significant figures}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+A option to format numbers to \emph{n} significant figures. By default, this is
+\code{NULL} and thus number values will be formatted according to the number of
+decimal places set via \code{decimals}. If opting to format according to the
+rules of significant figures, \code{n_sigfig} must be a number greater than or
+equal to \code{1}. Any values passed to the \code{decimals} and \code{drop_trailing_zeros}
+arguments will be ignored.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
+
+\item{suffixing}{\emph{Specification for large-number suffixing}
+
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
+
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
+transformation and \code{TRUE} will apply thousands (\code{"K"}), millions (\code{"M"}),
+billions (\code{"B"}), and trillions (\code{"T"}) suffixes after automatic value
+scaling.
+
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
 that any value provided to \code{scale_by} will be ignored.
 
 If using \code{system = "ind"} then the default suffix set provided by
-\code{suffixing = TRUE} will be \code{c(NA, "L", "Cr")}. This doesn't apply suffixes
-to the thousands range, but does express values in lakhs and crores.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{suffixing = TRUE} will be the equivalent of \code{c(NA, "L", "Cr")}. This
+doesn't apply suffixes to the thousands range, but does express values in
+\emph{lakhs} and \emph{crores}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_partsper.Rd b/man/fmt_partsper.Rd
index 65eaa8fbcf..fedb5441a6 100644
--- a/man/fmt_partsper.Rd
+++ b/man/fmt_partsper.Rd
@@ -25,86 +25,163 @@ fmt_partsper(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{to_units}{A keyword that signifies the desired output quantity. This
-can be any from the following set: \code{"per-mille"}, \code{"per-myriad"}, \code{"pcm"},
-\code{"ppm"}, \code{"ppb"}, \code{"ppt"}, or \code{"ppq"}.}
-
-\item{symbol}{The symbol/units to use for the quantity. By default, this is
-set to \code{"auto"} and \strong{gt} will choose the appropriate symbol based on the
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{to_units}{\emph{Output Quantity}
+
+\verb{singl-kw:[per-mille|per-myriad|pcm|ppm|ppb|ppt|ppq]} --- \emph{default:} \code{"per-mille"}
+
+A keyword that signifies the desired output quantity. This can be any from
+the following set: \code{"per-mille"}, \code{"per-myriad"}, \code{"pcm"}, \code{"ppm"},
+\code{"ppb"}, \code{"ppt"}, or \code{"ppq"}.}
+
+\item{symbol}{\emph{Symbol or units to use in output display}
+
+\verb{scalar<character>} --- \emph{default:} \code{"auto"}
+
+The symbol/units to use for the quantity. By default, this is set to
+\code{"auto"} and \strong{gt} will choose the appropriate symbol based on the
 \code{to_units} keyword and the output context. However, this can be changed by
 supplying a string (e.g, using \code{symbol = "ppbV"} when \code{to_units = "ppb"}).}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{scale_values}{Should the values be scaled through multiplication
-according to the keyword set in \code{to_units}? By default this is \code{TRUE} since
-the expectation is that normally values are proportions. Setting to \code{FALSE}
-signifies that the values are already scaled and require only the
-appropriate symbol/units when formatted.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the symbol/units. The default is \code{"auto"} which provides spacing
-dependent on the mark itself. This can be directly controlled by using
-either \code{TRUE} or \code{FALSE}.}
-
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{scale_values}{\emph{Scale input values accordingly}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the values be scaled through multiplication according to the keyword
+set in \code{to_units}? By default this is \code{TRUE} since the expectation is that
+normally values are proportions. Setting to \code{FALSE} signifies that the
+values are already scaled and require only the appropriate symbol/units
+when formatted.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{incl_space}{\emph{Include a space between the value and the symbol/units}
+
+\verb{scalar<character>|scalar<logical>} --- \emph{default:} \code{"auto"}
+
+An option for whether to include a space between the value and the
+symbol/units. The default is \code{"auto"} which provides spacing dependent on
+the mark itself. This can be directly controlled by using either \code{TRUE} or
+\code{FALSE}.}
+
+\item{system}{\emph{Numbering system for grouping separators}
+
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
+
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_passthrough.Rd b/man/fmt_passthrough.Rd
index 5c46d03789..41b939bfff 100644
--- a/man/fmt_passthrough.Rd
+++ b/man/fmt_passthrough.Rd
@@ -13,32 +13,53 @@ fmt_passthrough(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{escape}{An option to escape text according to the final output format
-of the table. For example, if a LaTeX table is to be generated then LaTeX
-escaping would be performed during rendering. By default this is set to
-\code{TRUE} and setting to \code{FALSE} would be useful in the case where text is
-crafted for a specific output format in mind.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{escape}{\emph{Text escaping}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to escape text according to the final output format of the table.
+For example, if a LaTeX table is to be generated then LaTeX escaping would
+be performed during rendering. By default this is set to \code{TRUE} but setting
+as \code{FALSE} would be useful in the case where text is crafted for a specific
+output format in mind.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_percent.Rd b/man/fmt_percent.Rd
index a5805ac148..52338b7590 100644
--- a/man/fmt_percent.Rd
+++ b/man/fmt_percent.Rd
@@ -25,81 +25,158 @@ fmt_percent(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{scale_values}{Should the values be scaled through multiplication by
-100? By default this is \code{TRUE} since the expectation is that normally
-values are proportions. Setting to \code{FALSE} signifies that the values are
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{scale_values}{\emph{Multiply input values by 100}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the values be scaled through multiplication by 100? By default this
+scaling is performed since the expectation is that incoming values are
+usually proportional. Setting to \code{FALSE} signifies that the values are
 already scaled and require only the percent sign when formatted.}
 
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{incl_space}{\emph{Include a space between the value and the \% sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option for whether to include a space between the value and the percent
+sign. The default is to not introduce a space character.}
 
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
+\item{placement}{\emph{Percent sign placement}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\verb{scalar<character>} --- \emph{default:} \code{"right"}
 
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
+This option governs the placement of the percent sign. This can be either
+be \code{right} (the default) or \code{left}.}
 
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
+\item{system}{\emph{Numbering system for grouping separators}
 
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
+\verb{singl-kw:[intl|ind]} --- \emph{default:} \code{"intl"}
 
-\item{incl_space}{An option for whether to include a space between the value
-and the percent sign. The default is to not introduce a space character.}
+The international numbering system (keyword: \code{"intl"}) is widely used and
+its grouping separators (i.e., \code{sep_mark}) are always separated by three
+digits. The alternative system, the Indian numbering system (keyword:
+\code{"ind"}), uses grouping separators that correspond to thousand, lakh,
+crore, and higher quantities.}
 
-\item{placement}{The placement of the percent sign. This can be either be
-\code{right} (the default) or \code{left}.}
+\item{locale}{\emph{Locale identifier}
 
-\item{system}{The numbering system to use. By default, this is the
-international numbering system (\code{"intl"}) whereby grouping separators
-(i.e., \code{sep_mark}) are separated by three digits. The alternative system,
-the Indian numbering system (\code{"ind"}) uses grouping separators that
-correspond to thousand, lakh, crore, and higher quantities.}
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_roman.Rd b/man/fmt_roman.Rd
index 3021eff02d..53a61dfeea 100644
--- a/man/fmt_roman.Rd
+++ b/man/fmt_roman.Rd
@@ -13,29 +13,50 @@ fmt_roman(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{case}{Should Roman numerals should be rendered as uppercase (\code{"upper"})
-or lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{case}{\emph{Use uppercase or lowercase letters}
+
+\verb{singl-kw:[upper|lower]} --- \emph{default:} \code{"upper"}
+
+Should Roman numerals should be rendered as uppercase (\code{"upper"}) or
+lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_scientific.Rd b/man/fmt_scientific.Rd
index 894b1e81da..742973bae2 100644
--- a/man/fmt_scientific.Rd
+++ b/man/fmt_scientific.Rd
@@ -21,61 +21,120 @@ fmt_scientific(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
 
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.}
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied.}
 
-\item{exp_style}{Style of formatting to use for the scientific notation
-formatting. By default this is \code{"x10n"} but other options include using
-a single letter (e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to
-signal a minimum digit width of one, or \code{"low-ten"} for using a stylized
-\code{"10"} marker.}
+\item{exp_style}{\emph{Style declaration for exponent formatting}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+\verb{scalar<character>} --- \emph{default:} \code{"x10n"}
 
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
+Style of formatting to use for the scientific notation formatting. By
+default this is \code{"x10n"} but other options include using a single letter
+(e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to signal a
+minimum digit width of one, or \code{"low-ten"} for using a stylized \code{"10"}
+marker.}
 
-\item{dec_mark}{The character to use as a decimal mark (e.g., using \code{dec_mark = ","} with \code{0.152} would result in a formatted value of \verb{0,152}).}
+\item{pattern}{\emph{Specification of the formatting pattern}
 
-\item{force_sign_m, force_sign_n}{Should the plus sign be shown for positive
-values of the mantissa (first component) or the exponent? This would
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign_m, force_sign_n}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the plus sign be shown for positive values of the mantissa (first
+component, \code{force_sign_m}) or the exponent (\code{force_sign_n})? This would
 effectively show a sign for all values except zero on either of those
 numeric components of the notation. If so, use \code{TRUE} for either one of
 these options. The default for both is \code{FALSE}, where only negative numbers
 will display a sign.}
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_spelled_num.Rd b/man/fmt_spelled_num.Rd
index eab829bb35..c212528919 100644
--- a/man/fmt_spelled_num.Rd
+++ b/man/fmt_spelled_num.Rd
@@ -13,33 +13,55 @@ fmt_spelled_num(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_time.Rd b/man/fmt_time.Rd
index 766c511647..b0afb3113f 100644
--- a/man/fmt_time.Rd
+++ b/man/fmt_time.Rd
@@ -14,37 +14,64 @@ fmt_time(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{time_style}{The time style to use. By default this is \code{"iso"} which
-corresponds to how times are formatted within ISO 8601 datetime values. The
-other time styles can be viewed using \code{\link[=info_time_style]{info_time_style()}}.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{time_style}{\emph{Predefined style for times}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=25)} --- \emph{default:} \code{"iso"}
+
+The time style to use. By default this is the short name \code{"iso"} which
+corresponds to how times are formatted within ISO 8601 datetime values.
+There are 25 time styles in total and their short names can be viewed using
+\code{\link[=info_time_style]{info_time_style()}}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/fmt_url.Rd b/man/fmt_url.Rd
index d39b0a66a1..98d23ed31d 100644
--- a/man/fmt_url.Rd
+++ b/man/fmt_url.Rd
@@ -18,46 +18,77 @@ fmt_url(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{The columns to format. Can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+Can either be a series of column names provided in \code{\link[=c]{c()}}, a vector of
+column indices, or a select helper function. Examples of select helper
+functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+undergo formatting. The default \code{\link[=everything]{everything()}} results in all rows in
+\code{columns} being formatted. Alternatively, we can supply a vector of row
+captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
 \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows to format. Providing \code{\link[=everything]{everything()}} (the
-default) results in all rows in \code{columns} being formatted. Alternatively,
-we can supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row
-indices, or a helper function focused on selections. The select helper
-functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions
-to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{label}{The visible 'label' to use for the link. If \code{NULL} (the default)
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{label}{\emph{Link label}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The visible 'label' to use for the link. If \code{NULL} (the default)
 the URL will serve as the label. There are two non-\code{NULL} options: (1) a
 static text can be used for the label by providing a string, and (2) a
 function can be provided to fashion a label from every URL.}
 
-\item{as_button}{An option to style the link as a button. By default, this is
+\item{as_button}{\emph{Style link as a button}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to style the link as a button. By default, this is
 \code{FALSE}. If this option is chosen then the \code{button_fill} argument becomes
 usable.}
 
-\item{color}{The color used for the resulting link and its underline. This is
+\item{color}{\emph{Link color}
+
+\verb{scalar<character>} --- \emph{default:} \code{"auto"}
+
+The color used for the resulting link and its underline. This is
 \code{"auto"} by default; this allows \strong{gt} to choose an appropriate color
-based on various factors (e.g., background \code{button_fill} when \code{as_button}
-is \code{TRUE}).}
+based on various factors (such as the background \code{button_fill} when
+\code{as_button} is \code{TRUE}).}
 
-\item{show_underline}{Should the link be decorated with an underline? By
+\item{show_underline}{\emph{Show the link underline}
+
+\verb{scalar<character>|scalar<logical>} --- \emph{default:} \code{"auto"}
+
+Should the link be decorated with an underline? By
 default this is \code{"auto"} which means that \strong{gt} will choose \code{TRUE} when
 \code{as_button = FALSE} and \code{FALSE} in the other case. The link underline will
 be the same color as that set in the \code{color} option.}
 
-\item{button_fill, button_width, button_outline}{Options for styling a
-link-as-button (and only applies if \code{as_button = TRUE}). All of these
-options are by default set to \code{"auto"}, allowing \strong{gt} to choose
-appropriate fill, width, and outline values.}
+\item{button_fill, button_width, button_outline}{\emph{Button options}
+
+\verb{scalar<character>} --- \emph{default:} \code{"auto"}
+
+Options for styling a link-as-button (and only applies if
+\code{as_button = TRUE}). All of these options are by default set to \code{"auto"},
+allowing \strong{gt} to choose appropriate fill, width, and outline values.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/ggplot_image.Rd b/man/ggplot_image.Rd
index f14c621e13..58689cd628 100644
--- a/man/ggplot_image.Rd
+++ b/man/ggplot_image.Rd
@@ -7,15 +7,28 @@
 ggplot_image(plot_object, height = 100, aspect_ratio = 1)
 }
 \arguments{
-\item{plot_object}{A ggplot plot object.}
+\item{plot_object}{\emph{A ggplot plot object}
 
-\item{height}{The absolute height (px) of the image in the table cell.}
+\verb{obj:<ggplot>} --- \strong{required}
 
-\item{aspect_ratio}{The plot's final aspect ratio. Where the height of the
-plot is fixed using the \code{height} argument, the \code{aspect_ratio}
-will either compress (\code{aspect_ratio} < \code{1.0}) or expand
-(\code{aspect_ratio} > \code{1.0}) the plot horizontally. The default value
-of \code{1.0} will neither compress nor expand the plot.}
+A \code{ggplot} plot object.}
+
+\item{height}{\emph{Height of image}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{100}
+
+The absolute height of the output image in the table cell (in \code{"px"}
+units). By default, this is set to \code{"100px"}.}
+
+\item{aspect_ratio}{\emph{The final aspect ratio of plot}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1.0}
+
+This is the plot's final aspect ratio. Where the height of the plot is
+fixed using the \code{height} argument, the \code{aspect_ratio} will either compress
+(\code{aspect_ratio} < \code{1.0}) or expand (\code{aspect_ratio} > \code{1.0}) the plot
+horizontally. The default value of \code{1.0} will neither compress nor expand
+the plot.}
 }
 \value{
 A character object with an HTML fragment that can be placed inside of
diff --git a/man/google_font.Rd b/man/google_font.Rd
index 982c66d559..f1f2a88308 100644
--- a/man/google_font.Rd
+++ b/man/google_font.Rd
@@ -7,7 +7,11 @@
 google_font(name)
 }
 \arguments{
-\item{name}{The complete name of a font available in \emph{Google Fonts}.}
+\item{name}{\emph{Google Font name}
+
+\verb{scalar<character>} --- \strong{required}
+
+The complete name of a font available in \emph{Google Fonts}.}
 }
 \value{
 An object of class \code{font_css}.
diff --git a/man/grand_summary_rows.Rd b/man/grand_summary_rows.Rd
index cec9a63dea..f3ddb7e3b4 100644
--- a/man/grand_summary_rows.Rd
+++ b/man/grand_summary_rows.Rd
@@ -16,45 +16,78 @@ grand_summary_rows(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{columns}{The columns for which the summaries should be calculated. By
-default, this is every column that has data cells (given by
-\code{everything()}).}
-
-\item{fns}{Functions used for aggregations. This can include base functions
-like \code{mean}, \code{min}, \code{max}, \code{median}, \code{sd}, or \code{sum} or any other
-user-defined aggregation function. Multiple functions, each of which would
-generate a different row, are to be supplied within a \code{list()}. We can
-specify the functions by use of function names in quotes (e.g., \code{"sum"}),
-as bare functions (e.g., \code{sum}), or in formula form (e.g.,
-\code{minimum ~ min(.)}) where the LHS could be used to supply the summary row
-label and id values. More information on this can be found in the
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the summaries should be calculated. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{fns}{\emph{Aggregation Expressions}
+
+\verb{<expression|list of expressions>}
+
+Functions used for aggregations. This can include base functions like
+\code{mean}, \code{min}, \code{max}, \code{median}, \code{sd}, or \code{sum} or any other user-defined
+aggregation function. Multiple functions, each of which would generate a
+different row, are to be supplied within a \code{list()}. We can specify the
+functions by use of function names in quotes (e.g., \code{"sum"}), as bare
+functions (e.g., \code{sum}), or in formula form (e.g., \code{minimum ~ min(.)})
+where the LHS could be used to supply the summary row label and ID values.
+More information on this can be found in the
 \emph{Aggregation expressions for \code{fns}} section.}
 
-\item{fmt}{Formatting expressions in formula form. The RHS of \code{~} should
-contain a formatting call (e.g.,
-\verb{~ fmt_number(., decimals = 3, use_seps = FALSE}). Optionally, the LHS
-could contain a group-targeting expression (e.g.,
+\item{fmt}{\emph{Formatting expressions}
+
+\verb{<expression|list of expressions>}
+
+Formatting expressions in formula form. The RHS of \code{~} should contain a
+formatting call (e.g., \verb{~ fmt_number(., decimals = 3, use_seps = FALSE}).
+Optionally, the LHS could contain a group-targeting expression (e.g.,
 \code{"group_a" ~ fmt_number(.)}). More information on this can be found in the
 \emph{Formatting expressions for \code{fmt}} section.}
 
-\item{side}{Should the grand summary rows be placed at the \code{"bottom"} (the
-default) or the \code{"top"} of the table?}
+\item{side}{\emph{Side used for placement of grand summary rows}
+
+\verb{singl-kw:[bottom|top]} --- \emph{default:} \code{"bottom"}
+
+Should the grand summary rows be placed at the \code{"bottom"} (the default) or
+the \code{"top"} of the table?}
+
+\item{missing_text}{\emph{Replacement text for \code{NA} values}
+
+\verb{scalar<character>} --- \emph{default:} \code{"---"}
+
+The text to be used in place of \code{NA} values in summary cells with no data
+outputs.}
+
+\item{formatter}{\emph{\link{Deprecated} Formatting function}
+
+\verb{<expression>}
+
+Deprecated, please use \code{fmt} instead. This was previously used as a way to
+input a formatting function name, which could be any of the \verb{fmt_*()}
+functions available in the package (e.g., \code{\link[=fmt_number]{fmt_number()}}, \code{\link[=fmt_percent]{fmt_percent()}},
+etc.), or a custom function using \code{\link[=fmt]{fmt()}}. The options of a formatter can
+be accessed through \code{...}.}
 
-\item{missing_text}{The text to be used in place of \code{NA} values in summary
-cells with no data outputs.}
+\item{...}{\emph{\link{Deprecated} Formatting arguments}
 
-\item{formatter}{Deprecated, please use \code{fmt} instead. This was previously
-used as a way to input a formatting function name, which could be any of
-the \verb{fmt_*()} functions available in the package (e.g., \code{\link[=fmt_number]{fmt_number()}},
-\code{\link[=fmt_percent]{fmt_percent()}}, etc.), or a custom function using \code{\link[=fmt]{fmt()}}. The options of
-a formatter can be accessed through \code{...}.}
+\verb{<Named arguments>}
 
-\item{...}{Deprecated (along with \code{formatter}) but otherwise used for
-argument values for a formatting function supplied in \code{formatter}. For
-example, if using \code{formatter = fmt_number}, options such as \code{decimals = 1},
-\code{use_seps = FALSE}, and the like can be used here.}
+Deprecated (along with \code{formatter}) but otherwise used for argument values
+for a formatting function supplied in \code{formatter}. For example, if using
+\code{formatter = fmt_number}, options such as \code{decimals = 1}, \code{use_seps = FALSE}, and the like can be used here.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/grp_add.Rd b/man/grp_add.Rd
index fde3143164..c7b8999c74 100644
--- a/man/grp_add.Rd
+++ b/man/grp_add.Rd
@@ -7,18 +7,35 @@
 grp_add(.data, ..., .list = list2(...), .before = NULL, .after = NULL)
 }
 \arguments{
-\item{.data}{A \code{gt_group} container object, typically generated through use
-of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
+\item{.data}{\emph{The gt table group object}
 
-\item{...}{One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated
-via the \code{\link[=gt]{gt()}} function.}
+\verb{obj:<gt_group>} --- \strong{required}
 
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
+This is a \code{gt_group} container object. It is typically generated through
+use of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects,
+or, made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
 
-\item{.before, .after}{A single index for either \code{.before} or \code{.after},
-specifying where the supplied \code{gt_tbl} objects should be placed amongst the
-existing collection of \strong{gt} tables. If nothing is provided for either
-argument the incoming \code{gt_tbl} objects will be appended.}
+\item{...}{\emph{One or more gt table objects}
+
+\verb{obj:<gt_tbl>} --- \strong{required} (or, use \code{...})
+
+One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated via the
+\code{\link[=gt]{gt()}} function.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
+
+\item{.before, .after}{\emph{Table used as anchor}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A single index for either \code{.before} or \code{.after}, specifying where the
+supplied \code{gt_tbl} objects should be placed amongst the existing collection
+of \strong{gt} tables. If nothing is provided for either argument the incoming
+\code{gt_tbl} objects will be appended.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/grp_clone.Rd b/man/grp_clone.Rd
index aa67000517..553b0fff57 100644
--- a/man/grp_clone.Rd
+++ b/man/grp_clone.Rd
@@ -7,16 +7,29 @@
 grp_clone(data, which = NULL, before = NULL, after = NULL)
 }
 \arguments{
-\item{data}{A \code{gt_group} container object, typically generated through use
-of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
+\item{data}{\emph{The gt table group object}
 
-\item{which}{A vector of index values denoting which \code{gt_tbl} tables should
-be cloned inside of the \code{gt_group} object.}
+\verb{obj:<gt_group>} --- \strong{required}
 
-\item{before, after}{A single index for either \code{before} or \code{after},
-specifies where the cloned \code{gt_tbl} objects should be placed amongst the
-existing collection of \strong{gt} tables. If nothing is provided for either
-argument the incoming \code{gt_tbl} objects will be appended.}
+This is a \code{gt_group} container object. It is typically generated through
+use of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects,
+or, made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
+
+\item{which}{\emph{The tables to clone}
+
+\verb{vector<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A vector of index values denoting which \strong{gt} tables should be cloned
+inside of the \code{gt_group} object.}
+
+\item{before, after}{\emph{Table used as anchor}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A single index for either \code{before} or \code{after}, specifies where the cloned
+\code{gt_tbl} objects should be placed amongst the existing collection of \strong{gt}
+tables. If nothing is provided for either argument, the incoming \code{gt_tbl}
+objects will be appended.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/grp_options.Rd b/man/grp_options.Rd
index 9c66ba3066..66c31a0e04 100644
--- a/man/grp_options.Rd
+++ b/man/grp_options.Rd
@@ -191,48 +191,68 @@ grp_options(
 )
 }
 \arguments{
-\item{data}{A \code{gt_group} container object, typically generated through use of
-the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
-
-\item{table.width}{The width of the table. Can be specified as a
-single-length character with units of pixels or as a percentage. If
-provided as a single-length numeric vector, it is assumed that the value is
-given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper functions can also
-be used to pass in numeric values and obtain values as pixel or percent
-units.}
-
-\item{table.layout}{The value for the \code{table-layout} CSS style in the HTML
-output context. By default, this is \code{"fixed"} but another valid option is
+\item{data}{\emph{The gt table group object}
+
+\verb{obj:<gt_group>} --- \strong{required}
+
+This is \code{gt_group} container object. It is typically generated through use
+of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects, or,
+made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
+
+\item{table.width}{\emph{Table width}
+
+The table width can be specified as a single-length character with units of
+pixels or as a percentage. If provided as a single-length numeric vector,
+it is assumed that the value is given in units of pixels. The \code{\link[=px]{px()}} and
+\code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
+obtain values as pixel or percent units.}
+
+\item{table.layout}{\emph{The table-layout property}
+
+This is the value for the \code{table-layout} CSS style in the HTML output
+context. By default, this is \code{"fixed"} but another valid option is
 \code{"auto"}.}
 
-\item{table.align}{The horizontal alignment of the table in its container. By
-default, this is \code{"center"}. Other options are \code{"left"} and \code{"right"}. This
-will automatically set \code{table.margin.left} and \code{table.margin.right} to the
-appropriate values.}
-
-\item{table.margin.left, table.margin.right}{The size of the margins on the
-left and right of the table within the container. Can be specified as a
-single-length character with units of pixels or as a percentage. If
-provided as a single-length numeric vector, it is assumed that the value is
-given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper functions can also
-be used to pass in numeric values and obtain values as pixel or percent
-units. Using \code{table.margin.left} or \code{table.margin.right} will overwrite any
-values set by \code{table.align}.}
-
-\item{table.background.color, heading.background.color, column_labels.background.color, row_group.background.color, stub.background.color, summary_row.background.color, grand_summary_row.background.color, footnotes.background.color, source_notes.background.color}{Background colors for the parent element \code{table} and the following child
-elements: \code{heading}, \code{column_labels}, \code{row_group}, \code{stub}, \code{summary_row},
-\code{grand_summary_row}, \code{footnotes}, and \code{source_notes}. A color name or a
-hexadecimal color code should be provided.}
+\item{table.align}{\emph{Horizontal alignment of table}
+
+The \code{table.align} option lets us set the horizontal alignment of the table
+in its container. By default, this is \code{"center"}. Other options are
+\code{"left"} and \code{"right"}. This will automatically set \code{table.margin.left} and
+\code{table.margin.right} to the appropriate values.}
 
-\item{table.additional_css}{This option can be used to supply an additional
-block of CSS rules to be applied after the automatically generated table
-CSS.}
+\item{table.margin.left, table.margin.right}{\emph{Left and right table margins}
 
-\item{table.font.names}{The names of the fonts used for the table. This is
-a vector of several font names. If the first font isn't available, then
-the next font is tried (and so on).}
+The size of the margins on the left and right of the table within the
+container can be set with \code{table.margin.left} and \code{table.margin.right}. Can
+be specified as a single-length character with units of pixels or as a
+percentage. If provided as a single-length numeric vector, it is assumed
+that the value is given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper
+functions can also be used to pass in numeric values and obtain values as
+pixel or percent units. Using \code{table.margin.left} or \code{table.margin.right}
+will overwrite any values set by \code{table.align}.}
 
-\item{table.font.size, heading.title.font.size, heading.subtitle.font.size, column_labels.font.size, row_group.font.size, stub.font.size, footnotes.font.size, source_notes.font.size}{The font sizes for the parent text element \code{table} and the following child
+\item{table.background.color, heading.background.color, column_labels.background.color, row_group.background.color, stub.background.color, summary_row.background.color, grand_summary_row.background.color, footnotes.background.color, source_notes.background.color}{\emph{Background colors}
+
+These options govern background colors for the parent element \code{table} and
+the following child elements: \code{heading}, \code{column_labels}, \code{row_group},
+\code{stub}, \code{summary_row}, \code{grand_summary_row}, \code{footnotes}, and
+\code{source_notes}. A color name or a hexadecimal color code should be
+provided.}
+
+\item{table.additional_css}{\emph{Additional CSS}
+
+The \code{table.additional_css} option can be used to supply an additional block
+of CSS rules to be applied after the automatically generated table CSS.}
+
+\item{table.font.names}{\emph{Default table fonts}
+
+The names of the fonts used for the table can be supplied through
+\code{table.font.names}. This is a vector of several font names. If the first
+font isn't available, then the next font is tried (and so on).}
+
+\item{table.font.size, heading.title.font.size, heading.subtitle.font.size, column_labels.font.size, row_group.font.size, stub.font.size, footnotes.font.size, source_notes.font.size}{\emph{Table font sizes}
+
+The font sizes for the parent text element \code{table} and the following child
 elements: \code{heading.title}, \code{heading.subtitle}, \code{column_labels},
 \code{row_group}, \code{footnotes}, and \code{source_notes}. Can be specified as a
 single-length character vector with units of pixels (e.g., \verb{12px}) or as a
@@ -241,35 +261,49 @@ it is assumed that the value is given in units of pixels. The \code{\link[=px]{p
 \code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
 obtain values as pixel or percentage units.}
 
-\item{table.font.weight, heading.title.font.weight, heading.subtitle.font.weight, column_labels.font.weight, row_group.font.weight, stub.font.weight}{The font weights of the table, \code{heading.title}, \code{heading.subtitle},
+\item{table.font.weight, heading.title.font.weight, heading.subtitle.font.weight, column_labels.font.weight, row_group.font.weight, stub.font.weight}{\emph{Table font weights}
+
+The font weights of the table, \code{heading.title}, \code{heading.subtitle},
 \code{column_labels}, \code{row_group}, and \code{stub} text elements. Can be a text-based
 keyword such as \code{"normal"}, \code{"bold"}, \code{"lighter"}, \code{"bolder"}, or, a
 numeric value between \code{1} and \code{1000}, inclusive. Note that only variable
 fonts may support the numeric mapping of weight.}
 
-\item{table.font.style}{The font style for the table. Can be one of either
+\item{table.font.style}{\emph{Default table font style}
+
+This is the default font style for the table. Can be one of either
 \code{"normal"}, \code{"italic"}, or \code{"oblique"}.}
 
-\item{table.font.color, table.font.color.light}{The text color used throughout the table. There are two variants:
-\code{table.font.color} is for text overlaid on lighter background colors, and
-\code{table.font.color.light} is automatically used when text needs to be
-overlaid on darker background colors. A color name or a hexadecimal color
-code should be provided.}
+\item{table.font.color, table.font.color.light}{\emph{Default dark and light text for the table}
+
+These options define text colors used throughout the table. There are two
+variants: \code{table.font.color} is for text overlaid on lighter background
+colors, and \code{table.font.color.light} is automatically used when text needs
+to be overlaid on darker background colors. A color name or a hexadecimal
+color code should be provided.}
 
-\item{table.border.top.style, table.border.top.width, table.border.top.color, table.border.right.style, table.border.right.width, table.border.right.color, table.border.bottom.style, table.border.bottom.width, table.border.bottom.color, table.border.left.style, table.border.left.width, table.border.left.color}{The style, width, and color properties of the table's absolute top and
+\item{table.border.top.style, table.border.top.width, table.border.top.color, table.border.right.style, table.border.right.width, table.border.right.color, table.border.bottom.style, table.border.bottom.width, table.border.bottom.color, table.border.left.style, table.border.left.width, table.border.left.color}{\emph{Top border properties}
+
+The style, width, and color properties of the table's absolute top and
 absolute bottom borders.}
 
-\item{heading.align}{Controls the horizontal alignment of the heading title
-and subtitle. We can either use \code{"center"}, \code{"left"}, or \code{"right"}.}
+\item{heading.align}{\emph{Horizontal alignment in the table header}
+
+Controls the horizontal alignment of the heading title and subtitle. We can
+either use \code{"center"}, \code{"left"}, or \code{"right"}.}
+
+\item{heading.padding, column_labels.padding, data_row.padding, row_group.padding, summary_row.padding, grand_summary_row.padding, footnotes.padding, source_notes.padding}{\emph{Vertical padding throughout the table}
 
-\item{heading.padding, column_labels.padding, data_row.padding, row_group.padding, summary_row.padding, grand_summary_row.padding, footnotes.padding, source_notes.padding}{The amount of vertical padding to incorporate in the \code{heading} (title and
+The amount of vertical padding to incorporate in the \code{heading} (title and
 subtitle), the \code{column_labels} (this includes the column spanners), the row
 group labels (\code{row_group.padding}), in the body/stub rows
 (\code{data_row.padding}), in summary rows (\code{summary_row.padding} or
 \code{grand_summary_row.padding}), or in the footnotes and source notes
 (\code{footnotes.padding} and \code{source_notes.padding}).}
 
-\item{heading.padding.horizontal, column_labels.padding.horizontal, data_row.padding.horizontal, row_group.padding.horizontal, summary_row.padding.horizontal, grand_summary_row.padding.horizontal, footnotes.padding.horizontal, source_notes.padding.horizontal}{The amount of horizontal padding to incorporate in the \code{heading} (title and
+\item{heading.padding.horizontal, column_labels.padding.horizontal, data_row.padding.horizontal, row_group.padding.horizontal, summary_row.padding.horizontal, grand_summary_row.padding.horizontal, footnotes.padding.horizontal, source_notes.padding.horizontal}{\emph{Horizontal padding throughout the table}
+
+The amount of horizontal padding to incorporate in the \code{heading} (title and
 subtitle), the \code{column_labels} (this includes the column spanners), the row
 group labels (\code{row_group.padding.horizontal}), in the body/stub rows
 (\code{data_row.padding}), in summary rows (\code{summary_row.padding.horizontal} or
@@ -277,127 +311,180 @@ group labels (\code{row_group.padding.horizontal}), in the body/stub rows
 notes (\code{footnotes.padding.horizontal} and
 \code{source_notes.padding.horizontal}).}
 
-\item{heading.border.bottom.style, heading.border.bottom.width, heading.border.bottom.color}{The style, width, and color properties of the header's bottom border. This
+\item{heading.border.bottom.style, heading.border.bottom.width, heading.border.bottom.color}{\emph{Properties of the header's bottom border}
+
+The style, width, and color properties of the header's bottom border. This
 border shares space with that of the \code{column_labels} location. If the
 \code{width} of this border is larger, then it will be the visible border.}
 
-\item{heading.border.lr.style, heading.border.lr.width, heading.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{heading.border.lr.style, heading.border.lr.width, heading.border.lr.color}{\emph{Properties of the header's left and right borders}
+
+The style, width, and color properties for the left and right borders of
 the \code{heading} location.}
 
-\item{column_labels.text_transform, row_group.text_transform, stub.text_transform, summary_row.text_transform, grand_summary_row.text_transform}{Options to apply text transformations to the \code{column_labels}, \code{row_group},
+\item{column_labels.text_transform, row_group.text_transform, stub.text_transform, summary_row.text_transform, grand_summary_row.text_transform}{\emph{Text transforms throughout the table}
+
+Options to apply text transformations to the \code{column_labels}, \code{row_group},
 \code{stub}, \code{summary_row}, and \code{grand_summary_row} text elements. Either of the
 \code{"uppercase"}, \code{"lowercase"}, or \code{"capitalize"} keywords can be used.}
 
-\item{column_labels.vlines.style, column_labels.vlines.width, column_labels.vlines.color}{The style, width, and color properties for all vertical lines ('vlines')
+\item{column_labels.vlines.style, column_labels.vlines.width, column_labels.vlines.color}{\emph{Properties of all vertical lines by the column labels}
+
+The style, width, and color properties for all vertical lines ('vlines')
 of the the \code{column_labels}.}
 
-\item{column_labels.border.top.style, column_labels.border.top.width, column_labels.border.top.color}{The style, width, and color properties for the top border of the
+\item{column_labels.border.top.style, column_labels.border.top.width, column_labels.border.top.color}{\emph{Properties of the border above the column labels}
+
+The style, width, and color properties for the top border of the
 \code{column_labels} location. This border shares space with that of the
 \code{heading} location. If the \code{width} of this border is larger, then it will
 be the visible border.}
 
-\item{column_labels.border.bottom.style, column_labels.border.bottom.width, column_labels.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{column_labels.border.bottom.style, column_labels.border.bottom.width, column_labels.border.bottom.color}{\emph{Properties of the border below the column labels}
+
+The style, width, and color properties for the bottom border of the
 \code{column_labels} location.}
 
-\item{column_labels.border.lr.style, column_labels.border.lr.width, column_labels.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{column_labels.border.lr.style, column_labels.border.lr.width, column_labels.border.lr.color}{\emph{Properties of the left and right borders next to the column labels}
+
+The style, width, and color properties for the left and right borders of
 the \code{column_labels} location.}
 
-\item{column_labels.hidden}{An option to hide the column labels. If providing
-\code{TRUE} then the entire \code{column_labels} location won't be seen and the table
-header (if present) will collapse downward.}
+\item{column_labels.hidden}{\emph{Hiding all column labels}
 
-\item{row_group.border.top.style, row_group.border.top.width, row_group.border.top.color, row_group.border.bottom.style, row_group.border.bottom.width, row_group.border.bottom.color, row_group.border.left.style, row_group.border.left.width, row_group.border.left.color, row_group.border.right.style, row_group.border.right.width, row_group.border.right.color}{The style, width, and color properties for all top, bottom, left, and right
+An option to hide the column labels. If providing \code{TRUE} then the entire
+\code{column_labels} location won't be seen and the table header (if present)
+will collapse downward.}
+
+\item{row_group.border.top.style, row_group.border.top.width, row_group.border.top.color, row_group.border.bottom.style, row_group.border.bottom.width, row_group.border.bottom.color, row_group.border.left.style, row_group.border.left.width, row_group.border.left.color, row_group.border.right.style, row_group.border.right.width, row_group.border.right.color}{\emph{Border properties associated with the \code{row_group} location}
+
+The style, width, and color properties for all top, bottom, left, and right
 borders of the \code{row_group} location.}
 
-\item{row_group.default_label}{An option to set a default row group label for
-any rows not formally placed in a row group named by \code{group} in any call of
-\code{tab_row_group()}. If this is set as \code{NA_character} and there are rows that
-haven't been placed into a row group (where one or more row groups already
-exist), those rows will be automatically placed into a row group without a
-label.}
+\item{row_group.default_label}{\emph{The default row group label}
+
+An option to set a default row group label for any rows not formally placed
+in a row group named by \code{group} in any call of \code{\link[=tab_row_group]{tab_row_group()}}. If this
+is set as \code{NA_character_} and there are rows that haven't been placed into a
+row group (where one or more row groups already exist), those rows will be
+automatically placed into a row group without a label.}
+
+\item{row_group.as_column}{\emph{Structure row groups with a column}
+
+How should row groups be structured? By default, they are separate rows
+that lie above the each of the groups. Setting this to \code{TRUE} will
+structure row group labels as a separate column in the table stub.}
 
-\item{row_group.as_column}{How should row groups be structured? By default,
-they are separate rows that lie above the each of the groups. Setting this
-to \code{TRUE} will structure row group labels are columns to the far left of
-the table.}
+\item{table_body.hlines.style, table_body.hlines.width, table_body.hlines.color, table_body.vlines.style, table_body.vlines.width, table_body.vlines.color}{\emph{Properties of all horizontal and vertical lines in the table body}
 
-\item{table_body.hlines.style, table_body.hlines.width, table_body.hlines.color, table_body.vlines.style, table_body.vlines.width, table_body.vlines.color}{The style, width, and color properties for all horizontal lines ('hlines')
+The style, width, and color properties for all horizontal lines ('hlines')
 and vertical lines ('vlines') in the \code{table_body}.}
 
-\item{table_body.border.top.style, table_body.border.top.width, table_body.border.top.color, table_body.border.bottom.style, table_body.border.bottom.width, table_body.border.bottom.color}{The style, width, and color properties for all top and bottom borders of
+\item{table_body.border.top.style, table_body.border.top.width, table_body.border.top.color, table_body.border.bottom.style, table_body.border.bottom.width, table_body.border.bottom.color}{\emph{Properties of top and bottom borders in the table body}
+
+The style, width, and color properties for all top and bottom borders of
 the \code{table_body} location.}
 
-\item{stub.border.style, stub.border.width, stub.border.color}{The style, width, and color properties for the vertical border of the table
+\item{stub.border.style, stub.border.width, stub.border.color}{\emph{Properties of the vertical border of the table stub}
+
+The style, width, and color properties for the vertical border of the table
 stub.}
 
-\item{stub.indent_length}{The width of each indentation level. By default
-this is \code{"5px"}.}
+\item{stub.indent_length}{\emph{Width of each indentation}
+
+The width of each indentation level for row labels in the stub. The
+indentation can be set by using \code{\link[=tab_stub_indent]{tab_stub_indent()}}. By default this is
+\code{"5px"}.}
+
+\item{stub_row_group.font.size, stub_row_group.font.weight, stub_row_group.text_transform, stub_row_group.border.style, stub_row_group.border.width, stub_row_group.border.color}{\emph{Properties of the row group column in the table stub}
+
+Options for the row group column in the table stub (made possible when
+using \code{row_group.as_column = TRUE}). The defaults for these options mirror
+that of the \verb{stub.*} variants (except for \code{stub_row_group.border.width},
+which is \code{"1px"} instead of \code{"2px"}).}
 
-\item{stub_row_group.font.size, stub_row_group.font.weight, stub_row_group.text_transform, stub_row_group.border.style, stub_row_group.border.width, stub_row_group.border.color}{Options for the row group column in the stub (made possible when using
-\code{row_group.as_column = TRUE}). The defaults for these options mirror that
-of the \verb{stub.*} variants (except for \code{stub_row_group.border.width}, which
-is \code{"1px"} instead of \code{"2px"}).}
+\item{summary_row.border.style, summary_row.border.width, summary_row.border.color}{\emph{Properties of horizontal borders belonging to summary rows}
 
-\item{summary_row.border.style, summary_row.border.width, summary_row.border.color}{The style, width, and color properties for all horizontal borders of the
+The style, width, and color properties for all horizontal borders of the
 \code{summary_row} location.}
 
-\item{grand_summary_row.border.style, grand_summary_row.border.width, grand_summary_row.border.color}{The style, width, and color properties for the top borders of the
+\item{grand_summary_row.border.style, grand_summary_row.border.width, grand_summary_row.border.color}{\emph{Properties of horizontal borders belonging to grand summary rows}
+
+The style, width, and color properties for the top borders of the
 \code{grand_summary_row} location.}
 
-\item{footnotes.border.bottom.style, footnotes.border.bottom.width, footnotes.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{footnotes.border.bottom.style, footnotes.border.bottom.width, footnotes.border.bottom.color}{\emph{Properties of the bottom border belonging to the footnotes}
+
+The style, width, and color properties for the bottom border of the
 \code{footnotes} location.}
 
-\item{footnotes.border.lr.style, footnotes.border.lr.width, footnotes.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{footnotes.border.lr.style, footnotes.border.lr.width, footnotes.border.lr.color}{\emph{Properties of left and right borders belonging to the footnotes}
+
+The style, width, and color properties for the left and right borders of
 the \code{footnotes} location.}
 
-\item{footnotes.marks}{The set of sequential marks used to reference and
-identify each of the footnotes (same input as the \code{\link[=opt_footnote_marks]{opt_footnote_marks()}}
-function). We can supply a vector that represents the series of footnote
-marks. This vector is recycled when its usage goes beyond the length of the
-set. At each cycle, the marks are simply combined (e.g., \code{*} -> \verb{**} ->
-\verb{***}). The option exists for providing keywords for certain types of
-footnote marks. The keyword \code{"numbers"} (the default, indicating that we
-want to use numeric marks). We can use lowercase \code{"letters"} or uppercase
-\code{"LETTERS"}. There is the option for using a traditional symbol set where
-\code{"standard"} provides four symbols, and, \code{"extended"} adds two more
-symbols, making six.}
-
-\item{footnotes.spec_ref, footnotes.spec_ftr}{Optional specifications for
-formatting of footnote references (\code{footnotes.spec_ref}) and their
-associated marks the footer section (\code{footnotes.spec_ftr}) (same input as
-the \code{\link[=opt_footnote_spec]{opt_footnote_spec()}} function). This is a string containing
-specification control characters. The default is the spec string \code{"^i"},
-which is superscript text set in italics. Other control characters that can
-be used are: (1) \code{"b"} for bold text, and (2) \code{"("} / \code{")"} for the
-enclosure of footnote marks in parentheses.}
-
-\item{footnotes.multiline, source_notes.multiline}{An option to either put
-footnotes and source notes in separate lines (the default, or \code{TRUE}) or
-render them as a continuous line of text with \code{footnotes.sep} providing the
-separator (by default \code{" "}) between notes.}
-
-\item{footnotes.sep, source_notes.sep}{The separating characters between
-adjacent footnotes and source notes in their respective footer sections
-when rendered as a continuous line of text (when
-\code{footnotes.multiline == FALSE}). The default value is a single space
+\item{footnotes.marks}{\emph{Sequence of footnote marks}
+
+The set of sequential marks used to reference and identify each of the
+footnotes (same input as the \code{\link[=opt_footnote_marks]{opt_footnote_marks()}} function). We can
+supply a vector that represents the series of footnote marks. This vector
+is recycled when its usage goes beyond the length of the set. At each
+cycle, the marks are simply combined (e.g., \code{*} -> \verb{**} -> \verb{***}). The
+option exists for providing keywords for certain types of footnote marks.
+The keyword \code{"numbers"} (the default, indicating that we want to use
+numeric marks). We can use lowercase \code{"letters"} or uppercase \code{"LETTERS"}.
+There is the option for using a traditional symbol set where \code{"standard"}
+provides four symbols, and, \code{"extended"} adds two more symbols, making six.}
+
+\item{footnotes.spec_ref, footnotes.spec_ftr}{\emph{Specifications for formatting of footnote marks}
+
+Optional specifications for formatting of footnote references
+(\code{footnotes.spec_ref}) and their associated marks the footer section
+(\code{footnotes.spec_ftr}) (same input as the \code{\link[=opt_footnote_spec]{opt_footnote_spec()}} function).
+This is a string containing specification control characters. The default
+is the spec string \code{"^i"}, which is superscript text set in italics. Other
+control characters that can be used are: (1) \code{"b"} for bold text, and (2)
+\code{"("} / \code{")"} for the enclosure of footnote marks in parentheses.}
+
+\item{footnotes.multiline, source_notes.multiline}{\emph{Typesetting of multiple footnotes and source notes}
+
+An option to either put footnotes and source notes in separate lines (the
+default, or \code{TRUE}) or render them as a continuous line of text with
+\code{footnotes.sep} providing the separator (by default \code{" "}) between notes.}
+
+\item{footnotes.sep, source_notes.sep}{\emph{Separator characters between adjacent footnotes and source notes}
+
+The separating characters between adjacent footnotes and source notes in
+their respective footer sections when rendered as a continuous line of text
+(when \code{footnotes.multiline == FALSE}). The default value is a single space
 character (\code{" "}).}
 
-\item{source_notes.border.bottom.style, source_notes.border.bottom.width, source_notes.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{source_notes.border.bottom.style, source_notes.border.bottom.width, source_notes.border.bottom.color}{\emph{Properties of the bottom border belonging to the source notes}
+
+The style, width, and color properties for the bottom border of the
 \code{source_notes} location.}
 
-\item{source_notes.border.lr.style, source_notes.border.lr.width, source_notes.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{source_notes.border.lr.style, source_notes.border.lr.width, source_notes.border.lr.color}{\emph{Properties of left and right borders belonging to the source notes}
+
+The style, width, and color properties for the left and right borders of
 the \code{source_notes} location.}
 
-\item{row.striping.background_color}{The background color for striped table
-body rows. A color name or a hexadecimal color code should be provided.}
+\item{row.striping.background_color}{\emph{Background color for row stripes}
+
+The background color for striped table body rows. A color name or a
+hexadecimal color code should be provided.}
+
+\item{row.striping.include_stub}{\emph{Inclusion of the table stub for row stripes}
+
+An option for whether to include the stub when striping rows.}
 
-\item{row.striping.include_stub}{An option for whether to include the stub
-when striping rows.}
+\item{row.striping.include_table_body}{\emph{Inclusion of the table body for row stripes}
 
-\item{row.striping.include_table_body}{An option for whether to include the
-table body when striping rows.}
+An option for whether to include the table body when striping rows.}
 
-\item{container.width, container.height, container.padding.x, container.padding.y}{The width and height of the table's container, and, the vertical and
+\item{container.width, container.height, container.padding.x, container.padding.y}{\emph{Table container dimensions and padding}
+
+The width and height of the table's container, and, the vertical and
 horizontal padding of the table's container. The container width and height
 can be specified with units of pixels or as a percentage. The padding is to
 be specified as a length with units of pixels. If provided as a numeric
@@ -405,54 +492,72 @@ value, it is assumed that the value is given in units of pixels. The \code{\link
 and \code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
 obtain values as pixel or percent units.}
 
-\item{container.overflow.x, container.overflow.y}{Options to enable scrolling
-in the horizontal and vertical directions when the table content overflows
-the container dimensions. Using \code{TRUE} (the default for both) means that
-horizontal or vertical scrolling is enabled to view the entire table in
-those directions. With \code{FALSE}, the table may be clipped if the table width
-or height exceeds the \code{container.width} or \code{container.height}.}
-
-\item{ihtml.active}{The option for displaying an interactive version of an
-HTML table (rather than an otherwise 'static' table). This enables the use
-of controls for pagination, global search, filtering, and sorting. The
-individual features are controlled by the other \verb{table.*} options. By
-default, the pagination (\code{ihtml.use_pagination}) and sorting
-(\code{ihtml.use_sorting}) features are enabled. The \code{ihtml.active} option,
-however, is \code{FALSE} by default.}
-
-\item{ihtml.use_pagination, ihtml.use_pagination_info}{For interactive HTML
-output, the option for using pagination controls (below the table body) can
-be controlled with \code{ihtml.use_pagination}. By default, this is \code{TRUE} and
-it will allow the use to page through table content. The informational
-display text regarding the current page can be set with
-\code{ihtml.use_pagination_info} (which is \code{TRUE} by default).}
-
-\item{ihtml.use_sorting}{For interactive HTML output, the option to provide
-controls for sorting column values. By default, this is \code{TRUE}.}
-
-\item{ihtml.use_search}{For interactive HTML output, an option that places a
-search field for globally filtering rows to the requested content. By
-default, this is \code{FALSE}.}
+\item{container.overflow.x, container.overflow.y}{\emph{Table container overflow}
+
+Options to enable scrolling in the horizontal and vertical directions when
+the table content overflows the container dimensions. Using \code{TRUE} (the
+default for both) means that horizontal or vertical scrolling is enabled to
+view the entire table in those directions. With \code{FALSE}, the table may be
+clipped if the table width or height exceeds the \code{container.width} or
+\code{container.height}.}
+
+\item{ihtml.active}{\emph{Display interactive HTML table}
+
+The option for displaying an interactive version of an HTML table (rather
+than an otherwise 'static' table). This enables the use of controls for
+pagination, global search, filtering, and sorting. The individual features
+are controlled by the other \verb{table.*} options. By default, the pagination
+(\code{ihtml.use_pagination}) and sorting (\code{ihtml.use_sorting}) features are
+enabled. The \code{ihtml.active} option, however, is \code{FALSE} by default.}
 
-\item{ihtml.use_filters}{For interactive HTML output, this places search
-fields below each column header and allows for filtering by column. By
+\item{ihtml.use_pagination, ihtml.use_pagination_info}{\emph{Use pagination}
+
+For interactive HTML output, the option for using pagination controls
+(below the table body) can be controlled with \code{ihtml.use_pagination}. By
+default, this is \code{TRUE} and it will allow the use to page through table
+content. The informational display text regarding the current page can be
+set with \code{ihtml.use_pagination_info} (which is \code{TRUE} by default).}
+
+\item{ihtml.use_sorting}{\emph{Provide column sorting controls}
+
+For interactive HTML output, the option to provide controls for sorting
+column values. By default, this is \code{TRUE}.}
+
+\item{ihtml.use_search}{\emph{Provide a global search field}
+
+For interactive HTML output, an option that places a search field for
+globally filtering rows to the requested content. By default, this is
+\code{FALSE}.}
+
+\item{ihtml.use_filters}{\emph{Display filtering fields}
+
+For interactive HTML output, this places search fields below each column
+header and allows for filtering by column. By default, this is \code{FALSE}.}
+
+\item{ihtml.use_resizers}{\emph{Allow column resizing}
+
+For interactive HTML output, this allows for interactive resizing of
+columns. By default, this is \code{FALSE}.}
+
+\item{ihtml.use_highlight}{\emph{Enable row highlighting on hover}
+
+For interactive HTML output, this highlights individual rows upon hover. By
 default, this is \code{FALSE}.}
 
-\item{ihtml.use_resizers}{For interactive HTML output, this allows for
-interactive resizing of columns. By default, this is \code{FALSE}.}
+\item{ihtml.use_compact_mode}{\emph{Use compact mode}
 
-\item{ihtml.use_highlight}{For interactive HTML output, this highlights
-individual rows upon hover. By default, this is \code{FALSE}.}
+For interactive HTML output, an option to reduce vertical padding and thus
+make the table consume less vertical space. By default, this is \code{FALSE}.}
 
-\item{ihtml.use_compact_mode}{For interactive HTML output, an option to
-reduce vertical padding and thus make the table consume less vertical
-space. By default, this is \code{FALSE}.}
+\item{ihtml.use_text_wrapping}{\emph{Use text wrapping}
 
-\item{ihtml.use_text_wrapping}{For interactive HTML output, an option to
-control text wrapping. By default (\code{TRUE}), text will be wrapped to
-multiple lines; if \code{FALSE}, text will be truncated to a single line.}
+For interactive HTML output, an option to control text wrapping. By default
+(\code{TRUE}), text will be wrapped to multiple lines; if \code{FALSE}, text will be
+truncated to a single line.}
 
-\item{ihtml.use_page_size_select, ihtml.page_size_default, ihtml.page_size_values}{For interactive HTML output, \code{ihtml.use_page_size_select} provides the
+\item{ihtml.use_page_size_select, ihtml.page_size_default, ihtml.page_size_values}{\emph{Change page size properties}
+
+For interactive HTML output, \code{ihtml.use_page_size_select} provides the
 option to display a dropdown menu for the number of rows to show per page
 of data. By default, this is the vector \code{c(10, 25, 50, 100)} which
 corresponds to options for \code{10}, \code{25}, \code{50}, and \code{100} rows of data per
@@ -461,39 +566,53 @@ page. To modify these page-size options, provide a numeric vector to
 be modified with \code{ihtml.page_size_default} and this works whether or not
 \code{ihtml.use_page_size_select} is set to \code{TRUE}.}
 
-\item{ihtml.pagination_type}{For interactive HTML output and when using
-pagination, one of three options for presentation pagination controls. The
-default is \code{"numbers"}, where a series of page-number buttons is presented
-along with 'previous' and 'next' buttons. The \code{"jump"} option provides an
-input field with a stepper for the page number. With \code{"simple"}, only the
-'previous' and 'next' buttons are displayed.}
+\item{ihtml.pagination_type}{\emph{Change pagination mode}
+
+For interactive HTML output and when using pagination, one of three options
+for presentation pagination controls. The default is \code{"numbers"}, where a
+series of page-number buttons is presented along with 'previous' and 'next'
+buttons. The \code{"jump"} option provides an input field with a stepper for the
+page number. With \code{"simple"}, only the 'previous' and 'next' buttons are
+displayed.}
+
+\item{page.orientation}{\emph{Set RTF page orientation}
 
-\item{page.orientation}{For RTF output, this provides an two options for page
+For RTF output, this provides an two options for page
 orientation: \code{"portrait"} (the default) and \code{"landscape"}.}
 
-\item{page.numbering}{Within RTF output, should page numbering be displayed?
-By default, this is set to \code{FALSE} but if \code{TRUE} then page numbering text
-will be added to the document header.}
+\item{page.numbering}{\emph{Enable RTF page numbering}
 
-\item{page.header.use_tbl_headings}{If \code{TRUE} then RTF output tables will
-migrate all table headings (including the table title and all column
-labels) to the page header. This page header content will repeat across
-pages. By default, this is \code{FALSE}.}
+Within RTF output, should page numbering be displayed? By default, this is
+set to \code{FALSE} but if \code{TRUE} then page numbering text will be added to the
+document header.}
 
-\item{page.footer.use_tbl_notes}{If \code{TRUE} then RTF output tables will
-migrate all table footer content (this includes footnotes and source notes)
-to the page footer. This page footer content will repeat across pages. By
-default, this is \code{FALSE}.}
+\item{page.header.use_tbl_headings}{\emph{Place table headings in RTF page header}
+
+If \code{TRUE} then RTF output tables will migrate all table headings (including
+the table title and all column labels) to the page header. This page header
+content will repeat across pages. By default, this is \code{FALSE}.}
 
-\item{page.width, page.height}{The page width and height in the standard
-portrait orientation. This is for RTF table output and the default
-values (in inches) are \verb{8.5in} and \verb{11.0in}.}
+\item{page.footer.use_tbl_notes}{\emph{Place table footer in RTF page footer}
 
-\item{page.margin.left, page.margin.right, page.margin.top, page.margin.bottom}{For RTF table output, these options correspond to the left, right, top, and
+If \code{TRUE} then RTF output tables will migrate all table footer content
+(this includes footnotes and source notes) to the page footer. This page
+footer content will repeat across pages. By default, this is \code{FALSE}.}
+
+\item{page.width, page.height}{\emph{Set RTF page dimensions}
+
+The page width and height in the standard portrait orientation. This is for
+RTF table output and the default values (in inches) are \verb{8.5in} and
+\verb{11.0in}.}
+
+\item{page.margin.left, page.margin.right, page.margin.top, page.margin.bottom}{\emph{Set RTF page margins}
+
+For RTF table output, these options correspond to the left, right, top, and
 bottom page margins. The default values for each of these is \verb{1.0in}.}
 
-\item{page.header.height, page.footer.height}{The heights of the page header
-and footer for RTF table outputs. Default values for both are \verb{0.5in}.}
+\item{page.header.height, page.footer.height}{\emph{Set RTF page header and footer distances}
+
+The heights of the page header and footer for RTF table outputs. Default
+values for both are \verb{0.5in}.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/grp_pull.Rd b/man/grp_pull.Rd
index 82a2946932..1214f2ee48 100644
--- a/man/grp_pull.Rd
+++ b/man/grp_pull.Rd
@@ -7,10 +7,19 @@
 grp_pull(data, which)
 }
 \arguments{
-\item{data}{A \code{gt_group} container object, typically generated through use of
-the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
+\item{data}{\emph{The gt table group object}
 
-\item{which}{An index value denoting which \code{gt_tbl} table should be obtained
+\verb{obj:<gt_group>} --- \strong{required}
+
+This is a \code{gt_group} container object. It is typically generated through
+use of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects,
+or, made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
+
+\item{which}{\emph{The table to pull from the group}
+
+\verb{scalar<numeric|integer>} --- \strong{required}
+
+A single index value denoting which \code{gt_tbl} table should be obtained
 from the \code{gt_group} object.}
 }
 \value{
diff --git a/man/grp_replace.Rd b/man/grp_replace.Rd
index adf1baeafc..10e86d0fb7 100644
--- a/man/grp_replace.Rd
+++ b/man/grp_replace.Rd
@@ -7,16 +7,33 @@
 grp_replace(.data, ..., .list = list2(...), .which)
 }
 \arguments{
-\item{.data}{A \code{gt_group} container object, typically generated through use
-of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
+\item{.data}{\emph{The gt table group object}
 
-\item{...}{One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated
-via the \code{\link[=gt]{gt()}} function.}
+\verb{obj:<gt_group>} --- \strong{required}
 
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
+This is a \code{gt_group} container object. It is typically generated through
+use of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects,
+or, made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
 
-\item{.which}{Index values denoting which \code{gt_tbl} tables should be replaced
-in the \code{gt_group} object.}
+\item{...}{\emph{One or more gt table objects}
+
+\verb{obj:<gt_tbl>} --- \strong{required} (or, use \code{...})
+
+One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated via the
+\code{\link[=gt]{gt()}} function.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
+
+\item{.which}{\emph{The tables to replace}
+
+\verb{vector<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A vector of index values denoting which \strong{gt} tables should be replaced
+inside of the \code{gt_group} object.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/grp_rm.Rd b/man/grp_rm.Rd
index 0ed4fe87d0..b56dc79772 100644
--- a/man/grp_rm.Rd
+++ b/man/grp_rm.Rd
@@ -7,10 +7,19 @@
 grp_rm(data, which)
 }
 \arguments{
-\item{data}{A \code{gt_group} container object, typically generated through use of
-the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects.}
+\item{data}{\emph{The gt table group object}
 
-\item{which}{An index value denoting which \code{gt_tbl} table should be removed
+\verb{obj:<gt_group>} --- \strong{required}
+
+This is a \code{gt_group} container object. It is typically generated through
+use of the \code{\link[=gt_group]{gt_group()}} function along with one or more \code{gt_tbl} objects,
+or, made by splitting a \strong{gt} table with \code{\link[=gt_split]{gt_split()}}.}
+
+\item{which}{\emph{The table to remove from the group}
+
+\verb{scalar<numeric|integer>} --- \strong{required}
+
+A single index value denoting which \code{gt_tbl} table should be removed
 from the \code{gt_group} object.}
 }
 \value{
diff --git a/man/gt.Rd b/man/gt.Rd
index 94a2796ee7..a7e55fc7d7 100644
--- a/man/gt.Rd
+++ b/man/gt.Rd
@@ -19,49 +19,92 @@ gt(
 )
 }
 \arguments{
-\item{data}{A \code{data.frame} object or a tibble.}
+\item{data}{\emph{Input data table}
 
-\item{rowname_col}{The column name in the input \code{data} table to use as row
-captions to be placed in the display table stub. If the \code{rownames_to_stub}
-option is \code{TRUE} then any column name provided to \code{rowname_col} will be
-ignored.}
+\verb{obj:<data.frame>|obj:<tbl_df>} --- \strong{required}
 
-\item{groupname_col}{The column name in the input \code{data} table to use as
-group labels for generation of stub row groups. If the input \code{data} table
-has the \code{grouped_df} class (through use of the \code{\link[dplyr:group_by]{dplyr::group_by()}} function
-or associated \verb{group_by*()} functions) then any input here is ignored.}
+A \code{data.frame} object or a tibble (\code{tbl_df}).}
 
-\item{process_md}{Should the contents of the \code{rowname_col} and
-\code{groupname_col} be interpreted as Markdown? By default this is \code{FALSE}.}
+\item{rowname_col}{\emph{Column for row names/labels from \code{data}}
 
-\item{caption}{An optional table caption to use for cross-referencing in R
-Markdown, Quarto, or \strong{bookdown}.}
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{rownames_to_stub}{An option to take rownames from the input \code{data}
-table as row captions in the display table stub.}
+The column name in the input \code{data} table to use as row labels to be placed
+in the table stub. If the \code{rownames_to_stub} option is \code{TRUE} then any
+column name provided to \code{rowname_col} will be ignored.}
 
-\item{row_group_as_column}{An option that alters the display of row group
-labels. By default this is \code{FALSE} and row group labels will appear in
-dedicated rows above their respective groups of rows. If \code{TRUE}, row group
-labels will occupy a secondary column in the table stub.}
+\item{groupname_col}{\emph{Column for group names/labels from \code{data}}
 
-\item{auto_align}{Optionally have column data be aligned depending on the
-content contained in each column of the input \code{data}. Internally, this
-calls \code{cols_align(align = "auto")} for all columns.}
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{id}{The table ID. By default, with \code{NULL}, this will be a random,
-ten-letter ID as generated by using the \code{\link[=random_id]{random_id()}} function. A custom
-table ID can be used with any single-length character vector.}
+The column name in the input \code{data} table to use as group labels for
+generation of stub row groups. If the input \code{data} table has the
+\code{grouped_df} class (through use of the \code{\link[dplyr:group_by]{dplyr::group_by()}} function or
+associated \verb{group_by*()} functions) then any input here is ignored.}
 
-\item{locale}{An optional locale ID that can be set as the default locale for
-all functions that take a \code{locale} argument. Examples of valid locales
-include \code{"en"} for English (United States) and \code{"fr"} for French (France).
-Refer to the information provided by the \code{\link[=info_locales]{info_locales()}} function to
-determine which locales are supported.}
+\item{process_md}{\emph{Process Markdown in \code{rowname_col} and \code{groupname_col}}
 
-\item{row_group.sep}{The separator to use between consecutive group names (a
-possibility when providing \code{data} as a \code{grouped_df} with multiple groups)
-in the displayed stub row group label.}
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the contents of the \code{rowname_col} and \code{groupname_col} be interpreted
+as Markdown? By default this won't happen.}
+
+\item{caption}{\emph{Table caption text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional table caption to use for cross-referencing in R Markdown,
+Quarto, or \strong{bookdown}.}
+
+\item{rownames_to_stub}{\emph{Use data frame row labels in the stub}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to take rownames from the input \code{data} table (should they be
+available) as row labels in the display table stub.}
+
+\item{row_group_as_column}{\emph{Mode for displaying row group labels in the stub}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option that alters the display of row group labels. By default this is
+\code{FALSE} and row group labels will appear in dedicated rows above their
+respective groups of rows. If \code{TRUE} row group labels will occupy a
+secondary column in the table stub.}
+
+\item{auto_align}{\emph{Automatic alignment of column values and labels}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Optionally have column data be aligned depending on the content contained
+in each column of the input \code{data}. Internally, this calls
+\code{cols_align(align = "auto")} for all columns.}
+
+\item{id}{\emph{The table ID}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+By default (with \code{NULL}) this will be a random, ten-letter ID as generated
+by using the \code{\link[=random_id]{random_id()}} function. A custom table ID can be used be
+providing a single-length character vector.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be set as the default locale for all
+functions that take a \code{locale} argument. Examples include \code{"en"} for
+English (United States) and \code{"fr"} for French (France). We can use the
+\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
+are supported.}
+
+\item{row_group.sep}{\emph{Separator text for multiple row group labels}
+
+\verb{scalar<character>} --- \emph{default:} \code{getOption("gt.row_group.sep", " - ")}
+
+The separator to use between consecutive group names (a possibility when
+providing \code{data} as a \code{grouped_df} with multiple groups) in the displayed
+row group label.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/gt_group.Rd b/man/gt_group.Rd
index 6f699ce39d..f0b5f71ca0 100644
--- a/man/gt_group.Rd
+++ b/man/gt_group.Rd
@@ -7,13 +7,25 @@
 gt_group(..., .list = list2(...), .use_grp_opts = FALSE)
 }
 \arguments{
-\item{...}{One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated
-via the \code{\link[=gt]{gt()}} function.}
+\item{...}{\emph{One or more gt table data objects}
 
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
+\verb{obj:<gt_tbl>} --- (\code{optional})
 
-\item{.use_grp_opts}{Should options specified in the \code{gt_group} object be
-applied to all contained \strong{gt} tables? By default this is \code{FALSE}.}
+One or more \strong{gt} table (\code{gt_tbl}) objects, typically generated via the
+\code{\link[=gt]{gt()}} function.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
+
+\item{.use_grp_opts}{\emph{Apply options to all contained tables?}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should options specified in the \code{gt_group} object be applied to all
+contained \strong{gt} tables? By default this is \code{FALSE}.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/gt_output.Rd b/man/gt_output.Rd
index f0851f266a..d17b2ce193 100644
--- a/man/gt_output.Rd
+++ b/man/gt_output.Rd
@@ -7,7 +7,11 @@
 gt_output(outputId)
 }
 \arguments{
-\item{outputId}{An output variable from which to read the table.}
+\item{outputId}{\emph{Shiny output ID}
+
+\verb{scalar<character>} --- \strong{required}
+
+An output variable from which to read the table.}
 }
 \value{
 An object of class \code{shiny.tag}.
diff --git a/man/gt_preview.Rd b/man/gt_preview.Rd
index 52d912cf0c..7d80c1778f 100644
--- a/man/gt_preview.Rd
+++ b/man/gt_preview.Rd
@@ -7,18 +7,33 @@
 gt_preview(data, top_n = 5, bottom_n = 1, incl_rownums = TRUE)
 }
 \arguments{
-\item{data}{A \code{data.frame} object or a tibble.}
+\item{data}{\emph{Input data table}
 
-\item{top_n}{This value will be used as the number of rows from the top of
-the table to display. The default, \code{5}, will show the first five rows of
-the table.}
+\verb{obj:<data.frame>|obj:<tbl_df>} --- \strong{required}
 
-\item{bottom_n}{The value will be used as the number of rows from the bottom
+A \code{data.frame} object or a tibble (\code{tbl_df}).}
+
+\item{top_n}{\emph{Top n rows to display}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{5}
+
+The \code{top_n} value will be used as the number of rows from the top of the
+table to display. The default, \code{5}, will show the first five rows of the
+table.}
+
+\item{bottom_n}{\emph{Bottom n rows to display}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+The \code{bottom_n} value will be used as the number of rows from the bottom
 of the table to display. The default, \code{1}, will show the final row of the
 table.}
 
-\item{incl_rownums}{An option to include the row numbers for \code{data} in the
-table stub. By default, this is \code{TRUE}.}
+\item{incl_rownums}{\emph{Display row numbers}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to include the row numbers for \code{data} in the table stub.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/gt_split.Rd b/man/gt_split.Rd
index 21b5f12ddd..5a4d039a8b 100644
--- a/man/gt_split.Rd
+++ b/man/gt_split.Rd
@@ -7,18 +7,37 @@
 gt_split(data, row_every_n = NULL, row_slice_i = NULL, col_slice_at = NULL)
 }
 \arguments{
-\item{data}{A \strong{gt} table object (\code{gt_tbl}) that is created using the \code{\link[=gt]{gt()}}
-function.}
+\item{data}{\emph{The gt table data object}
 
-\item{row_every_n}{A directive to split at every \emph{n} number of rows. This
-argument expects a single numerical value.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{row_slice_i}{An argument for splitting at specific row indices. Here,
-we expect either a vector of index values or a function that evaluates to a
-numeric vector.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{col_slice_at}{Any columns where vertical splitting across should occur.
-The splits occur to the right of the resolved column names.}
+\item{row_every_n}{\emph{Split at every n rows}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A directive to split at every \emph{n} number of rows. This argument expects a
+single numerical value.}
+
+\item{row_slice_i}{\emph{Row-slicing indices}
+
+\verb{vector<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An argument for splitting at specific row indices. Here, we expect either a
+vector of index values or a function that evaluates to a numeric vector.}
+
+\item{col_slice_at}{\emph{Column-slicing locations}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Any columns where vertical splitting across should occur. The splits occur
+to the right of the resolved column names. Can either be a series of column
+names provided in \code{\link[=c]{c()}}, a vector of column indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}.}
 }
 \value{
 An object of class \code{gt_group}.
diff --git a/man/gtsave.Rd b/man/gtsave.Rd
index a9a4b13929..754221041f 100644
--- a/man/gtsave.Rd
+++ b/man/gtsave.Rd
@@ -7,18 +7,33 @@
 gtsave(data, filename, path = NULL, ...)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{filename}{The file name to create on disk. Ensure that an extension
-compatible with the output types is provided (\code{.html}, \code{.tex}, \code{.ltx},
-\code{.rtf}, \code{.docx}). If a custom save function is provided then the file
-extension is disregarded.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{path}{An optional path to which the file should be saved (combined with
-filename).}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{...}{All other options passed to the appropriate internal saving
-function.}
+\item{filename}{\emph{Output filename}
+
+\verb{scalar<character>} --- \strong{required}
+
+The file name to create on disk. Ensure that an extension compatible with
+the output types is provided (\code{.html}, \code{.tex}, \code{.ltx}, \code{.rtf}, \code{.docx}). If
+a custom save function is provided then the file extension is disregarded.}
+
+\item{path}{\emph{Output path}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional path to which the file should be saved (combined with
+\code{filename}).}
+
+\item{...}{\emph{Additional options}
+
+\verb{<named arguments>}
+
+All other options passed to the appropriate internal saving function.}
 }
 \value{
 Invisibly returns \code{TRUE} if the export process is successful.
diff --git a/man/html.Rd b/man/html.Rd
index 5f9fb665d9..ca57d1d938 100644
--- a/man/html.Rd
+++ b/man/html.Rd
@@ -7,8 +7,19 @@
 html(text, ...)
 }
 \arguments{
-\item{text, ...}{The text that is understood to be HTML text, which is to be
-preserved.}
+\item{text}{\emph{HTML text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text that is understood to be HTML text, which is to be preserved in
+the HTML output context.}
+
+\item{...}{\emph{Optional parameters for \code{htmltools::HTML()}}
+
+\verb{<multiple expressions>} --- (\code{optional})
+
+The \code{htmltools::HTML()} function contains \code{...} and anything provided here
+will be passed to that internal function call.}
 }
 \value{
 A character object of class \code{html}. It's tagged as an HTML fragment
diff --git a/man/info_currencies.Rd b/man/info_currencies.Rd
index 810a3b6b4e..aaea53ed36 100644
--- a/man/info_currencies.Rd
+++ b/man/info_currencies.Rd
@@ -7,15 +7,23 @@
 info_currencies(type = c("code", "symbol"), begins_with = NULL)
 }
 \arguments{
-\item{type}{The type of currency information provided. Can either be \code{code}
-where currency information corresponding to 3-letter currency codes is
-provided, or \code{symbol} where currency info for common currency names (e.g.,
-dollar, pound, yen, etc.) is returned.}
-
-\item{begins_with}{Providing a single letter will filter currencies to only
-those that begin with that letter in their currency code. The default
-(\code{NULL}) will produce a table with all currencies displayed. This option
-only constrains the information table where \code{type == "code"}.}
+\item{type}{\emph{Type of currency}
+
+\verb{singl-kw:[code|symbol]} --- \emph{default:} \code{"code"}
+
+The type of currency information provided. Can either be \code{code} where
+currency information corresponding to 3-letter currency codes is provided,
+or \code{symbol} where currency info for common currency names (e.g., dollar,
+pound, yen, etc.) is returned.}
+
+\item{begins_with}{\emph{Show currencies beginning with a specific letter}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Providing a single letter will filter currencies to only those that begin
+with that letter in their currency code. The default (\code{NULL}) will produce
+a table with all currencies displayed. This option only constrains the
+information table where \code{type == "code"}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/info_locales.Rd b/man/info_locales.Rd
index 07cff0e1f7..0fe2290945 100644
--- a/man/info_locales.Rd
+++ b/man/info_locales.Rd
@@ -7,9 +7,13 @@
 info_locales(begins_with = NULL)
 }
 \arguments{
-\item{begins_with}{Providing a single letter will filter locales to only
-those that begin with that letter in their base locale ID. The default
-(\code{NULL}) will produce a table with all locales displayed.}
+\item{begins_with}{\emph{Show locales beginning with a specific letter}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Providing a single letter will filter locales to only those that begin
+with that letter in their locale ID. The default (\code{NULL}) will produce
+a table with all locales displayed}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/info_paletteer.Rd b/man/info_paletteer.Rd
index 977974939c..50a63e40c1 100644
--- a/man/info_paletteer.Rd
+++ b/man/info_paletteer.Rd
@@ -7,10 +7,14 @@
 info_paletteer(color_pkgs = NULL)
 }
 \arguments{
-\item{color_pkgs}{A vector of color packages that determines which sets of
-palettes should be displayed in the information table. If this is
-\code{NULL} (the default) then all of the discrete palettes from all of the
-color packages represented in \strong{paletteer} will be displayed.}
+\item{color_pkgs}{\emph{Filter to specific color packages}
+
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A vector of color packages that determines which sets of palettes should be
+displayed in the information table. If this is \code{NULL} (the default) then
+all of the discrete palettes from all of the color packages represented in
+\strong{paletteer} will be displayed.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/local_image.Rd b/man/local_image.Rd
index 5bf9e969ab..f96ea684a6 100644
--- a/man/local_image.Rd
+++ b/man/local_image.Rd
@@ -7,9 +7,18 @@
 local_image(filename, height = 30)
 }
 \arguments{
-\item{filename}{A path to an image file.}
+\item{filename}{\emph{Path to image file}
 
-\item{height}{The absolute height (px) of the image in the table cell.}
+\verb{scalar<character>} --- \strong{required}
+
+A local path to an image file on disk.}
+
+\item{height}{\emph{Height of image}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{30}
+
+The absolute height of the image in the table cell (in \code{"px"} units). By
+default, this is set to \code{"30px"}.}
 }
 \value{
 A character object with an HTML fragment that can be placed inside of
diff --git a/man/md.Rd b/man/md.Rd
index b350588b3d..e28d7cb3eb 100644
--- a/man/md.Rd
+++ b/man/md.Rd
@@ -7,11 +7,15 @@
 md(text)
 }
 \arguments{
-\item{text}{The text that is understood to contain Markdown formatting.}
+\item{text}{\emph{Markdown text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text that is understood to contain Markdown formatting.}
 }
 \value{
 A character object of class \code{from_markdown}. It's tagged as being
-Markdown text and it will undergo conversion to HTML.
+Markdown text and it will undergo conversion to the desired output context.
 }
 \description{
 Markdown! It's a wonderful thing. We can use it in certain places (e.g.,
diff --git a/man/opt_align_table_header.Rd b/man/opt_align_table_header.Rd
index 5021b1d5c2..43e1903a0d 100644
--- a/man/opt_align_table_header.Rd
+++ b/man/opt_align_table_header.Rd
@@ -7,10 +7,19 @@
 opt_align_table_header(data, align = c("left", "center", "right"))
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{align}{The alignment of the title and subtitle elements in the table
-header. Options are \code{"left"} (the default), \code{"center"}, or \code{"right"}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{align}{\emph{Header alignment}
+
+\verb{singl-kw:[left|center|right]} --- \emph{default:} \code{"left"}
+
+The alignment of the title and subtitle elements in the table header.
+Options are \code{"left"} (the default), \code{"center"}, or \code{"right"}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_all_caps.Rd b/man/opt_all_caps.Rd
index d1ea8be36a..80b35973d1 100644
--- a/man/opt_all_caps.Rd
+++ b/man/opt_all_caps.Rd
@@ -11,15 +11,28 @@ opt_all_caps(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{all_caps}{A logical value to indicate whether the text transformation
-to all caps should be performed (\code{TRUE}, the default) or reset to default
-values (\code{FALSE}) for the \code{locations} targeted.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{locations}{Which locations should undergo this text transformation? By
-default it includes all of the \code{"column_labels"}, the \code{"stub"}, and the
-\code{"row_group"} locations. However, we could just choose one or two of those.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{all_caps}{\emph{Use all-caps transformation}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value to indicate whether the text transformation to all caps
+should be performed (\code{TRUE}, the default) or reset to default values
+(\code{FALSE}) for the \code{locations} targeted.}
+
+\item{locations}{\emph{Locations to target}
+
+\verb{mult-kw:[column_labels|stub|row_group]} --- \emph{default:} \code{c("column_labels", "stub", "row_group")}
+
+Which locations should undergo this text transformation? By default it
+includes all of the \code{"column_labels"}, the \code{"stub"}, and the \code{"row_group"}
+locations. However, we could just choose one or two of those.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_css.Rd b/man/opt_css.Rd
index 6fbcc82305..5785e91ddb 100644
--- a/man/opt_css.Rd
+++ b/man/opt_css.Rd
@@ -7,20 +7,35 @@
 opt_css(data, css, add = TRUE, allow_duplicates = FALSE)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{css}{The CSS to include as part of the rendered table's \verb{<style>}
-element.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{add}{If \code{TRUE}, the default, the CSS is added to any already-defined
-CSS (typically from previous calls of \code{\link[=opt_table_font]{opt_table_font()}}, \code{opt_css()}, or,
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{css}{\emph{CSS declarations}
+
+\verb{scalar<character>} --- \strong{required}
+
+The CSS to include as part of the rendered table's \verb{<style>} element.}
+
+\item{add}{\emph{Add to existing CSS}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+If \code{TRUE}, the default, the CSS is added to any already-defined CSS
+(typically from previous calls of \code{\link[=opt_table_font]{opt_table_font()}}, \code{opt_css()}, or,
 directly setting CSS the \code{table.additional_css} value in \code{\link[=tab_options]{tab_options()}}).
 If this is set to \code{FALSE}, the CSS provided here will replace any
 previously-stored CSS.}
 
-\item{allow_duplicates}{When this is \code{FALSE} (the default), the CSS provided
-here won't be added (provided that \code{add = TRUE}) if it is seen in the
-already-defined CSS.}
+\item{allow_duplicates}{\emph{Allow for CSS duplication}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+When this is \code{FALSE} (the default), the CSS provided here won't be added
+(provided that \code{add = TRUE}) if it is seen in the already-defined CSS.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_footnote_marks.Rd b/man/opt_footnote_marks.Rd
index ff9476a5b1..7935a722cf 100644
--- a/man/opt_footnote_marks.Rd
+++ b/man/opt_footnote_marks.Rd
@@ -7,12 +7,21 @@
 opt_footnote_marks(data, marks = "numbers")
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{marks}{Either a character vector of length greater than 1 (that will
-represent the series of marks) or a single keyword that represents a preset
-sequence of marks. The valid keywords are: \code{"numbers"} (for numeric marks),
-\code{"letters"} and \code{"LETTERS"} (for lowercase and uppercase alphabetic marks),
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{marks}{\emph{Sequence of footnote marks}
+
+\verb{vector<character>} --- \emph{default:} \code{"numbers"}
+
+Either a character vector of length greater than 1 (that will represent the
+series of marks) or a single keyword that represents a preset sequence of
+marks. The valid keywords are: \code{"numbers"} (for numeric marks), \code{"letters"}
+and \code{"LETTERS"} (for lowercase and uppercase alphabetic marks),
 \code{"standard"} (for a traditional set of four symbol marks), and \code{"extended"}
 (which adds two more symbols to the standard set).}
 }
diff --git a/man/opt_footnote_spec.Rd b/man/opt_footnote_spec.Rd
index 67aa4e8926..6b31c6e997 100644
--- a/man/opt_footnote_spec.Rd
+++ b/man/opt_footnote_spec.Rd
@@ -7,12 +7,21 @@
 opt_footnote_spec(data, spec_ref = NULL, spec_ftr = NULL)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{spec_ref, spec_ftr}{Specification of the footnote marks when behaving as
-footnote references and as marks in the footer section of the table. This
-is a string containing spec characters. The default is the spec string
-\code{"^i"}, which is superscript text set in italics.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{spec_ref, spec_ftr}{\emph{Specifications for formatting of footnote marks}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Specification of the footnote marks when behaving as footnote references
+and as marks in the footer section of the table. This is a string
+containing spec characters. The default is the spec string \code{"^i"}, which is
+superscript text set in italics.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_horizontal_padding.Rd b/man/opt_horizontal_padding.Rd
index f969d462b9..6c3e64f412 100644
--- a/man/opt_horizontal_padding.Rd
+++ b/man/opt_horizontal_padding.Rd
@@ -7,10 +7,19 @@
 opt_horizontal_padding(data, scale = 1)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{scale}{A scale factor by which the horizontal padding will be adjusted.
-Must be a number between \code{0} and \code{3}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{scale}{\emph{Scale factor}
+
+\verb{scalar<numeric|integer>(0>=val>=3)} --- \emph{default:} \code{1}
+
+A scale factor by which the horizontal padding will be adjusted. Must be a
+number between \code{0} and \code{3}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_interactive.Rd b/man/opt_interactive.Rd
index 6c1880c8e2..70b37518aa 100644
--- a/man/opt_interactive.Rd
+++ b/man/opt_interactive.Rd
@@ -23,60 +23,122 @@ opt_interactive(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{active}{The \code{active} option will either enable or disable interactive
-features for an HTML table. The individual features of an interactive HTML
-table are controlled by the other options.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{use_pagination}{This is the option for using pagination controls (below
-the table body). By default, this is \code{TRUE} and it will allow the use to
-page through table content.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{use_pagination_info}{If \code{use_pagination} is \code{TRUE} then the
-\code{use_pagination_info} option can be used to display informational text
-regarding the current page view (this is set to \code{TRUE} by default).}
+\item{active}{\emph{Display interactive HTML table}
 
-\item{use_sorting}{This option provides controls for sorting column values.
-By default, this is \code{TRUE}.}
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{use_search}{The \code{use_search} option places a search field for globally
-filtering rows to the requested content. By default, this is \code{FALSE}.}
+The \code{active} option will either enable or disable interactive features for
+an HTML table. The individual features of an interactive HTML table are
+controlled by the other options.}
 
-\item{use_filters}{The \code{use_filters} option places search fields below each
-column header and allows for filtering by column. By default, this is
-\code{FALSE}.}
+\item{use_pagination}{\emph{Display pagination controls}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+This is the option for using pagination controls (below the table body). By
+default, this is \code{TRUE} and it will allow the use to page through table
+content.}
+
+\item{use_pagination_info}{\emph{Display pagination info}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+If \code{use_pagination} is \code{TRUE} then the \code{use_pagination_info} option can be
+used to display informational text regarding the current page view (this is
+set to \code{TRUE} by default).}
+
+\item{use_sorting}{\emph{Provide column sorting controls}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+This option provides controls for sorting column values. By default, this
+is \code{TRUE}.}
+
+\item{use_search}{\emph{Provide a global search field}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+The \code{use_search} option places a search field for globally filtering rows
+to the requested content. By default, this is \code{FALSE}.}
+
+\item{use_filters}{\emph{Display filtering fields}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+The \code{use_filters} option places search fields below each column header and
+allows for filtering by column. By default, this is \code{FALSE}.}
+
+\item{use_resizers}{\emph{Allow column resizing}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+This option allows for the interactive resizing of columns. By default,
+this is \code{FALSE}.}
 
-\item{use_resizers}{This option allows for the interactive resizing of
-columns. By default, this is \code{FALSE}.}
+\item{use_highlight}{\emph{Enable row highlighting on hover}
 
-\item{use_highlight}{The \code{use_highlight} option highlights individual rows
-upon hover. By default, this is \code{FALSE}.}
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{use_compact_mode}{To reduce vertical padding and thus make the table
-consume less vertical space the \code{use_compact_mode} option can be used. By
+The \code{use_highlight} option highlights individual rows upon hover. By
 default, this is \code{FALSE}.}
 
-\item{use_text_wrapping}{The \code{use_text_wrapping} option controls whether
-text wrapping occurs throughout the table. This is \code{TRUE} by default and
-with that text will be wrapped to multiple lines. If \code{FALSE}, text will be
-truncated to a single line.}
-
-\item{use_page_size_select, page_size_default, page_size_values}{The
-\code{use_page_size_select} option lets us display a dropdown menu for the
-number of rows to show per page of data. By default, this is the vector
-\code{c(10, 25, 50, 100)} which corresponds to options for \code{10}, \code{25}, \code{50}, and
-\code{100} rows of data per page. To modify these page-size options, provide a
-numeric vector to \code{page_size_values}. The default page size (initially set
-as \code{10}) can be modified with \code{page_size_default} and this works whether or
-not \code{use_page_size_select} is set to \code{TRUE}.}
-
-\item{pagination_type}{When using pagination the \code{pagination_type} option
-lets us select between one of three options for the layout of pagination
-controls. The default is \code{"numbers"}, where a series of page-number buttons
-is presented along with 'previous' and 'next' buttons. The \code{"jump"} option
-provides an input field with a stepper for the page number. With
-\code{"simple"}, only the 'previous' and 'next' buttons are displayed.}
+\item{use_compact_mode}{\emph{Use compact mode}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+To reduce vertical padding and thus make the table consume less vertical
+space the \code{use_compact_mode} option can be used. By default, this is
+\code{FALSE}.}
+
+\item{use_text_wrapping}{\emph{Use text wrapping}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+The \code{use_text_wrapping} option controls whether text wrapping occurs
+throughout the table. This is \code{TRUE} by default and with that text will be
+wrapped to multiple lines. If \code{FALSE}, text will be truncated to a single
+line.}
+
+\item{use_page_size_select}{\emph{Allow for page size selection}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+The \code{use_page_size_select} option lets us display a dropdown menu for the
+number of rows to show per page of data.}
+
+\item{page_size_default}{\emph{Change the default page size}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{10}
+
+The default page size (initially set as \code{10}) can be modified with
+\code{page_size_default} and this works whether or not \code{use_page_size_select} is
+set to \code{TRUE}.}
+
+\item{page_size_values}{\emph{Set of page-size values}
+
+\verb{vector<numeric|integer>} --- \emph{default:} \code{c(10, 25, 50, 100)}
+
+By default, this is the vector \code{c(10, 25, 50, 100)} which corresponds to
+options for \code{10}, \code{25}, \code{50}, and \code{100} rows of data per page. To modify
+these page-size options, provide a numeric vector to \code{page_size_values}.}
+
+\item{pagination_type}{\emph{Change pagination mode}
+
+\verb{scalar<character>} --- \emph{default:} \code{"numbers"}
+
+When using pagination the \code{pagination_type} option lets us select between
+one of three options for the layout of pagination controls. The default is
+\code{"numbers"}, where a series of page-number buttons is presented along with
+'previous' and 'next' buttons. The \code{"jump"} option provides an input field
+with a stepper for the page number. With \code{"simple"}, only the 'previous'
+and 'next' buttons are displayed.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_row_striping.Rd b/man/opt_row_striping.Rd
index 3e03072cef..af2b2f4f70 100644
--- a/man/opt_row_striping.Rd
+++ b/man/opt_row_striping.Rd
@@ -7,10 +7,19 @@
 opt_row_striping(data, row_striping = TRUE)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{row_striping}{A logical value to indicate whether row striping should
-be added or removed.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{row_striping}{\emph{Use alternating row stripes}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value to indicate whether row striping should be added or
+removed.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_stylize.Rd b/man/opt_stylize.Rd
index 83911193dd..fd1f76b6c3 100644
--- a/man/opt_stylize.Rd
+++ b/man/opt_stylize.Rd
@@ -7,16 +7,32 @@
 opt_stylize(data, style = 1, color = "blue", add_row_striping = TRUE)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{style}{Six numbered styles are available. Simply provide a number from
-\code{1} (the default) to \code{6} to choose a distinct look.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{color}{There are six color variations: \code{"blue"} (the default),
-\code{"cyan"}, \code{"pink"}, \code{"green"}, \code{"red"}, and \code{"gray"}.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{add_row_striping}{An option to enable row striping in the table body
-for the style chosen. By default, this is \code{TRUE}.}
+\item{style}{\emph{Table style}
+
+\verb{scalar<numeric|integer>(1>=val>=6)} --- \emph{default:} \code{1}
+
+Six numbered styles are available. Simply provide a number from \code{1} (the
+default) to \code{6} to choose a distinct look.}
+
+\item{color}{\emph{Color variation}
+
+\verb{scalar<character>} --- \emph{default:} \code{"blue"}
+
+There are six color variations: \code{"blue"}, \code{"cyan"}, \code{"pink"}, \code{"green"},
+\code{"red"}, and \code{"gray"}.}
+
+\item{add_row_striping}{\emph{Allow row striping}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to enable row striping in the table body for the \code{style} chosen.}
 }
 \value{
 an object of class \code{gt_tbl}.
diff --git a/man/opt_table_font.Rd b/man/opt_table_font.Rd
index 38223e0c64..a2c4a2202c 100644
--- a/man/opt_table_font.Rd
+++ b/man/opt_table_font.Rd
@@ -14,30 +14,54 @@ opt_table_font(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{font}{One or more font names available as system or web fonts. These
-can be combined with a \code{c()} or a \code{list()}. To choose fonts from the
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{font}{\emph{Default table fonts}
+
+\verb{vector<character>|list|obj:<font_css>} --- \emph{default:} \code{NULL} (\code{optional})
+
+One or more font names available as system or web fonts. These can be
+combined with a \code{c()} or a \code{list()}. To choose fonts from the
 \emph{Google Fonts} service, we can call the \code{\link[=google_font]{google_font()}} helper function.}
 
-\item{stack}{A keyword that represents the name of a font stack (obtained via
-internally via the \code{\link[=system_fonts]{system_fonts()}} helper function). If provided, this new
-stack will replace any defined fonts and any \code{font} values will be
-prepended.}
+\item{stack}{\emph{Name of font stack}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A name that is representative of a font stack (obtained via internally via
+the \code{\link[=system_fonts]{system_fonts()}} helper function). If provided, this new stack will
+replace any defined fonts and any \code{font} values will be prepended.}
+
+\item{weight}{\emph{Text weight}
+
+\verb{scalar<character|numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Option to set the weight of the font. Can be a text-based keyword such as
+\code{"normal"}, \code{"bold"}, \code{"lighter"}, \code{"bolder"}, or, a numeric value between
+\code{1} and \code{1000}, inclusive. Please note that typefaces have varying support
+for the numeric mapping of weight.}
+
+\item{style}{\emph{Text style}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An option to modify the text style. Can be one of either \code{"normal"},
+\code{"italic"}, or \code{"oblique"}.}
 
-\item{weight}{Option to set the weight of the font. Can be a text-based
-keyword such as \code{"normal"}, \code{"bold"}, \code{"lighter"}, \code{"bolder"}, or, a
-numeric value between \code{1} and \code{1000}, inclusive. Please note that typefaces
-have varying support for the numeric mapping of weight.}
+\item{add}{\emph{Add to existing fonts}
 
-\item{style}{An option to modify the text style. Can be one of either
-\code{"normal"}, \code{"italic"}, or \code{"oblique"}.}
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{add}{Should this font be added to the beginning of any already-defined
-fonts for the table? By default, this is \code{TRUE} and is recommended since
-those fonts already present can serve as fallbacks when everything
-specified in \code{font} is not available. If a \code{stack} is provided, then \code{add}
-will automatically set to \code{FALSE}.}
+Should fonts be added to the beginning of any already-defined fonts for the
+table? By default, this is \code{TRUE} and is recommended since those fonts
+already present can serve as fallbacks when everything specified in \code{font}
+is not available. If a \code{stack} is provided, then \code{add} will automatically
+set to \code{FALSE}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_table_lines.Rd b/man/opt_table_lines.Rd
index 6c20b951c9..5b77897e03 100644
--- a/man/opt_table_lines.Rd
+++ b/man/opt_table_lines.Rd
@@ -7,10 +7,19 @@
 opt_table_lines(data, extent = c("all", "none", "default"))
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{extent}{The extent to which lines will be visible in the table. Options
-are \code{"all"}, \code{"none"}, or \code{"default"}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{extent}{\emph{Extent of lines added}
+
+\verb{singl-kw:[all|none|default]} --- \emph{default:} \code{"all"}
+
+The extent to which lines will be visible in the table. Options are
+\code{"all"}, \code{"none"}, or \code{"default"}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_table_outline.Rd b/man/opt_table_outline.Rd
index 0e7c6f536d..3e082aa693 100644
--- a/man/opt_table_outline.Rd
+++ b/man/opt_table_outline.Rd
@@ -7,12 +7,33 @@
 opt_table_outline(data, style = "solid", width = px(3), color = "#D3D3D3")
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{style, width, color}{The style, width, and color properties for the table
-outline. By default, these are \code{"solid"}, \code{px(3)} (or, \code{"3px"}), and
-\code{"#D3D3D3"}. If \code{"none"} is used then the outline is removed and any values
-provided for \code{width} and \code{color} will be ignored (i.e., not set).}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{style}{\emph{Outline style property}
+
+\verb{scalar<character>} --- \emph{default:} \code{"solid"}
+
+The style property for the table outline. By default, this is \code{"solid"}. If
+\code{"none"} is used then the outline is removed and any values provided for
+\code{width} and \code{color} will be ignored (i.e., not set).}
+
+\item{width}{\emph{Outline width value}
+
+\verb{scalar<character>} --- \emph{default:} \code{px(3)}
+
+The width property for the table outline. By default, this is \code{px(3)} (or,
+\code{"3px"}).}
+
+\item{color}{\emph{Color of outline}
+
+\verb{scalar<character>} --- \emph{default:} \code{"#D3D3D3"}
+
+The color of the table outline. By default, this is \code{"#D3D3D3"}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/opt_vertical_padding.Rd b/man/opt_vertical_padding.Rd
index 023c12b6fe..fe60cbdd8d 100644
--- a/man/opt_vertical_padding.Rd
+++ b/man/opt_vertical_padding.Rd
@@ -7,10 +7,19 @@
 opt_vertical_padding(data, scale = 1)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{scale}{A scale factor by which the vertical padding will be adjusted.
-Must be a number between \code{0} and \code{3}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{scale}{\emph{Scale factor}
+
+\verb{scalar<numeric|integer>(0>=val>=3)} --- \emph{default:} \code{1}
+
+A scale factor by which the vertical padding will be adjusted. Must be a
+number between \code{0} and \code{3}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/pct.Rd b/man/pct.Rd
index c4d56d716d..c52785c063 100644
--- a/man/pct.Rd
+++ b/man/pct.Rd
@@ -7,9 +7,12 @@
 pct(x)
 }
 \arguments{
-\item{x}{the numeric value to format as a string percentage for some
-\code{\link[=tab_options]{tab_options()}} arguments that can take percentage values
-(e.g., \code{table.width}).}
+\item{x}{\emph{Numeric value in percent}
+
+\verb{scalar<numeric|integer>} --- \strong{required}
+
+The numeric value to format as a string percentage for some \code{\link[=tab_options]{tab_options()}}
+arguments that can take percentage values (e.g., \code{table.width}).}
 }
 \value{
 A character vector with a single value in percentage units.
diff --git a/man/px.Rd b/man/px.Rd
index b69b571562..dbe91a28d3 100644
--- a/man/px.Rd
+++ b/man/px.Rd
@@ -7,9 +7,13 @@
 px(x)
 }
 \arguments{
-\item{x}{the numeric value to format as a string (e.g., \code{"12px"}) for
-some \code{\link[=tab_options]{tab_options()}} arguments that can take values as units of
-pixels (e.g., \code{table.font.size}).}
+\item{x}{\emph{Numeric length in pixels}
+
+\verb{scalar<numeric|integer>} --- \strong{required}
+
+The numeric value to format as a string (e.g., \code{"12px"}) for some
+\code{\link[=tab_options]{tab_options()}} arguments that can take values as units of pixels (e.g.,
+\code{table.font.size}).}
 }
 \value{
 A character vector with a single value in pixel units.
diff --git a/man/random_id.Rd b/man/random_id.Rd
index 3eab1cd3ea..c4c6c786a4 100644
--- a/man/random_id.Rd
+++ b/man/random_id.Rd
@@ -7,7 +7,12 @@
 random_id(n = 10)
 }
 \arguments{
-\item{n}{The number of lowercase letters to use for the random ID.}
+\item{n}{\emph{Number of letters}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{10}
+
+The \code{n} argument defines the number of lowercase letters to use for the
+random ID.}
 }
 \value{
 A character vector containing a single, random ID.
diff --git a/man/render_gt.Rd b/man/render_gt.Rd
index acdf5467da..917445de43 100644
--- a/man/render_gt.Rd
+++ b/man/render_gt.Rd
@@ -15,28 +15,53 @@ render_gt(
 )
 }
 \arguments{
-\item{expr}{An expression that creates a \strong{gt} table object. For sake of
-convenience, a data frame or tibble can be used here (it will be
-automatically introduced to \code{\link[=gt]{gt()}} with its default options).}
+\item{expr}{\emph{Expression}
 
-\item{width, height}{The width and height of the table's container. Either can
-be specified as a single-length character with units of pixels or as a
-percentage. If provided as a single-length numeric vector, it is assumed
-that the value is given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper
-functions can also be used to pass in numeric values and obtain values as
-pixel or percent units.}
+\verb{<expression>|obj:<data.frame>|obj:<tbl_df>}
 
-\item{align}{The alignment of the table in its container. By default, this is
-\code{"center"}. Other options are \code{"left"} and \code{"right"}.}
+An expression that creates a \strong{gt} table object. For sake of convenience,
+a data frame or tibble can be used here (it will be automatically
+introduced to \code{\link[=gt]{gt()}} with its default options).}
 
-\item{env}{The environment in which to evaluate the \code{expr}.}
+\item{width, height}{\emph{Dimensions of table container}
 
-\item{quoted}{Is \code{expr} a quoted expression (with \code{quote()})? This is useful
-if you want to save an expression in a variable.}
+\verb{scalar<numeric|integer|character>} --- \emph{default:} \code{NULL} (\code{optional})
 
-\item{outputArgs}{A list of arguments to be passed through to the implicit
-call to \code{\link[=gt_output]{gt_output()}} when \code{render_gt()} is used in an interactive R
-Markdown document.}
+The width and height of the table's container. Either can be specified as a
+single-length character vector with units of pixels or as a percentage. If
+provided as a single-length numeric vector, it is assumed that the value is
+given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper functions can also
+be used to pass in numeric values and obtain values as pixel or percent
+units.}
+
+\item{align}{\emph{Table alignment}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The alignment of the table in its container. If \code{NULL}, the table will be
+center-aligned. Valid options for this are: \code{"center"}, \code{"left"}, and
+\code{"right"}.}
+
+\item{env}{\emph{Evaluation environment}
+
+\verb{<environment>} --- \emph{default:} \code{parent.frame()}
+
+The environment in which to evaluate the \code{expr}.}
+
+\item{quoted}{\emph{Option to \code{quote()} \code{expr}}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Is \code{expr} a quoted expression (with \code{quote()})? This is useful if you want
+to save an expression in a variable.}
+
+\item{outputArgs}{\emph{Output arguments}
+
+\code{list} --- \emph{default:} \code{list()}
+
+A list of arguments to be passed through to the implicit call to
+\code{\link[=gt_output]{gt_output()}} when \code{render_gt()} is used in an interactive R Markdown
+document.}
 }
 \value{
 An object of class \code{shiny.render.function}.
diff --git a/man/rm_caption.Rd b/man/rm_caption.Rd
index 4510ee9810..eb9bdedfa5 100644
--- a/man/rm_caption.Rd
+++ b/man/rm_caption.Rd
@@ -7,7 +7,12 @@
 rm_caption(data)
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/rm_footnotes.Rd b/man/rm_footnotes.Rd
index 891ca36534..62a7fb0980 100644
--- a/man/rm_footnotes.Rd
+++ b/man/rm_footnotes.Rd
@@ -7,13 +7,22 @@
 rm_footnotes(data, footnotes = everything())
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
+\item{data}{\emph{The gt table data object}
 
-\item{footnotes}{A specification of which footnotes should be removed.
-The footnotes to be removed can be given as a vector of integer values
-(they are stored as integer positions, in order of creation, starting at
-\code{1}). A select helper can also be used and, by default, this is
-\code{everything()} (whereby all footnotes will be removed).}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{footnotes}{\emph{Footnotes to remove}
+
+\verb{scalar<numeric|integer>|everything()} --- \emph{default:} \code{everything()}
+
+A specification of which footnotes should be removed. The footnotes to be
+removed can be given as a vector of integer values (they are stored as
+integer positions, in order of creation, starting at \code{1}). A select helper
+can also be used and, by default, this is \code{everything()} (whereby all
+footnotes will be removed).}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/rm_header.Rd b/man/rm_header.Rd
index 92ce3a4b2a..755f73bdf2 100644
--- a/man/rm_header.Rd
+++ b/man/rm_header.Rd
@@ -7,7 +7,12 @@
 rm_header(data)
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/rm_source_notes.Rd b/man/rm_source_notes.Rd
index 2be27fe05b..e4bac8fa1e 100644
--- a/man/rm_source_notes.Rd
+++ b/man/rm_source_notes.Rd
@@ -7,13 +7,22 @@
 rm_source_notes(data, source_notes = everything())
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
+\item{data}{\emph{The gt table data object}
 
-\item{source_notes}{A specification of which source notes should be removed.
-The source notes to be removed can be given as a vector of integer values
-(they are stored as integer positions, in order of creation, starting at
-\code{1}). A select helper can also be used and, by default, this is
-\code{everything()} (whereby all source notes will be removed).}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{source_notes}{\emph{Source notes to remove}
+
+\verb{scalar<numeric|integer>|everything()} --- \emph{default:} \code{everything()}
+
+A specification of which source notes should be removed. The source notes
+to be removed can be given as a vector of integer values (they are stored
+as integer positions, in order of creation, starting at \code{1}). A select
+helper can also be used and, by default, this is \code{everything()} (whereby
+all source notes will be removed).}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/rm_spanners.Rd b/man/rm_spanners.Rd
index e832751be1..ad971435c5 100644
--- a/man/rm_spanners.Rd
+++ b/man/rm_spanners.Rd
@@ -7,19 +7,31 @@
 rm_spanners(data, spanners = everything(), levels = NULL)
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
-
-\item{spanners}{A specification of which spanner column labels should be
-removed. Those to be removed can be given as a vector of spanner ID values
-(every spanner column label has one, either set by the user or by \strong{gt}
-when using \code{\link[=tab_spanner_delim]{tab_spanner_delim()}}). A select helper can also be used and, by
-default, this is \code{everything()} (whereby all spanner column labels will be
-removed).}
-
-\item{levels}{Instead of removing spanner column labels by ID values, entire
-levels of spanners can instead be removed. Supply a numeric vector of level
-values (the first level is \code{1}) and, if they are present, they will be
-removed. Any input given to \code{level} will mean that \code{spanners} is ignored.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{spanners}{\emph{Spanners to remove}
+
+\verb{<spanner-targeting expression>} --- \emph{default:} \code{everything()}
+
+A specification of which spanner column labels should be removed. Those to
+be removed can be given as a vector of spanner ID values (every spanner
+column label has one, either set by the user or by \strong{gt} when using
+\code{\link[=tab_spanner_delim]{tab_spanner_delim()}}). A select helper can also be used and, by default,
+this is \code{everything()} (whereby all spanner column labels will be removed).}
+
+\item{levels}{\emph{Spanner levels to remove}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Instead of removing spanner column labels by ID values, entire levels of
+spanners can instead be removed. Supply a numeric vector of level values
+(the first level is \code{1}) and, if they are present, they will be removed.
+Any input given to \code{level} will mean that \code{spanners} is ignored.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/rm_stubhead.Rd b/man/rm_stubhead.Rd
index 1ffb30597a..a5da0c81c1 100644
--- a/man/rm_stubhead.Rd
+++ b/man/rm_stubhead.Rd
@@ -7,7 +7,12 @@
 rm_stubhead(data)
 }
 \arguments{
-\item{data}{A table object of class \code{gt_tbl}.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/row_group_order.Rd b/man/row_group_order.Rd
index 535555d360..6656671da3 100644
--- a/man/row_group_order.Rd
+++ b/man/row_group_order.Rd
@@ -7,12 +7,21 @@
 row_group_order(data, groups)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{groups}{A character vector of row group ID values corresponding to the
-revised ordering. While this vector must contain valid group ID values, it
-is not required to have all of the row group IDs within it; any omitted
-values will be added to the end while preserving the original ordering.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{groups}{\emph{Specification of row group IDs}
+
+\verb{vector<character>} --- \strong{required}
+
+A character vector of row group ID values corresponding to the revised
+ordering. While this vector must contain valid group ID values, it is not
+required to have all of the row group IDs within it; any omitted values
+will be added to the end while preserving the original ordering.}
 }
 \value{
 An object of class \code{gt_tbl}.
@@ -29,9 +38,9 @@ ordering.
 \section{Examples}{
 
 
-Use \code{\link{exibble}} to create a \strong{gt} table with a stub and with row groups.
-Modify the order of the row groups with \code{row_group_order()}, specifying the
-new ordering in \code{groups}.
+Let's use \code{\link{exibble}} to create a \strong{gt} table with a stub and with row
+groups. We can modify the order of the row groups with \code{row_group_order()},
+specifying the new ordering in \code{groups}.
 
 \if{html}{\out{<div class="sourceCode r">}}\preformatted{exibble |>
   dplyr::select(char, currency, row, group) |>
diff --git a/man/rows_add.Rd b/man/rows_add.Rd
index 94c4bb49a4..c21b282b37 100644
--- a/man/rows_add.Rd
+++ b/man/rows_add.Rd
@@ -14,31 +14,56 @@ rows_add(
 )
 }
 \arguments{
-\item{.data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{...}{Expressions for the assignment of cell values to the new rows by
-column name in \code{.data}. Name-value pairs, in the form of \verb{<column> = <value vector>} will work, so long as the \verb{<column>} value exists in the table.
-Two-sided formulas with column-resolving expressions (e.g, \verb{<expr> ~ <value vector>}) can also be used, where the left-hand side corresponds to
-selections of columns. Column names should be enclosed in \code{\link[=c]{c()}} and select
-helpers like \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}},
-\code{\link[=one_of]{one_of()}}, and \code{\link[=everything]{everything()}} can be used in the LHS. The length of the
-longest vector in \verb{<value vector>} determines how many new rows will be
-added. Single values in \verb{<value vector>} will be repeated down in cases
-where there are multiple rows to be added.}
-
-\item{.list}{Allows for the use of a list as an input alternative to \code{...}.}
-
-\item{.before, .after}{A single row-resolving expression (i.e.,
-\strong{tidyselect}-style expressions like \code{starts_with()}) or row index can be
-given to either \code{.before} or \code{.after}. This specifies where the new rows
-should be positioned among the existing rows in the input data table.
-Importantly, only a single row must be resolved (otherwise, the function
-will be stopped). If nothing is provided for either argument then any new
-rows will be placed at the bottom of the table.}
-
-\item{.n_empty}{An option to add empty rows in lieu of rows containing data
-that would otherwise be supplied to \code{...} or \code{.list}. If the option is
-taken, provide an integer value here.}
+\item{.data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Cell data assignments}
+
+\verb{<multiple expressions>} --- (or, use \code{.list})
+
+Expressions for the assignment of cell values to the new rows by column
+name in \code{.data}. Name-value pairs, in the form of
+\verb{<column> = <value vector>} will work, so long as the \verb{<column>} value
+exists in the table. Two-sided formulas with column-resolving expressions
+(e.g, \verb{<expr> ~ <value vector>}) can also be used, where the left-hand side
+corresponds to selections of columns. Column names should be enclosed in
+\code{\link[=c]{c()}} and select helpers like \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and \code{\link[=everything]{everything()}} can be used in the LHS. The
+length of the longest vector in \verb{<value vector>} determines how many new
+rows will be added. Single values in \verb{<value vector>} will be repeated down
+in cases where there are multiple rows to be added.}
+
+\item{.list}{\emph{Alternative to \code{...}}
+
+\verb{<list of multiple expressions>} --- (or, use \code{...})
+
+Allows for the use of a list as an input alternative to \code{...}.}
+
+\item{.before, .after}{\emph{Row used as anchor}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A single row-resolving expression or row index an be given to either
+\code{.before} or \code{.after}. The row specifies where the new rows should be
+positioned among the existing rows in the input data table. While select
+helper functions such as \code{\link[=starts_with]{starts_with()}} and \code{\link[=ends_with]{ends_with()}} can be used for
+row targeting, it's recommended that a single row name or index be used.
+This is to ensure that exactly one row is provided to either of these
+arguments (otherwise, the function will be stopped). If nothing is provided
+for either argument then any new rows will be placed at the bottom of the
+table.}
+
+\item{.n_empty}{\emph{Number of empty rows to add}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{NULL} (\code{optional})
+
+An option to add empty rows in lieu of rows containing data that would
+otherwise be supplied to \code{...} or \code{.list}. If the option is taken, provide
+an integer value here.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/sub_large_vals.Rd b/man/sub_large_vals.Rd
index 4f13284595..cdc6f813eb 100644
--- a/man/sub_large_vals.Rd
+++ b/man/sub_large_vals.Rd
@@ -14,34 +14,57 @@ sub_large_vals(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which substitution operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{threshold}{\emph{Threshold value}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1E12}
+
+The threshold value with which values should be considered large enough for
+replacement.}
+
+\item{large_pattern}{\emph{Pattern specification for large values}
+
+\verb{scalar<character>} --- \emph{default:} \code{">={x}"}
+
+The pattern text to be used in place of the suitably large values in the
+rendered table.}
 
-\item{threshold}{The threshold value with which values should be considered
-large enough for replacement.}
+\item{sign}{\emph{Consider positive or negative values?}
 
-\item{large_pattern}{The pattern text to be used in place of the suitably
-large values in the rendered table.}
+\verb{scalar<character>} --- \emph{default:} \code{"+"}
 
-\item{sign}{The sign of the numbers to be considered in the replacement. By
-default, we only consider positive values (\code{"+"}). The other option (\code{"-"})
-can be used to consider only negative values.}
+The sign of the numbers to be considered in the replacement. By default, we
+only consider positive values (\code{"+"}). The other option (\code{"-"}) can be used
+to consider only negative values.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/sub_missing.Rd b/man/sub_missing.Rd
index 8e2755e961..c737a09d16 100644
--- a/man/sub_missing.Rd
+++ b/man/sub_missing.Rd
@@ -12,27 +12,43 @@ sub_missing(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which substitution operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{missing_text}{The text to be used in place of \code{NA} values in the
-rendered table.}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{missing_text}{\emph{Replacement text for \code{NA} values}
+
+\verb{scalar<character>} --- \emph{default:} \code{"---"}
+
+The text to be used in place of \code{NA} values in the rendered table. We can
+optionally use the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} functions to style the text as
+Markdown or to retain HTML elements in the text.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/sub_small_vals.Rd b/man/sub_small_vals.Rd
index d5d737b9b3..167e6a13c9 100644
--- a/man/sub_small_vals.Rd
+++ b/man/sub_small_vals.Rd
@@ -14,34 +14,57 @@ sub_small_vals(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which substitution operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{threshold}{\emph{Threshold value}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{0.01}
+
+The threshold value with which values should be considered small enough for
+replacement.}
+
+\item{small_pattern}{\emph{Pattern specification for small values}
+
+\verb{scalar<character>} --- \emph{default:} \code{if (sign == "+") "<{x}" else md("<*abs*(-{x})")}
+
+The pattern text to be used in place of the suitably small values in the
+rendered table.}
 
-\item{threshold}{The threshold value with which values should be considered
-small enough for replacement.}
+\item{sign}{\emph{Consider positive or negative values?}
 
-\item{small_pattern}{The pattern text to be used in place of the suitably
-small values in the rendered table.}
+\verb{scalar<character>} --- \emph{default:} \code{"+"}
 
-\item{sign}{The sign of the numbers to be considered in the replacement. By
-default, we only consider positive values (\code{"+"}). The other option (\code{"-"})
-can be used to consider only negative values.}
+The sign of the numbers to be considered in the replacement. By default, we
+only consider positive values (\code{"+"}). The other option (\code{"-"}) can be used
+to consider only negative values.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/sub_values.Rd b/man/sub_values.Rd
index fa1f7aaefc..b029ae44b7 100644
--- a/man/sub_values.Rd
+++ b/man/sub_values.Rd
@@ -16,48 +16,76 @@ sub_values(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which substitution operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{values}{The specific value or values that should be replaced with a
-\code{replacement} value. If \code{pattern} is also supplied then \code{values} will be
-ignored.}
-
-\item{pattern}{A regex pattern that can target solely those values in
-\code{character}-based columns. If \code{values} is also supplied, \code{pattern} will
-take precedence.}
-
-\item{fn}{A supplied function that operates on \code{x} (the data in a column) and
-should return a logical vector that matches the length of \code{x} (i.e., number
-of rows in the input table). If either of \code{values} or \code{pattern} is also
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{values}{\emph{Values to match on}
+
+\verb{scalar<character|numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The specific value or values that should be replaced with a \code{replacement}
+value. If \code{pattern} is also supplied then \code{values} will be ignored.}
+
+\item{pattern}{\emph{Regex pattern to match with}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A regex pattern that can target solely those values in \code{character}-based
+columns. If \code{values} is also supplied, \code{pattern} will take precedence.}
+
+\item{fn}{\emph{Function to return logical values}
+
+\verb{<function>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A supplied function that operates on \code{x} (the data in a column) and should
+return a logical vector that matches the length of \code{x} (i.e., number of
+rows in the input table). If either of \code{values} or \code{pattern} is also
 supplied, \code{fn} will take precedence.}
 
-\item{replacement}{The replacement value for any cell values matched by
-either \code{values} or \code{pattern}. Must be a character or numeric vector of
-length 1.}
+\item{replacement}{\emph{Replacement value for matches}
+
+\verb{scalar<character|numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The replacement value for any cell values matched by either \code{values} or
+\code{pattern}. Must be a character or numeric vector of length 1.}
+
+\item{escape}{\emph{Text escaping}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{escape}{An option to escape replacement text according to the final
-output format of the table. For example, if a LaTeX table is to be
-generated then LaTeX escaping would be performed on the replacements during
-rendering. By default this is set to \code{TRUE} but setting to \code{FALSE} would be
-useful in the case where replacement text is crafted for a specific output
-format in mind.}
+An option to escape replacement text according to the final output format
+of the table. For example, if a LaTeX table is to be generated then LaTeX
+escaping would be performed on the replacements during rendering. By
+default this is set to \code{TRUE} but setting to \code{FALSE} would be useful in the
+case where replacement text is crafted for a specific output format in
+mind.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/sub_zero.Rd b/man/sub_zero.Rd
index b0f36f213e..41deb28227 100644
--- a/man/sub_zero.Rd
+++ b/man/sub_zero.Rd
@@ -7,27 +7,43 @@
 sub_zero(data, columns = everything(), rows = everything(), zero_text = "nil")
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which substitution operations are constrained. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
 
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{zero_text}{The text to be used in place of zero values in the rendered
-table.}
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{zero_text}{\emph{Replacement text for zero values}
+
+\verb{scalar<character>} --- \emph{default:} \code{"nil"}
+
+The text to be used in place of zero values in the rendered table. We can
+optionally use the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} functions to style the text as
+Markdown or to retain HTML elements in the text.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/summary_rows.Rd b/man/summary_rows.Rd
index d3010e67df..90d0f536aa 100644
--- a/man/summary_rows.Rd
+++ b/man/summary_rows.Rd
@@ -17,51 +17,89 @@ summary_rows(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{groups}{The groups to consider for generation of group-wise summary
-rows. By default this is set to \code{everything()}, which means that all
-available groups will obtain summary rows. Providing the ID values (in
-quotes) of row groups in \code{c()} will generate summary rows for those
-specified groups.}
-
-\item{columns}{The columns for which the summaries should be calculated. By
-default, this is every column that has data cells (given by
-\code{everything()}).}
-
-\item{fns}{Functions used for aggregations. This can include base functions
-like \code{mean}, \code{min}, \code{max}, \code{median}, \code{sd}, or \code{sum} or any other
-user-defined aggregation function. Multiple functions, each of which would
-generate a different row, are to be supplied within a \code{list()}. We can
-specify the functions by use of function names in quotes (e.g., \code{"sum"}),
-as bare functions (e.g., \code{sum}), or in formula form (e.g.,
-\code{minimum ~ min(.)}) where the LHS could be used to supply the summary row
-label and id values. More information on this can be found in the
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{groups}{\emph{Specification of row group IDs}
+
+\verb{<row-group-targeting expression>} --- \emph{default:} \code{everything()}
+
+The row groups to which targeting operations are constrained. Can either be
+a series of row group ID values provided in \code{\link[=c]{c()}} or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}. By default this is set to \code{\link[=everything]{everything()}}, which means that
+all available groups will obtain summary rows.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns for which the summaries should be calculated. Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
+
+\item{fns}{\emph{Aggregation Expressions}
+
+\verb{<expression|list of expressions>}
+
+Functions used for aggregations. This can include base functions like
+\code{mean}, \code{min}, \code{max}, \code{median}, \code{sd}, or \code{sum} or any other user-defined
+aggregation function. Multiple functions, each of which would generate a
+different row, are to be supplied within a \code{list()}. We can specify the
+functions by use of function names in quotes (e.g., \code{"sum"}), as bare
+functions (e.g., \code{sum}), or in formula form (e.g., \code{minimum ~ min(.)})
+where the LHS could be used to supply the summary row label and ID values.
+More information on this can be found in the
 \emph{Aggregation expressions for \code{fns}} section.}
 
-\item{fmt}{Formatting expressions in formula form. The RHS of \code{~} should
-contain a formatting call (e.g.,
-\verb{~ fmt_number(., decimals = 3, use_seps = FALSE}). Optionally, the LHS
-could contain a group-targeting expression (e.g.,
+\item{fmt}{\emph{Formatting expressions}
+
+\verb{<expression|list of expressions>}
+
+Formatting expressions in formula form. The RHS of \code{~} should contain a
+formatting call (e.g., \verb{~ fmt_number(., decimals = 3, use_seps = FALSE}).
+Optionally, the LHS could contain a group-targeting expression (e.g.,
 \code{"group_a" ~ fmt_number(.)}). More information on this can be found in the
 \emph{Formatting expressions for \code{fmt}} section.}
 
-\item{side}{Should the summary rows be placed at the \code{"bottom"} (the default)
-or the \code{"top"} of the row group?}
+\item{side}{\emph{Side used for placement of summary rows}
+
+\verb{singl-kw:[bottom|top]} --- \emph{default:} \code{"bottom"}
+
+Should the summary rows be placed at the \code{"bottom"} (the default) or the
+\code{"top"} of the row group?}
+
+\item{missing_text}{\emph{Replacement text for \code{NA} values}
+
+\verb{scalar<character>} --- \emph{default:} \code{"---"}
+
+The text to be used in place of \code{NA} values in summary cells with no data
+outputs.}
+
+\item{formatter}{\emph{\link{Deprecated} Formatting function}
+
+\verb{<expression>}
+
+Deprecated, please use \code{fmt} instead. This was previously used as a way to
+input a formatting function name, which could be any of the \verb{fmt_*()}
+functions available in the package (e.g., \code{\link[=fmt_number]{fmt_number()}}, \code{\link[=fmt_percent]{fmt_percent()}},
+etc.), or a custom function using \code{\link[=fmt]{fmt()}}. The options of a formatter can
+be accessed through \code{...}.}
 
-\item{missing_text}{The text to be used in place of \code{NA} values in summary
-cells with no data outputs.}
+\item{...}{\emph{\link{Deprecated} Formatting arguments}
 
-\item{formatter}{Deprecated, please use \code{fmt} instead. This was previously
-used as a way to input a formatting function name, which could be any of
-the \verb{fmt_*()} functions available in the package (e.g., \code{\link[=fmt_number]{fmt_number()}},
-\code{\link[=fmt_percent]{fmt_percent()}}, etc.), or a custom function using \code{\link[=fmt]{fmt()}}. The options of
-a formatter can be accessed through \code{...}.}
+\verb{<Named arguments>}
 
-\item{...}{Deprecated (along with \code{formatter}) but otherwise used for
-argument values for a formatting function supplied in \code{formatter}. For
-example, if using \code{formatter = fmt_number}, options such as \code{decimals = 1},
-\code{use_seps = FALSE}, and the like can be used here.}
+Deprecated (along with \code{formatter}) but otherwise used for argument values
+for a formatting function supplied in \code{formatter}. For example, if using
+\code{formatter = fmt_number}, options such as \code{decimals = 1}, \code{use_seps = FALSE}, and the like can be used here.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/system_fonts.Rd b/man/system_fonts.Rd
index 3d6113fc17..f942594567 100644
--- a/man/system_fonts.Rd
+++ b/man/system_fonts.Rd
@@ -7,8 +7,12 @@
 system_fonts(name)
 }
 \arguments{
-\item{name}{A keyword from the set of \code{"system-ui"}, \code{"transitional"},
-\code{"old-style"}, \code{"humanist"}, \code{"geometric-humanist"},
+\item{name}{\emph{Name of font stack}
+
+\verb{scalar<character>} --- \strong{required}
+
+The name of a font stack. Must be drawn from the set of \code{"system-ui"},
+\code{"transitional"}, \code{"old-style"}, \code{"humanist"}, \code{"geometric-humanist"},
 \code{"classical-humanist"}, \code{"neo-grotesque"}, \code{"monospace-slab-serif"},
 \code{"monospace-code"}, \code{"industrial"}, \code{"rounded-sans"}, \code{"slab-serif"},
 \code{"antique"}, \code{"didone"}, and \code{"handwritten"}.}
diff --git a/man/tab_caption.Rd b/man/tab_caption.Rd
index dfad9c08c7..f7d3f8626f 100644
--- a/man/tab_caption.Rd
+++ b/man/tab_caption.Rd
@@ -7,10 +7,19 @@
 tab_caption(data, caption)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{caption}{The table caption to use for cross-referencing in R Markdown,
-Quarto, or \strong{bookdown}.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{caption}{\emph{Table caption text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The table caption to use for cross-referencing in R Markdown, Quarto, or
+\strong{bookdown}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_footnote.Rd b/man/tab_footnote.Rd
index 8c41a5b3e5..3363f425a9 100644
--- a/man/tab_footnote.Rd
+++ b/man/tab_footnote.Rd
@@ -12,28 +12,45 @@ tab_footnote(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{footnote}{The text to be used in the footnote. We can optionally use
-the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} functions to style the text as Markdown or to
-retain HTML elements in the footnote text.}
-
-\item{locations}{The cell or set of cells to be associated with the footnote.
-Supplying any of the \verb{cells_*()} helper functions is a useful way to target
-the location cells that are associated with the footnote text. These helper
-functions are: \code{\link[=cells_title]{cells_title()}}, \code{\link[=cells_stubhead]{cells_stubhead()}},
-\code{\link[=cells_column_spanners]{cells_column_spanners()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
-\code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_summary]{cells_summary()}}, \code{\link[=cells_grand_summary]{cells_grand_summary()}},
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{footnote}{\emph{Footnote text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text to be used in the footnote. We can optionally use the \code{\link[=md]{md()}} and
+\code{\link[=html]{html()}} functions to style the text as Markdown or to retain HTML elements
+in the footnote text.}
+
+\item{locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The cell or set of cells to be associated with the footnote. Supplying any
+of the \verb{cells_*()} helper functions is a useful way to target the location
+cells that are associated with the footnote text. These helper functions
+are: \code{\link[=cells_title]{cells_title()}}, \code{\link[=cells_stubhead]{cells_stubhead()}}, \code{\link[=cells_column_spanners]{cells_column_spanners()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, \code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_stub]{cells_stub()}},
+\code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_summary]{cells_summary()}}, \code{\link[=cells_grand_summary]{cells_grand_summary()}},
 \code{\link[=cells_stub_summary]{cells_stub_summary()}}, and \code{\link[=cells_stub_grand_summary]{cells_stub_grand_summary()}}. Additionally, we
 can enclose several \verb{cells_*()} calls within a \code{list()} if we wish to link
 the footnote text to different types of locations (e.g., body cells, row
 group labels, the table title, etc.).}
 
-\item{placement}{Where to affix footnote marks to the table content. Two
-options for this are \verb{"left} or \code{"right"}, where the placement is either to
-the absolute left or right of the cell content. By default, however, this
-option is set to \code{"auto"} whereby \strong{gt} will choose a preferred
-left-or-right placement depending on the alignment of the cell content.}
+\item{placement}{\emph{Placement of footnote mark}
+
+\verb{singl-kw:[auto|right|left]} --- \emph{default:} \code{"auto"}
+
+Where to affix footnote marks to the table content. Two options for this
+are \verb{"left} or \code{"right"}, where the placement is either to the absolute
+left or right of the cell content. By default, however, this option is set
+to \code{"auto"} whereby \strong{gt} will choose a preferred left-or-right placement
+depending on the alignment of the cell content.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_header.Rd b/man/tab_header.Rd
index bc24e7b047..d911bf3093 100644
--- a/man/tab_header.Rd
+++ b/man/tab_header.Rd
@@ -7,14 +7,34 @@
 tab_header(data, title, subtitle = NULL, preheader = NULL)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{title, subtitle}{Text to be used in the table title and, optionally, for
-the table subtitle. We can elect to use the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} helper
-functions to style the text as Markdown or to retain HTML elements in the
-text.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{preheader}{Optional preheader content that is rendered above the table.
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{title}{\emph{Header title}
+
+\verb{scalar<character>} --- \strong{required}
+
+Text to be used in the table title. We can elect to use the \code{\link[=md]{md()}} and
+\code{\link[=html]{html()}} helper functions to style the text as Markdown or to retain HTML
+elements in the text.}
+
+\item{subtitle}{\emph{Header subtitle}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Text to be used in the table subtitle. We can elect to use the \code{\link[=md]{md()}} and
+\code{\link[=html]{html()}} helper functions to style the text as Markdown or to retain HTML
+elements in the text.}
+
+\item{preheader}{\emph{RTF preheader text}
+
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+Optional preheader content that is rendered above the table for RTF output.
 Can be supplied as a vector of text.}
 }
 \value{
diff --git a/man/tab_info.Rd b/man/tab_info.Rd
index 588245cad1..5974ad2469 100644
--- a/man/tab_info.Rd
+++ b/man/tab_info.Rd
@@ -7,7 +7,12 @@
 tab_info(data)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_options.Rd b/man/tab_options.Rd
index fd7a1b414d..d9a901054e 100644
--- a/man/tab_options.Rd
+++ b/man/tab_options.Rd
@@ -193,47 +193,67 @@ tab_options(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{table.width}{The width of the table. Can be specified as a
-single-length character with units of pixels or as a percentage. If
-provided as a single-length numeric vector, it is assumed that the value is
-given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper functions can also
-be used to pass in numeric values and obtain values as pixel or percent
-units.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{table.layout}{The value for the \code{table-layout} CSS style in the HTML
-output context. By default, this is \code{"fixed"} but another valid option is
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{table.width}{\emph{Table width}
+
+The table width can be specified as a single-length character with units of
+pixels or as a percentage. If provided as a single-length numeric vector,
+it is assumed that the value is given in units of pixels. The \code{\link[=px]{px()}} and
+\code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
+obtain values as pixel or percent units.}
+
+\item{table.layout}{\emph{The table-layout property}
+
+This is the value for the \code{table-layout} CSS style in the HTML output
+context. By default, this is \code{"fixed"} but another valid option is
 \code{"auto"}.}
 
-\item{table.align}{The horizontal alignment of the table in its container. By
-default, this is \code{"center"}. Other options are \code{"left"} and \code{"right"}. This
-will automatically set \code{table.margin.left} and \code{table.margin.right} to the
-appropriate values.}
-
-\item{table.margin.left, table.margin.right}{The size of the margins on the
-left and right of the table within the container. Can be specified as a
-single-length character with units of pixels or as a percentage. If
-provided as a single-length numeric vector, it is assumed that the value is
-given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper functions can also
-be used to pass in numeric values and obtain values as pixel or percent
-units. Using \code{table.margin.left} or \code{table.margin.right} will overwrite any
-values set by \code{table.align}.}
-
-\item{table.background.color, heading.background.color, column_labels.background.color, row_group.background.color, stub.background.color, summary_row.background.color, grand_summary_row.background.color, footnotes.background.color, source_notes.background.color}{Background colors for the parent element \code{table} and the following child
-elements: \code{heading}, \code{column_labels}, \code{row_group}, \code{stub}, \code{summary_row},
-\code{grand_summary_row}, \code{footnotes}, and \code{source_notes}. A color name or a
-hexadecimal color code should be provided.}
+\item{table.align}{\emph{Horizontal alignment of table}
+
+The \code{table.align} option lets us set the horizontal alignment of the table
+in its container. By default, this is \code{"center"}. Other options are
+\code{"left"} and \code{"right"}. This will automatically set \code{table.margin.left} and
+\code{table.margin.right} to the appropriate values.}
+
+\item{table.margin.left, table.margin.right}{\emph{Left and right table margins}
+
+The size of the margins on the left and right of the table within the
+container can be set with \code{table.margin.left} and \code{table.margin.right}. Can
+be specified as a single-length character with units of pixels or as a
+percentage. If provided as a single-length numeric vector, it is assumed
+that the value is given in units of pixels. The \code{\link[=px]{px()}} and \code{\link[=pct]{pct()}} helper
+functions can also be used to pass in numeric values and obtain values as
+pixel or percent units. Using \code{table.margin.left} or \code{table.margin.right}
+will overwrite any values set by \code{table.align}.}
 
-\item{table.additional_css}{This option can be used to supply an additional
-block of CSS rules to be applied after the automatically generated table
-CSS.}
+\item{table.background.color, heading.background.color, column_labels.background.color, row_group.background.color, stub.background.color, summary_row.background.color, grand_summary_row.background.color, footnotes.background.color, source_notes.background.color}{\emph{Background colors}
 
-\item{table.font.names}{The names of the fonts used for the table. This is
-a vector of several font names. If the first font isn't available, then
-the next font is tried (and so on).}
+These options govern background colors for the parent element \code{table} and
+the following child elements: \code{heading}, \code{column_labels}, \code{row_group},
+\code{stub}, \code{summary_row}, \code{grand_summary_row}, \code{footnotes}, and
+\code{source_notes}. A color name or a hexadecimal color code should be
+provided.}
 
-\item{table.font.size, heading.title.font.size, heading.subtitle.font.size, column_labels.font.size, row_group.font.size, stub.font.size, footnotes.font.size, source_notes.font.size}{The font sizes for the parent text element \code{table} and the following child
+\item{table.additional_css}{\emph{Additional CSS}
+
+The \code{table.additional_css} option can be used to supply an additional block
+of CSS rules to be applied after the automatically generated table CSS.}
+
+\item{table.font.names}{\emph{Default table fonts}
+
+The names of the fonts used for the table can be supplied through
+\code{table.font.names}. This is a vector of several font names. If the first
+font isn't available, then the next font is tried (and so on).}
+
+\item{table.font.size, heading.title.font.size, heading.subtitle.font.size, column_labels.font.size, row_group.font.size, stub.font.size, footnotes.font.size, source_notes.font.size}{\emph{Table font sizes}
+
+The font sizes for the parent text element \code{table} and the following child
 elements: \code{heading.title}, \code{heading.subtitle}, \code{column_labels},
 \code{row_group}, \code{footnotes}, and \code{source_notes}. Can be specified as a
 single-length character vector with units of pixels (e.g., \verb{12px}) or as a
@@ -242,35 +262,49 @@ it is assumed that the value is given in units of pixels. The \code{\link[=px]{p
 \code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
 obtain values as pixel or percentage units.}
 
-\item{table.font.weight, heading.title.font.weight, heading.subtitle.font.weight, column_labels.font.weight, row_group.font.weight, stub.font.weight}{The font weights of the table, \code{heading.title}, \code{heading.subtitle},
+\item{table.font.weight, heading.title.font.weight, heading.subtitle.font.weight, column_labels.font.weight, row_group.font.weight, stub.font.weight}{\emph{Table font weights}
+
+The font weights of the table, \code{heading.title}, \code{heading.subtitle},
 \code{column_labels}, \code{row_group}, and \code{stub} text elements. Can be a text-based
 keyword such as \code{"normal"}, \code{"bold"}, \code{"lighter"}, \code{"bolder"}, or, a
 numeric value between \code{1} and \code{1000}, inclusive. Note that only variable
 fonts may support the numeric mapping of weight.}
 
-\item{table.font.style}{The font style for the table. Can be one of either
+\item{table.font.style}{\emph{Default table font style}
+
+This is the default font style for the table. Can be one of either
 \code{"normal"}, \code{"italic"}, or \code{"oblique"}.}
 
-\item{table.font.color, table.font.color.light}{The text color used throughout the table. There are two variants:
-\code{table.font.color} is for text overlaid on lighter background colors, and
-\code{table.font.color.light} is automatically used when text needs to be
-overlaid on darker background colors. A color name or a hexadecimal color
-code should be provided.}
+\item{table.font.color, table.font.color.light}{\emph{Default dark and light text for the table}
+
+These options define text colors used throughout the table. There are two
+variants: \code{table.font.color} is for text overlaid on lighter background
+colors, and \code{table.font.color.light} is automatically used when text needs
+to be overlaid on darker background colors. A color name or a hexadecimal
+color code should be provided.}
 
-\item{table.border.top.style, table.border.top.width, table.border.top.color, table.border.right.style, table.border.right.width, table.border.right.color, table.border.bottom.style, table.border.bottom.width, table.border.bottom.color, table.border.left.style, table.border.left.width, table.border.left.color}{The style, width, and color properties of the table's absolute top and
+\item{table.border.top.style, table.border.top.width, table.border.top.color, table.border.right.style, table.border.right.width, table.border.right.color, table.border.bottom.style, table.border.bottom.width, table.border.bottom.color, table.border.left.style, table.border.left.width, table.border.left.color}{\emph{Top border properties}
+
+The style, width, and color properties of the table's absolute top and
 absolute bottom borders.}
 
-\item{heading.align}{Controls the horizontal alignment of the heading title
-and subtitle. We can either use \code{"center"}, \code{"left"}, or \code{"right"}.}
+\item{heading.align}{\emph{Horizontal alignment in the table header}
+
+Controls the horizontal alignment of the heading title and subtitle. We can
+either use \code{"center"}, \code{"left"}, or \code{"right"}.}
 
-\item{heading.padding, column_labels.padding, data_row.padding, row_group.padding, summary_row.padding, grand_summary_row.padding, footnotes.padding, source_notes.padding}{The amount of vertical padding to incorporate in the \code{heading} (title and
+\item{heading.padding, column_labels.padding, data_row.padding, row_group.padding, summary_row.padding, grand_summary_row.padding, footnotes.padding, source_notes.padding}{\emph{Vertical padding throughout the table}
+
+The amount of vertical padding to incorporate in the \code{heading} (title and
 subtitle), the \code{column_labels} (this includes the column spanners), the row
 group labels (\code{row_group.padding}), in the body/stub rows
 (\code{data_row.padding}), in summary rows (\code{summary_row.padding} or
 \code{grand_summary_row.padding}), or in the footnotes and source notes
 (\code{footnotes.padding} and \code{source_notes.padding}).}
 
-\item{heading.padding.horizontal, column_labels.padding.horizontal, data_row.padding.horizontal, row_group.padding.horizontal, summary_row.padding.horizontal, grand_summary_row.padding.horizontal, footnotes.padding.horizontal, source_notes.padding.horizontal}{The amount of horizontal padding to incorporate in the \code{heading} (title and
+\item{heading.padding.horizontal, column_labels.padding.horizontal, data_row.padding.horizontal, row_group.padding.horizontal, summary_row.padding.horizontal, grand_summary_row.padding.horizontal, footnotes.padding.horizontal, source_notes.padding.horizontal}{\emph{Horizontal padding throughout the table}
+
+The amount of horizontal padding to incorporate in the \code{heading} (title and
 subtitle), the \code{column_labels} (this includes the column spanners), the row
 group labels (\code{row_group.padding.horizontal}), in the body/stub rows
 (\code{data_row.padding}), in summary rows (\code{summary_row.padding.horizontal} or
@@ -278,127 +312,180 @@ group labels (\code{row_group.padding.horizontal}), in the body/stub rows
 notes (\code{footnotes.padding.horizontal} and
 \code{source_notes.padding.horizontal}).}
 
-\item{heading.border.bottom.style, heading.border.bottom.width, heading.border.bottom.color}{The style, width, and color properties of the header's bottom border. This
+\item{heading.border.bottom.style, heading.border.bottom.width, heading.border.bottom.color}{\emph{Properties of the header's bottom border}
+
+The style, width, and color properties of the header's bottom border. This
 border shares space with that of the \code{column_labels} location. If the
 \code{width} of this border is larger, then it will be the visible border.}
 
-\item{heading.border.lr.style, heading.border.lr.width, heading.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{heading.border.lr.style, heading.border.lr.width, heading.border.lr.color}{\emph{Properties of the header's left and right borders}
+
+The style, width, and color properties for the left and right borders of
 the \code{heading} location.}
 
-\item{column_labels.text_transform, row_group.text_transform, stub.text_transform, summary_row.text_transform, grand_summary_row.text_transform}{Options to apply text transformations to the \code{column_labels}, \code{row_group},
+\item{column_labels.text_transform, row_group.text_transform, stub.text_transform, summary_row.text_transform, grand_summary_row.text_transform}{\emph{Text transforms throughout the table}
+
+Options to apply text transformations to the \code{column_labels}, \code{row_group},
 \code{stub}, \code{summary_row}, and \code{grand_summary_row} text elements. Either of the
 \code{"uppercase"}, \code{"lowercase"}, or \code{"capitalize"} keywords can be used.}
 
-\item{column_labels.vlines.style, column_labels.vlines.width, column_labels.vlines.color}{The style, width, and color properties for all vertical lines ('vlines')
+\item{column_labels.vlines.style, column_labels.vlines.width, column_labels.vlines.color}{\emph{Properties of all vertical lines by the column labels}
+
+The style, width, and color properties for all vertical lines ('vlines')
 of the the \code{column_labels}.}
 
-\item{column_labels.border.top.style, column_labels.border.top.width, column_labels.border.top.color}{The style, width, and color properties for the top border of the
+\item{column_labels.border.top.style, column_labels.border.top.width, column_labels.border.top.color}{\emph{Properties of the border above the column labels}
+
+The style, width, and color properties for the top border of the
 \code{column_labels} location. This border shares space with that of the
 \code{heading} location. If the \code{width} of this border is larger, then it will
 be the visible border.}
 
-\item{column_labels.border.bottom.style, column_labels.border.bottom.width, column_labels.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{column_labels.border.bottom.style, column_labels.border.bottom.width, column_labels.border.bottom.color}{\emph{Properties of the border below the column labels}
+
+The style, width, and color properties for the bottom border of the
 \code{column_labels} location.}
 
-\item{column_labels.border.lr.style, column_labels.border.lr.width, column_labels.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{column_labels.border.lr.style, column_labels.border.lr.width, column_labels.border.lr.color}{\emph{Properties of the left and right borders next to the column labels}
+
+The style, width, and color properties for the left and right borders of
 the \code{column_labels} location.}
 
-\item{column_labels.hidden}{An option to hide the column labels. If providing
-\code{TRUE} then the entire \code{column_labels} location won't be seen and the table
-header (if present) will collapse downward.}
+\item{column_labels.hidden}{\emph{Hiding all column labels}
+
+An option to hide the column labels. If providing \code{TRUE} then the entire
+\code{column_labels} location won't be seen and the table header (if present)
+will collapse downward.}
+
+\item{row_group.border.top.style, row_group.border.top.width, row_group.border.top.color, row_group.border.bottom.style, row_group.border.bottom.width, row_group.border.bottom.color, row_group.border.left.style, row_group.border.left.width, row_group.border.left.color, row_group.border.right.style, row_group.border.right.width, row_group.border.right.color}{\emph{Border properties associated with the \code{row_group} location}
 
-\item{row_group.border.top.style, row_group.border.top.width, row_group.border.top.color, row_group.border.bottom.style, row_group.border.bottom.width, row_group.border.bottom.color, row_group.border.left.style, row_group.border.left.width, row_group.border.left.color, row_group.border.right.style, row_group.border.right.width, row_group.border.right.color}{The style, width, and color properties for all top, bottom, left, and right
+The style, width, and color properties for all top, bottom, left, and right
 borders of the \code{row_group} location.}
 
-\item{row_group.default_label}{An option to set a default row group label for
-any rows not formally placed in a row group named by \code{group} in any call of
-\code{tab_row_group()}. If this is set as \code{NA_character} and there are rows that
-haven't been placed into a row group (where one or more row groups already
-exist), those rows will be automatically placed into a row group without a
-label.}
+\item{row_group.default_label}{\emph{The default row group label}
 
-\item{row_group.as_column}{How should row groups be structured? By default,
-they are separate rows that lie above the each of the groups. Setting this
-to \code{TRUE} will structure row group labels are columns to the far left of
-the table.}
+An option to set a default row group label for any rows not formally placed
+in a row group named by \code{group} in any call of \code{\link[=tab_row_group]{tab_row_group()}}. If this
+is set as \code{NA_character_} and there are rows that haven't been placed into a
+row group (where one or more row groups already exist), those rows will be
+automatically placed into a row group without a label.}
 
-\item{table_body.hlines.style, table_body.hlines.width, table_body.hlines.color, table_body.vlines.style, table_body.vlines.width, table_body.vlines.color}{The style, width, and color properties for all horizontal lines ('hlines')
+\item{row_group.as_column}{\emph{Structure row groups with a column}
+
+How should row groups be structured? By default, they are separate rows
+that lie above the each of the groups. Setting this to \code{TRUE} will
+structure row group labels as a separate column in the table stub.}
+
+\item{table_body.hlines.style, table_body.hlines.width, table_body.hlines.color, table_body.vlines.style, table_body.vlines.width, table_body.vlines.color}{\emph{Properties of all horizontal and vertical lines in the table body}
+
+The style, width, and color properties for all horizontal lines ('hlines')
 and vertical lines ('vlines') in the \code{table_body}.}
 
-\item{table_body.border.top.style, table_body.border.top.width, table_body.border.top.color, table_body.border.bottom.style, table_body.border.bottom.width, table_body.border.bottom.color}{The style, width, and color properties for all top and bottom borders of
+\item{table_body.border.top.style, table_body.border.top.width, table_body.border.top.color, table_body.border.bottom.style, table_body.border.bottom.width, table_body.border.bottom.color}{\emph{Properties of top and bottom borders in the table body}
+
+The style, width, and color properties for all top and bottom borders of
 the \code{table_body} location.}
 
-\item{stub.border.style, stub.border.width, stub.border.color}{The style, width, and color properties for the vertical border of the table
+\item{stub.border.style, stub.border.width, stub.border.color}{\emph{Properties of the vertical border of the table stub}
+
+The style, width, and color properties for the vertical border of the table
 stub.}
 
-\item{stub.indent_length}{The width of each indentation level. By default
-this is \code{"5px"}.}
+\item{stub.indent_length}{\emph{Width of each indentation}
 
-\item{stub_row_group.font.size, stub_row_group.font.weight, stub_row_group.text_transform, stub_row_group.border.style, stub_row_group.border.width, stub_row_group.border.color}{Options for the row group column in the stub (made possible when using
-\code{row_group.as_column = TRUE}). The defaults for these options mirror that
-of the \verb{stub.*} variants (except for \code{stub_row_group.border.width}, which
-is \code{"1px"} instead of \code{"2px"}).}
+The width of each indentation level for row labels in the stub. The
+indentation can be set by using \code{\link[=tab_stub_indent]{tab_stub_indent()}}. By default this is
+\code{"5px"}.}
 
-\item{summary_row.border.style, summary_row.border.width, summary_row.border.color}{The style, width, and color properties for all horizontal borders of the
+\item{stub_row_group.font.size, stub_row_group.font.weight, stub_row_group.text_transform, stub_row_group.border.style, stub_row_group.border.width, stub_row_group.border.color}{\emph{Properties of the row group column in the table stub}
+
+Options for the row group column in the table stub (made possible when
+using \code{row_group.as_column = TRUE}). The defaults for these options mirror
+that of the \verb{stub.*} variants (except for \code{stub_row_group.border.width},
+which is \code{"1px"} instead of \code{"2px"}).}
+
+\item{summary_row.border.style, summary_row.border.width, summary_row.border.color}{\emph{Properties of horizontal borders belonging to summary rows}
+
+The style, width, and color properties for all horizontal borders of the
 \code{summary_row} location.}
 
-\item{grand_summary_row.border.style, grand_summary_row.border.width, grand_summary_row.border.color}{The style, width, and color properties for the top borders of the
+\item{grand_summary_row.border.style, grand_summary_row.border.width, grand_summary_row.border.color}{\emph{Properties of horizontal borders belonging to grand summary rows}
+
+The style, width, and color properties for the top borders of the
 \code{grand_summary_row} location.}
 
-\item{footnotes.border.bottom.style, footnotes.border.bottom.width, footnotes.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{footnotes.border.bottom.style, footnotes.border.bottom.width, footnotes.border.bottom.color}{\emph{Properties of the bottom border belonging to the footnotes}
+
+The style, width, and color properties for the bottom border of the
 \code{footnotes} location.}
 
-\item{footnotes.border.lr.style, footnotes.border.lr.width, footnotes.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{footnotes.border.lr.style, footnotes.border.lr.width, footnotes.border.lr.color}{\emph{Properties of left and right borders belonging to the footnotes}
+
+The style, width, and color properties for the left and right borders of
 the \code{footnotes} location.}
 
-\item{footnotes.marks}{The set of sequential marks used to reference and
-identify each of the footnotes (same input as the \code{\link[=opt_footnote_marks]{opt_footnote_marks()}}
-function). We can supply a vector that represents the series of footnote
-marks. This vector is recycled when its usage goes beyond the length of the
-set. At each cycle, the marks are simply combined (e.g., \code{*} -> \verb{**} ->
-\verb{***}). The option exists for providing keywords for certain types of
-footnote marks. The keyword \code{"numbers"} (the default, indicating that we
-want to use numeric marks). We can use lowercase \code{"letters"} or uppercase
-\code{"LETTERS"}. There is the option for using a traditional symbol set where
-\code{"standard"} provides four symbols, and, \code{"extended"} adds two more
-symbols, making six.}
-
-\item{footnotes.spec_ref, footnotes.spec_ftr}{Optional specifications for
-formatting of footnote references (\code{footnotes.spec_ref}) and their
-associated marks the footer section (\code{footnotes.spec_ftr}) (same input as
-the \code{\link[=opt_footnote_spec]{opt_footnote_spec()}} function). This is a string containing
-specification control characters. The default is the spec string \code{"^i"},
-which is superscript text set in italics. Other control characters that can
-be used are: (1) \code{"b"} for bold text, and (2) \code{"("} / \code{")"} for the
-enclosure of footnote marks in parentheses.}
-
-\item{footnotes.multiline, source_notes.multiline}{An option to either put
-footnotes and source notes in separate lines (the default, or \code{TRUE}) or
-render them as a continuous line of text with \code{footnotes.sep} providing the
-separator (by default \code{" "}) between notes.}
-
-\item{footnotes.sep, source_notes.sep}{The separating characters between
-adjacent footnotes and source notes in their respective footer sections
-when rendered as a continuous line of text (when
-\code{footnotes.multiline == FALSE}). The default value is a single space
+\item{footnotes.marks}{\emph{Sequence of footnote marks}
+
+The set of sequential marks used to reference and identify each of the
+footnotes (same input as the \code{\link[=opt_footnote_marks]{opt_footnote_marks()}} function). We can
+supply a vector that represents the series of footnote marks. This vector
+is recycled when its usage goes beyond the length of the set. At each
+cycle, the marks are simply combined (e.g., \code{*} -> \verb{**} -> \verb{***}). The
+option exists for providing keywords for certain types of footnote marks.
+The keyword \code{"numbers"} (the default, indicating that we want to use
+numeric marks). We can use lowercase \code{"letters"} or uppercase \code{"LETTERS"}.
+There is the option for using a traditional symbol set where \code{"standard"}
+provides four symbols, and, \code{"extended"} adds two more symbols, making six.}
+
+\item{footnotes.spec_ref, footnotes.spec_ftr}{\emph{Specifications for formatting of footnote marks}
+
+Optional specifications for formatting of footnote references
+(\code{footnotes.spec_ref}) and their associated marks the footer section
+(\code{footnotes.spec_ftr}) (same input as the \code{\link[=opt_footnote_spec]{opt_footnote_spec()}} function).
+This is a string containing specification control characters. The default
+is the spec string \code{"^i"}, which is superscript text set in italics. Other
+control characters that can be used are: (1) \code{"b"} for bold text, and (2)
+\code{"("} / \code{")"} for the enclosure of footnote marks in parentheses.}
+
+\item{footnotes.multiline, source_notes.multiline}{\emph{Typesetting of multiple footnotes and source notes}
+
+An option to either put footnotes and source notes in separate lines (the
+default, or \code{TRUE}) or render them as a continuous line of text with
+\code{footnotes.sep} providing the separator (by default \code{" "}) between notes.}
+
+\item{footnotes.sep, source_notes.sep}{\emph{Separator characters between adjacent footnotes and source notes}
+
+The separating characters between adjacent footnotes and source notes in
+their respective footer sections when rendered as a continuous line of text
+(when \code{footnotes.multiline == FALSE}). The default value is a single space
 character (\code{" "}).}
 
-\item{source_notes.border.bottom.style, source_notes.border.bottom.width, source_notes.border.bottom.color}{The style, width, and color properties for the bottom border of the
+\item{source_notes.border.bottom.style, source_notes.border.bottom.width, source_notes.border.bottom.color}{\emph{Properties of the bottom border belonging to the source notes}
+
+The style, width, and color properties for the bottom border of the
 \code{source_notes} location.}
 
-\item{source_notes.border.lr.style, source_notes.border.lr.width, source_notes.border.lr.color}{The style, width, and color properties for the left and right borders of
+\item{source_notes.border.lr.style, source_notes.border.lr.width, source_notes.border.lr.color}{\emph{Properties of left and right borders belonging to the source notes}
+
+The style, width, and color properties for the left and right borders of
 the \code{source_notes} location.}
 
-\item{row.striping.background_color}{The background color for striped table
-body rows. A color name or a hexadecimal color code should be provided.}
+\item{row.striping.background_color}{\emph{Background color for row stripes}
 
-\item{row.striping.include_stub}{An option for whether to include the stub
-when striping rows.}
+The background color for striped table body rows. A color name or a
+hexadecimal color code should be provided.}
 
-\item{row.striping.include_table_body}{An option for whether to include the
-table body when striping rows.}
+\item{row.striping.include_stub}{\emph{Inclusion of the table stub for row stripes}
 
-\item{container.width, container.height, container.padding.x, container.padding.y}{The width and height of the table's container, and, the vertical and
+An option for whether to include the stub when striping rows.}
+
+\item{row.striping.include_table_body}{\emph{Inclusion of the table body for row stripes}
+
+An option for whether to include the table body when striping rows.}
+
+\item{container.width, container.height, container.padding.x, container.padding.y}{\emph{Table container dimensions and padding}
+
+The width and height of the table's container, and, the vertical and
 horizontal padding of the table's container. The container width and height
 can be specified with units of pixels or as a percentage. The padding is to
 be specified as a length with units of pixels. If provided as a numeric
@@ -406,54 +493,72 @@ value, it is assumed that the value is given in units of pixels. The \code{\link
 and \code{\link[=pct]{pct()}} helper functions can also be used to pass in numeric values and
 obtain values as pixel or percent units.}
 
-\item{container.overflow.x, container.overflow.y}{Options to enable scrolling
-in the horizontal and vertical directions when the table content overflows
-the container dimensions. Using \code{TRUE} (the default for both) means that
-horizontal or vertical scrolling is enabled to view the entire table in
-those directions. With \code{FALSE}, the table may be clipped if the table width
-or height exceeds the \code{container.width} or \code{container.height}.}
-
-\item{ihtml.active}{The option for displaying an interactive version of an
-HTML table (rather than an otherwise 'static' table). This enables the use
-of controls for pagination, global search, filtering, and sorting. The
-individual features are controlled by the other \verb{table.*} options. By
-default, the pagination (\code{ihtml.use_pagination}) and sorting
-(\code{ihtml.use_sorting}) features are enabled. The \code{ihtml.active} option,
-however, is \code{FALSE} by default.}
-
-\item{ihtml.use_pagination, ihtml.use_pagination_info}{For interactive HTML
-output, the option for using pagination controls (below the table body) can
-be controlled with \code{ihtml.use_pagination}. By default, this is \code{TRUE} and
-it will allow the use to page through table content. The informational
-display text regarding the current page can be set with
-\code{ihtml.use_pagination_info} (which is \code{TRUE} by default).}
-
-\item{ihtml.use_sorting}{For interactive HTML output, the option to provide
-controls for sorting column values. By default, this is \code{TRUE}.}
-
-\item{ihtml.use_search}{For interactive HTML output, an option that places a
-search field for globally filtering rows to the requested content. By
-default, this is \code{FALSE}.}
+\item{container.overflow.x, container.overflow.y}{\emph{Table container overflow}
+
+Options to enable scrolling in the horizontal and vertical directions when
+the table content overflows the container dimensions. Using \code{TRUE} (the
+default for both) means that horizontal or vertical scrolling is enabled to
+view the entire table in those directions. With \code{FALSE}, the table may be
+clipped if the table width or height exceeds the \code{container.width} or
+\code{container.height}.}
+
+\item{ihtml.active}{\emph{Display interactive HTML table}
+
+The option for displaying an interactive version of an HTML table (rather
+than an otherwise 'static' table). This enables the use of controls for
+pagination, global search, filtering, and sorting. The individual features
+are controlled by the other \verb{table.*} options. By default, the pagination
+(\code{ihtml.use_pagination}) and sorting (\code{ihtml.use_sorting}) features are
+enabled. The \code{ihtml.active} option, however, is \code{FALSE} by default.}
+
+\item{ihtml.use_pagination, ihtml.use_pagination_info}{\emph{Use pagination}
+
+For interactive HTML output, the option for using pagination controls
+(below the table body) can be controlled with \code{ihtml.use_pagination}. By
+default, this is \code{TRUE} and it will allow the use to page through table
+content. The informational display text regarding the current page can be
+set with \code{ihtml.use_pagination_info} (which is \code{TRUE} by default).}
 
-\item{ihtml.use_filters}{For interactive HTML output, this places search
-fields below each column header and allows for filtering by column. By
+\item{ihtml.use_sorting}{\emph{Provide column sorting controls}
+
+For interactive HTML output, the option to provide controls for sorting
+column values. By default, this is \code{TRUE}.}
+
+\item{ihtml.use_search}{\emph{Provide a global search field}
+
+For interactive HTML output, an option that places a search field for
+globally filtering rows to the requested content. By default, this is
+\code{FALSE}.}
+
+\item{ihtml.use_filters}{\emph{Display filtering fields}
+
+For interactive HTML output, this places search fields below each column
+header and allows for filtering by column. By default, this is \code{FALSE}.}
+
+\item{ihtml.use_resizers}{\emph{Allow column resizing}
+
+For interactive HTML output, this allows for interactive resizing of
+columns. By default, this is \code{FALSE}.}
+
+\item{ihtml.use_highlight}{\emph{Enable row highlighting on hover}
+
+For interactive HTML output, this highlights individual rows upon hover. By
 default, this is \code{FALSE}.}
 
-\item{ihtml.use_resizers}{For interactive HTML output, this allows for
-interactive resizing of columns. By default, this is \code{FALSE}.}
+\item{ihtml.use_compact_mode}{\emph{Use compact mode}
+
+For interactive HTML output, an option to reduce vertical padding and thus
+make the table consume less vertical space. By default, this is \code{FALSE}.}
 
-\item{ihtml.use_highlight}{For interactive HTML output, this highlights
-individual rows upon hover. By default, this is \code{FALSE}.}
+\item{ihtml.use_text_wrapping}{\emph{Use text wrapping}
 
-\item{ihtml.use_compact_mode}{For interactive HTML output, an option to
-reduce vertical padding and thus make the table consume less vertical
-space. By default, this is \code{FALSE}.}
+For interactive HTML output, an option to control text wrapping. By default
+(\code{TRUE}), text will be wrapped to multiple lines; if \code{FALSE}, text will be
+truncated to a single line.}
 
-\item{ihtml.use_text_wrapping}{For interactive HTML output, an option to
-control text wrapping. By default (\code{TRUE}), text will be wrapped to
-multiple lines; if \code{FALSE}, text will be truncated to a single line.}
+\item{ihtml.use_page_size_select, ihtml.page_size_default, ihtml.page_size_values}{\emph{Change page size properties}
 
-\item{ihtml.use_page_size_select, ihtml.page_size_default, ihtml.page_size_values}{For interactive HTML output, \code{ihtml.use_page_size_select} provides the
+For interactive HTML output, \code{ihtml.use_page_size_select} provides the
 option to display a dropdown menu for the number of rows to show per page
 of data. By default, this is the vector \code{c(10, 25, 50, 100)} which
 corresponds to options for \code{10}, \code{25}, \code{50}, and \code{100} rows of data per
@@ -462,47 +567,63 @@ page. To modify these page-size options, provide a numeric vector to
 be modified with \code{ihtml.page_size_default} and this works whether or not
 \code{ihtml.use_page_size_select} is set to \code{TRUE}.}
 
-\item{ihtml.pagination_type}{For interactive HTML output and when using
-pagination, one of three options for presentation pagination controls. The
-default is \code{"numbers"}, where a series of page-number buttons is presented
-along with 'previous' and 'next' buttons. The \code{"jump"} option provides an
-input field with a stepper for the page number. With \code{"simple"}, only the
-'previous' and 'next' buttons are displayed.}
+\item{ihtml.pagination_type}{\emph{Change pagination mode}
 
-\item{page.orientation}{For RTF output, this provides an two options for page
+For interactive HTML output and when using pagination, one of three options
+for presentation pagination controls. The default is \code{"numbers"}, where a
+series of page-number buttons is presented along with 'previous' and 'next'
+buttons. The \code{"jump"} option provides an input field with a stepper for the
+page number. With \code{"simple"}, only the 'previous' and 'next' buttons are
+displayed.}
+
+\item{page.orientation}{\emph{Set RTF page orientation}
+
+For RTF output, this provides an two options for page
 orientation: \code{"portrait"} (the default) and \code{"landscape"}.}
 
-\item{page.numbering}{Within RTF output, should page numbering be displayed?
-By default, this is set to \code{FALSE} but if \code{TRUE} then page numbering text
-will be added to the document header.}
+\item{page.numbering}{\emph{Enable RTF page numbering}
 
-\item{page.header.use_tbl_headings}{If \code{TRUE} then RTF output tables will
-migrate all table headings (including the table title and all column
-labels) to the page header. This page header content will repeat across
-pages. By default, this is \code{FALSE}.}
+Within RTF output, should page numbering be displayed? By default, this is
+set to \code{FALSE} but if \code{TRUE} then page numbering text will be added to the
+document header.}
 
-\item{page.footer.use_tbl_notes}{If \code{TRUE} then RTF output tables will
-migrate all table footer content (this includes footnotes and source notes)
-to the page footer. This page footer content will repeat across pages. By
-default, this is \code{FALSE}.}
+\item{page.header.use_tbl_headings}{\emph{Place table headings in RTF page header}
+
+If \code{TRUE} then RTF output tables will migrate all table headings (including
+the table title and all column labels) to the page header. This page header
+content will repeat across pages. By default, this is \code{FALSE}.}
+
+\item{page.footer.use_tbl_notes}{\emph{Place table footer in RTF page footer}
 
-\item{page.width, page.height}{The page width and height in the standard
-portrait orientation. This is for RTF table output and the default
-values (in inches) are \verb{8.5in} and \verb{11.0in}.}
+If \code{TRUE} then RTF output tables will migrate all table footer content
+(this includes footnotes and source notes) to the page footer. This page
+footer content will repeat across pages. By default, this is \code{FALSE}.}
 
-\item{page.margin.left, page.margin.right, page.margin.top, page.margin.bottom}{For RTF table output, these options correspond to the left, right, top, and
+\item{page.width, page.height}{\emph{Set RTF page dimensions}
+
+The page width and height in the standard portrait orientation. This is for
+RTF table output and the default values (in inches) are \verb{8.5in} and
+\verb{11.0in}.}
+
+\item{page.margin.left, page.margin.right, page.margin.top, page.margin.bottom}{\emph{Set RTF page margins}
+
+For RTF table output, these options correspond to the left, right, top, and
 bottom page margins. The default values for each of these is \verb{1.0in}.}
 
-\item{page.header.height, page.footer.height}{The heights of the page header
-and footer for RTF table outputs. Default values for both are \verb{0.5in}.}
+\item{page.header.height, page.footer.height}{\emph{Set RTF page header and footer distances}
+
+The heights of the page header and footer for RTF table outputs. Default
+values for both are \verb{0.5in}.}
+
+\item{quarto.use_bootstrap, quarto.disable_processing}{\emph{Modify Quarto properties}
 
-\item{quarto.use_bootstrap, quarto.disable_processing}{When rendering a \strong{gt}
-table with Quarto, the table can undergo transformations to support
-advanced Quarto features. Setting \code{quarto.use_bootstrap} to \code{TRUE} (\code{FALSE}
-by default) will allow Quarto to add Bootstrap classes to the table,
-allowing those styles to permeate the table. Quarto performs other
-alterations as well but they can all be deactivated with
-\code{quarto.disable_processing = TRUE} (this option is \code{FALSE} by default).}
+When rendering a \strong{gt} table with Quarto, the table can undergo
+transformations to support advanced Quarto features. Setting
+\code{quarto.use_bootstrap} to \code{TRUE} (\code{FALSE} by default) will allow Quarto to
+add Bootstrap classes to the table, allowing those styles to permeate the
+table. Quarto performs other alterations as well but they can all be
+deactivated with \code{quarto.disable_processing = TRUE} (this option is \code{FALSE}
+by default).}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_row_group.Rd b/man/tab_row_group.Rd
index 1f8e58f536..9df45ac9d9 100644
--- a/man/tab_row_group.Rd
+++ b/man/tab_row_group.Rd
@@ -7,17 +7,38 @@
 tab_row_group(data, label, rows, id = label, others_label = NULL, group = NULL)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{label}{The text to use for the row group label.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{rows}{The rows to be made components of the row group. Can either be a
-vector of row captions provided in \code{c()}, a vector of row indices, or a
-helper function focused on selections. The select helper functions are:
-\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and
-\code{\link[=everything]{everything()}}.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{id}{The ID for the row group. When accessing a row group through
+\item{label}{\emph{Row group label text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text to use for the row group label. We can optionally use the \code{\link[=md]{md()}}
+and \code{\link[=html]{html()}} functions to style the text as Markdown or to retain HTML
+elements in the text.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \strong{required}
+
+The rows to be made components of the row group. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{id}{\emph{Row group ID}
+
+\verb{scalar<character>} --- \emph{default:} \code{label}
+
+The ID for the row group. When accessing a row group through
 \code{\link[=cells_row_groups]{cells_row_groups()}} (when using \code{\link[=tab_style]{tab_style()}} or \code{\link[=tab_footnote]{tab_footnote()}}) the
 \code{id} value is used as the reference (and not the \code{label}). If an \code{id} is
 not explicitly provided here, it will be taken from the \code{label} value. It
@@ -27,10 +48,18 @@ markup, is lengthy, or both). Finally, when providing an \code{id} value you
 must ensure that it is unique across all ID values set for row groups (the
 function will stop if \code{id} isn't unique).}
 
-\item{others_label}{This argument is deprecated. Instead use
+\item{others_label}{\emph{\link{Deprecated} Label for default row group}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+This argument is deprecated. Instead use
 \verb{tab_options(row_group.default_label = <label>)}.}
 
-\item{group}{This argument is deprecated. Instead use \code{label}.}
+\item{group}{\emph{\link{Deprecated} The group label}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+This argument is deprecated. Instead use \code{label}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_source_note.Rd b/man/tab_source_note.Rd
index edcbee0ff2..e8c9de8169 100644
--- a/man/tab_source_note.Rd
+++ b/man/tab_source_note.Rd
@@ -7,11 +7,20 @@
 tab_source_note(data, source_note)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{source_note}{Text to be used in the source note. We can optionally use
-the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} functions to style the text as Markdown or to
-retain HTML elements in the text.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{source_note}{\emph{Source note text}
+
+\verb{scalar<character>} --- \strong{required}
+
+Text to be used in the source note. We can optionally use the \code{\link[=md]{md()}} and
+\code{\link[=html]{html()}} functions to style the text as Markdown or to retain HTML elements
+in the text.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_spanner.Rd b/man/tab_spanner.Rd
index 8bfcc51482..f242e96e4c 100644
--- a/man/tab_spanner.Rd
+++ b/man/tab_spanner.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/tab_create_modify.R
 \name{tab_spanner}
 \alias{tab_spanner}
-\title{Add a spanner column label}
+\title{Add a spanner label}
 \usage{
 tab_spanner(
   data,
@@ -16,43 +16,78 @@ tab_spanner(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{label}{The text to use for the spanner column label.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{columns}{The columns to serve as components of the spanner. Can either
-be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
-or a helper function focused on selections. The select helper functions
-are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{label}{\emph{Spanner label text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text to use for the spanner label. We can optionally use the \code{\link[=md]{md()}} and
+\code{\link[=html]{html()}} functions to style the text as Markdown or to retain HTML elements
+in the text.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The columns to serve as components of the spanner. Can either be a series
+of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a select
+helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
 \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. This argument works in tandem with the
-\code{spanner} argument.}
-
-\item{spanners}{The spanners that should be spanned over, should they already
-be defined. One or more spanner ID values (in quotes) can be supplied here.
-This argument works in tandem with the \code{columns} argument.}
-
-\item{level}{An explicit level to which the spanner should be placed. If not
-provided, \strong{gt} will choose the level based on the inputs provided within
-\code{columns} and \code{spanners}, placing the spanner label where it will fit. The
-first spanner level (right above the column labels) is \code{1}.}
-
-\item{id}{The ID for the spanner column label. When accessing a spanner
-through the \code{spanners} argument of \code{tab_spanner()} or
-\code{\link[=cells_column_spanners]{cells_column_spanners()}} (when using \code{\link[=tab_style]{tab_style()}} or \code{\link[=tab_footnote]{tab_footnote()}})
-the \code{id} value is used as the reference (and not the \code{label}). If an \code{id}
-is not explicitly provided here, it will be taken from the \code{label} value.
-It is advisable to set an explicit \code{id} value if you plan to access this
-cell in a later function call and the label text is complicated (e.g.,
-contains markup, is lengthy, or both). Finally, when providing an \code{id}
-value you must ensure that it is unique across all ID values set for column
-spanner labels (the function will stop if \code{id} isn't unique).}
-
-\item{gather}{An option to move the specified \code{columns} such that they are
-unified under the spanner column label. Ordering of the moved-into-place
-columns will be preserved in all cases. By default, this is set to \code{TRUE}.}
-
-\item{replace}{Should new spanners be allowed to partially or fully replace
-existing spanners? (This is a possibility if setting spanners at an already
+\code{spanners} argument.}
+
+\item{spanners}{\emph{Spanners to target}
+
+\verb{vector<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The spanners that should be spanned over, should they already be defined.
+One or more spanner ID values (in quotes) can be supplied here. This
+argument works in tandem with the \code{columns} argument.}
+
+\item{level}{\emph{Spanner level for insertion}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An explicit level to which the spanner should be placed. If not provided,
+\strong{gt} will choose the level based on the inputs provided within \code{columns}
+and \code{spanners}, placing the spanner label where it will fit. The first
+spanner level (right above the column labels) is \code{1}.}
+
+\item{id}{\emph{Spanner ID}
+
+\verb{scalar<character>} --- \emph{default:} \code{label}
+
+The ID for the spanner. When accessing a spanner through the \code{spanners}
+argument of \code{tab_spanner()} or \code{\link[=cells_column_spanners]{cells_column_spanners()}} (when using
+\code{\link[=tab_style]{tab_style()}} or \code{\link[=tab_footnote]{tab_footnote()}}) the \code{id} value is used as the reference
+(and not the \code{label}). If an \code{id} is not explicitly provided here, it will
+be taken from the \code{label} value. It is advisable to set an explicit \code{id}
+value if you plan to access this cell in a later function call and the
+label text is complicated (e.g., contains markup, is lengthy, or both).
+Finally, when providing an \code{id} value you must ensure that it is unique
+across all ID values set for column spanner labels (the function will stop
+if \code{id} isn't unique).}
+
+\item{gather}{\emph{Gather columns together}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to move the specified \code{columns} such that they are unified under
+the spanner. Ordering of the moved-into-place columns will be preserved in
+all cases. By default, this is set to \code{TRUE}.}
+
+\item{replace}{\emph{Replace existing spanners}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should new spanners be allowed to partially or fully replace existing
+spanners? (This is a possibility if setting spanners at an already
 populated \code{level}.) By default, this is set to \code{FALSE} and an error will
 occur if some replacement is attempted.}
 }
diff --git a/man/tab_spanner_delim.Rd b/man/tab_spanner_delim.Rd
index 480e86b27c..187cf8ccf0 100644
--- a/man/tab_spanner_delim.Rd
+++ b/man/tab_spanner_delim.Rd
@@ -14,44 +14,67 @@ tab_spanner_delim(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{delim}{The delimiter to use to split an input column name. This should
-be a single character (e.g., \code{"_"}, \code{"."}, etc.).}
-
-\item{columns}{The columns to consider for the splitting, relabeling, and
-spanner setting operations. This can either be a series of column names
-provided in \code{\link[=c]{c()}}, a vector of column indices, or a helper function
-focused on selections. The select helper functions are: \code{\link[=starts_with]{starts_with()}},
-\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
-\code{\link[=everything]{everything()}}. By default, we consider all columns in the table through
-the use of \code{\link[=everything]{everything()}}.}
-
-\item{split}{Should the delimiter splitting occur from the \code{"last"} instance
-of the \code{delim} character or from the \code{"first"}? The default here uses the
-\code{"last"} keyword, and splitting begins at the last instance of the
-delimiter in the column name. This option only has some consequence when
-there is a \code{limit} value applied that is lesser than the number of
-delimiter characters for a given column name (i.e., number of splits is not
-the maximum possible number).}
-
-\item{limit}{An optional limit to place on the splitting procedure. The
-default \code{NULL} means that a column name will be split as many times are
-there are delimiter characters. In other words, the default is no limit. If
-an integer value is given to \code{limit} then splitting will cease at the
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{delim}{\emph{Delimiter for splitting}
+
+\verb{scalar<character>} --- \strong{required}
+
+The delimiter to use to split an input column name. This should be a single
+character (e.g., \code{"_"}, \code{"."}, etc.).}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to consider for the splitting, relabeling, and spanner setting
+operations. Can either be a series of column names provided in \code{\link[=c]{c()}}, a
+vector of column indices, or a select helper function. Examples of select
+helper functions include \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}},
+\code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. This argument
+works in tandem with the \code{spanners} argument.}
+
+\item{split}{\emph{Splitting side}
+
+\verb{singl-kw:[last|first]} --- \emph{default:} \code{"last"}
+
+Should the delimiter splitting occur from the \code{"last"} instance of the
+\code{delim} character or from the \code{"first"}? The default here uses the \code{"last"}
+keyword, and splitting begins at the last instance of the delimiter in the
+column name. This option only has some consequence when there is a \code{limit}
+value applied that is lesser than the number of delimiter characters for a
+given column name (i.e., number of splits is not the maximum possible
+number).}
+
+\item{limit}{\emph{Limit for splitting}
+
+\verb{scalar<numeric|integer|character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional limit to place on the splitting procedure. The default \code{NULL}
+means that a column name will be split as many times are there are
+delimiter characters. In other words, the default means there is no limit.
+If an integer value is given to \code{limit} then splitting will cease at the
 iteration given by \code{limit}. This works in tandem with \code{split} since we can
 adjust the number of splits from either the right side (\code{split = "last"})
 or left side (\code{split = "first"}) of the column name.}
 
-\item{reverse}{Should the order of split names be reversed? By default, this
-is \code{FALSE}.}
+\item{reverse}{\emph{Reverse vector of split names}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the order of split names be reversed? By default, this is \code{FALSE}.}
 }
 \value{
 An object of class \code{gt_tbl}.
 }
 \description{
 The \code{cols_spanner_delim()} function can take specially-crafted column names
-and generate one or more spanner column labels (along with relabeling the
+and generate one or more spanners (along with relabeling the
 column labels). This is done by splitting the column name by a specified
 delimiter character (this is the \code{delim}) and placing the fragments from top
 to bottom (i.e., higher-level spanners to the column labels). Furthermore,
@@ -84,7 +107,7 @@ If we take a hypothetical table that includes the column names
 well-defined structure. We start with the more general to the left
 (\code{"province"}) and move to the more specific on the right (\code{"pop"}). If the
 columns are in the table in this exact order, then things are in an ideal
-state as the eventual spanner column labels will form from this neighboring.
+state as the eventual spanner labels will form from this neighboring.
 When using \code{tab_spanner_delim()} here with \code{delim} set as \code{"."} we get the
 following text fragments:
 \itemize{
@@ -274,7 +297,7 @@ column labels with \code{\link[=cols_label_with]{cols_label_with()}}.
 
 \seealso{
 \code{\link[=tab_spanner]{tab_spanner()}} to manually create spanners with more control over
-spanner column labels.
+spanner labels.
 
 Other part creation/modification functions: 
 \code{\link{tab_caption}()},
diff --git a/man/tab_stub_indent.Rd b/man/tab_stub_indent.Rd
index a0be5cd129..7b3ba6b252 100644
--- a/man/tab_stub_indent.Rd
+++ b/man/tab_stub_indent.Rd
@@ -7,21 +7,35 @@
 tab_stub_indent(data, rows, indent = "increase")
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{rows}{The rows to consider for the indentation change. Can either be a
-vector of row captions provided in \code{c()}, a vector of row indices, or a
-helper function focused on selections. The select helper functions are:
-\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, and
-\code{\link[=everything]{everything()}}.}
-
-\item{indent}{An indentation directive either as a keyword describing the
-indentation change or as an explicit integer value for directly setting the
-indentation level. The keyword \code{"increase"} (the default) will increase the
-indentation level by one; \code{"decrease"} will do the same in the reverse
-direction. The starting indentation level of \code{0} means no indentation and
-this values serves as a lower bound. The upper bound for indentation is at
-level \code{5}.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \strong{required}
+
+The rows to consider for the indentation change. The default \code{\link[=everything]{everything()}}
+results in all rows being targeted. Alternatively, we can supply a vector
+of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a select helper
+function. Examples of select helper functions include \code{\link[=starts_with]{starts_with()}},
+\code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and
+\code{\link[=everything]{everything()}}. We can also use expressions to filter down to the rows we
+need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{indent}{\emph{Indentation directive}
+
+\verb{scalar<character|numeric|integer>} --- \emph{default:} \code{"increase"}
+
+An indentation directive either as a keyword describing the indentation
+change or as an explicit integer value for directly setting the indentation
+level. The keyword \code{"increase"} (the default) will increase the indentation
+level by one; \code{"decrease"} will do the same in the reverse direction. The
+starting indentation level of \code{0} means no indentation and this values
+serves as a lower bound. The upper bound for indentation is at level \code{5}.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_stubhead.Rd b/man/tab_stubhead.Rd
index 334b46dfa2..8fdff3235a 100644
--- a/man/tab_stubhead.Rd
+++ b/man/tab_stubhead.Rd
@@ -7,11 +7,20 @@
 tab_stubhead(data, label)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{label}{The text to be used as the stubhead label. We can optionally use
-the \code{\link[=md]{md()}} and \code{\link[=html]{html()}} functions to style the text as Markdown or to
-retain HTML elements in the text.}
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{label}{\emph{Stubhead label text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The text to be used as the stubhead label. We can optionally use the \code{\link[=md]{md()}}
+and \code{\link[=html]{html()}} functions to style the text as Markdown or to retain HTML
+elements in the text.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/tab_style.Rd b/man/tab_style.Rd
index 8c9ffbd9bb..0d8b5b48f9 100644
--- a/man/tab_style.Rd
+++ b/man/tab_style.Rd
@@ -7,21 +7,34 @@
 tab_style(data, style, locations)
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{style}{The styles to use for the cells at the targeted \code{locations}. The
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{style}{\emph{Style declarations}
+
+\verb{<style expressions>} --- \strong{required}
+
+The styles to use for the cells at the targeted \code{locations}. The
 \code{\link[=cell_text]{cell_text()}}, \code{\link[=cell_fill]{cell_fill()}}, and \code{\link[=cell_borders]{cell_borders()}} helper functions can be
 used here to more easily generate valid styles. If using more than one
 helper function to define styles, all calls must be enclosed in a \code{\link[=list]{list()}}.
 Custom CSS declarations can be used for HTML output by including a
 \code{\link[=css]{css()}}-based statement as a list item.}
 
-\item{locations}{the cell or set of cells to be associated with the style.
-Supplying any of the \verb{cells_*()} helper functions is a useful way to target
-the location cells that are associated with the styling. These helper
-functions are: \code{\link[=cells_title]{cells_title()}}, \code{\link[=cells_stubhead]{cells_stubhead()}},
-\code{\link[=cells_column_spanners]{cells_column_spanners()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
-\code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_summary]{cells_summary()}}, \code{\link[=cells_grand_summary]{cells_grand_summary()}},
+\item{locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \strong{required}
+
+The cell or set of cells to be associated with the style. Supplying any of
+the \verb{cells_*()} helper functions is a useful way to target the location
+cells that are associated with the styling. These helper functions are:
+\code{\link[=cells_title]{cells_title()}}, \code{\link[=cells_stubhead]{cells_stubhead()}}, \code{\link[=cells_column_spanners]{cells_column_spanners()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, \code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_stub]{cells_stub()}},
+\code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_summary]{cells_summary()}}, \code{\link[=cells_grand_summary]{cells_grand_summary()}},
 \code{\link[=cells_stub_summary]{cells_stub_summary()}}, \code{\link[=cells_stub_grand_summary]{cells_stub_grand_summary()}}, \code{\link[=cells_footnotes]{cells_footnotes()}},
 and \code{\link[=cells_source_notes]{cells_source_notes()}}. Additionally, we can enclose several
 \verb{cells_*()} calls within a \code{list()} if we wish to apply styling to
diff --git a/man/tab_style_body.Rd b/man/tab_style_body.Rd
index 1b2c5085fa..4ac8584d32 100644
--- a/man/tab_style_body.Rd
+++ b/man/tab_style_body.Rd
@@ -17,55 +17,90 @@ tab_style_body(
 )
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{style}{The styles to use for the targeted cells. The \code{\link[=cell_text]{cell_text()}},
-\code{\link[=cell_fill]{cell_fill()}}, and \code{\link[=cell_borders]{cell_borders()}} helper functions can be used here to
-more easily generate valid styles. If using more than one helper function
-to define styles, all calls must be enclosed in a \code{\link[=list]{list()}}. Custom CSS
-declarations can be used for HTML output by including a \code{\link[=css]{css()}}-based
-statement as a list item.}
-
-\item{columns}{Optional columns for constraining the targeting process.
-Providing \code{\link[=everything]{everything()}} (the default) results in cells in all \code{columns}
-being targeting (this can be limited by \code{rows} however). Can either be a
-series of column names provided in \code{\link[=c]{c()}}, a vector of column indices, or a
-helper function focused on selections. The select helper functions are:
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{style}{\emph{Style declarations}
+
+\verb{<style expressions>} --- \strong{required}
+
+The styles to use for the targeted cells. The \code{\link[=cell_text]{cell_text()}}, \code{\link[=cell_fill]{cell_fill()}},
+and \code{\link[=cell_borders]{cell_borders()}} helper functions can be used here to more easily
+generate valid styles. If using more than one helper function to define
+styles, all calls must be enclosed in a \code{\link[=list]{list()}}. Custom CSS declarations
+can be used for HTML output by including a \code{\link[=css]{css()}}-based statement as a
+list item.}
+
+\item{columns}{\emph{Columns to target}
+
+\verb{<column-targeting expression>} --- \emph{default:} \code{everything()}
+
+The columns to which the targeting operations are constrained.  Can either
+be a series of column names provided in \code{\link[=c]{c()}}, a vector of column indices,
+or a select helper function. Examples of select helper functions include
 \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
-\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.}
-
-\item{rows}{Optional rows for constraining the targeting process. Providing
-\code{\link[=everything]{everything()}} (the default) results in all rows in \code{columns} being
-targeted. Alternatively, we can supply a vector of row captions within
-\code{\link[=c]{c()}}, a vector of row indices, or a helper function focused on selections.
-The select helper functions are: \code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}},
-\code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}}, \code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}.
-We can also use expressions to filter down to the rows we need (e.g.,
-\verb{[colname_1] > 100 & [colname_2] < 50}).}
-
-\item{values}{The specific value or values that should be targeted for
-styling. If \code{pattern} is also supplied then \code{values} will be ignored.}
-
-\item{pattern}{A regex pattern that can target solely those values in
-\code{character}-based columns. If \code{values} is also supplied, \code{pattern} will
-take precedence.}
-
-\item{fn}{A supplied function that operates on each cell of each column
-specified through \code{columns} and \code{rows}. The function should be fashioned
-such that a single logical value is returned. If either of \code{values} or
-\code{pattern} is also supplied, \code{fn} will take precedence.}
-
-\item{targets}{A vector of styling target keywords to contain or expand the
-target of each cell. By default, this is a vector just containing \code{"cell"}.
-However, the keywords \code{"row"} and \code{"column"} may be used separately or in
-combination to style the target cells' associated rows or columns.}
-
-\item{extents}{A vector of locations to project styling. By default, this is
-a vector just containing \code{"body"}, whereby styled rows or columns
-(facilitated via inclusion of the \code{"row"} and \code{"column"} keywords in
-\code{targets}) will not permeate into the stub. The additional keyword \code{"stub"}
-may be used alone or in conjunction with \code{"body"} to project or expand the
-styling into the stub.}
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. This argument works in tandem with the
+\code{spanners} argument.}
+
+\item{rows}{\emph{Rows to target}
+
+\verb{<row-targeting expression>} --- \emph{default:} \code{everything()}
+
+In conjunction with \code{columns}, we can specify which of their rows should
+form a constraint for targeting operations. The default \code{\link[=everything]{everything()}}
+results in all rows in \code{columns} being formatted. Alternatively, we can
+supply a vector of row captions within \code{\link[=c]{c()}}, a vector of row indices, or a
+select helper function. Examples of select helper functions include
+\code{\link[=starts_with]{starts_with()}}, \code{\link[=ends_with]{ends_with()}}, \code{\link[=contains]{contains()}}, \code{\link[=matches]{matches()}}, \code{\link[=one_of]{one_of()}},
+\code{\link[=num_range]{num_range()}}, and \code{\link[=everything]{everything()}}. We can also use expressions to filter
+down to the rows we need (e.g., \verb{[colname_1] > 100 & [colname_2] < 50}).}
+
+\item{values}{\emph{Values for targeting}
+
+\verb{vector<character|numeric|integer>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The specific value or values that should be targeted for styling. If
+\code{pattern} is also supplied then \code{values} will be ignored.}
+
+\item{pattern}{\emph{Regex pattern for targeting}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A regex pattern that can target solely those values in \code{character}-based
+columns. If \code{values} is also supplied, \code{pattern} will take precedence.}
+
+\item{fn}{\emph{Function to return logical values}
+
+\verb{<function>} --- \emph{default:} \code{NULL} (\code{optional})
+
+A supplied function that operates on each cell of each column specified
+through \code{columns} and \code{rows}. The function should be fashioned such that a
+single logical value is returned. If either of \code{values} or \code{pattern} is
+also supplied, \code{fn} will take precedence.}
+
+\item{targets}{\emph{Styling targets}
+
+\verb{vector<character>} --- \emph{default:} \code{"cell"}
+
+A vector of styling target keywords to contain or expand the target of each
+cell. By default, this is a vector just containing \code{"cell"}. However, the
+keywords \code{"row"} and \code{"column"} may be used separately or in combination to
+style the target cells' associated rows or columns.}
+
+\item{extents}{\emph{Styling extents}
+
+\verb{vector<character>} --- \emph{default:} \code{"body"}
+
+A vector of locations to project styling. By default, this is a vector just
+containing \code{"body"}, whereby styled rows or columns (facilitated via
+inclusion of the \code{"row"} and \code{"column"} keywords in \code{targets}) will not
+permeate into the stub. The additional keyword \code{"stub"} may be used alone
+or in conjunction with \code{"body"} to project or expand the styling into the
+stub.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/test_image.Rd b/man/test_image.Rd
index be144e2482..901f063ae2 100644
--- a/man/test_image.Rd
+++ b/man/test_image.Rd
@@ -7,8 +7,12 @@
 test_image(type = c("png", "svg"))
 }
 \arguments{
-\item{type}{The type of the image, which can either be \code{png} (the default) or
-\code{svg}.}
+\item{type}{\emph{The image type}
+
+\verb{singl-kw:[png|svg]} --- \emph{default:} \code{"png"}
+
+The type of image to produce here can either be \code{"png"} (the default) or
+\code{"svg"}.}
 }
 \value{
 A character vector with a single path to an image file.
diff --git a/man/text_case_match.Rd b/man/text_case_match.Rd
index 3ba963d836..e8607f61a8 100644
--- a/man/text_case_match.Rd
+++ b/man/text_case_match.Rd
@@ -13,32 +13,51 @@ text_case_match(
 )
 }
 \arguments{
-\item{.data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{...}{A sequence of two-sided formulas matching this general
-construction: \verb{<old_text> ~ <new_text>}. The left hand side (LHS)
-determines which values to match on and it can be any length (allowing for
-\code{new_text} to replace different values of \code{old_text}). The right hand side
-(RHS) provides the replacement text (it must resolve to a single value of
-the \code{character} class).}
-
-\item{.default}{The replacement text to use when cell values aren't matched
-by any of the LHS inputs. If \code{NULL}, the default, no replacement text will
-be used.}
-
-\item{.replace}{A choice in how the matching is to be done. The default
-\code{"all"} means that the \code{old_text} (on the LHS of formulas given in \code{...})
-must match the cell text \emph{completely}. With that option, the replacement
-will completely replace that matched text. With \code{"partial"}, the match will
-occur in all substrings of \code{old_text}. In this way, the replacements will
-act on those matched substrings.}
-
-\item{.locations}{The cell or set of cells to be associated with the text
-transformation. Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}},
-\code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, and
-\code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can be used here. We can enclose
-several of these calls within a \code{list()} if we wish to make the
-transformation happen at different locations.}
+\item{.data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Matching expressions}
+
+\verb{<multiple expressions>} --- \strong{required}
+
+A sequence of two-sided formulas matching this general construction:
+\verb{<old_text> ~ <new_text>}. The left hand side (LHS) determines which values
+to match on and it can be any length (allowing for \code{new_text} to replace
+different values of \code{old_text}). The right hand side (RHS) provides the
+replacement text (it must resolve to a single value of the \code{character}
+class).}
+
+\item{.default}{\emph{Default replacement text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The replacement text to use when cell values aren't matched by any of the
+LHS inputs. If \code{NULL}, the default, no replacement text will be used.}
+
+\item{.replace}{\emph{Method for text replacement}
+
+\verb{singl-kw:[all|partial]} --- \emph{default:} \code{"all"}
+
+A choice in how the matching is to be done. The default \code{"all"} means that
+the \code{old_text} (on the LHS of formulas given in \code{...}) must match the cell
+text \emph{completely}. With that option, the replacement will completely
+replace that matched text. With \code{"partial"}, the match will occur in all
+substrings of \code{old_text}. In this way, the replacements will act on those
+matched substrings.}
+
+\item{.locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \emph{default:} \code{cells_body()}
+
+The cell or set of cells to be associated with the text transformation.
+Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, and \code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can
+be used here. We can enclose several of these calls within a \code{list()} if we
+wish to make the transformation happen at different locations.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/text_case_when.Rd b/man/text_case_when.Rd
index 433a915c71..54f5f132e6 100644
--- a/man/text_case_when.Rd
+++ b/man/text_case_when.Rd
@@ -7,23 +7,38 @@
 text_case_when(.data, ..., .default = NULL, .locations = cells_body())
 }
 \arguments{
-\item{.data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{.data}{\emph{The gt table data object}
 
-\item{...}{A sequence of two-sided formulas. The left hand side (LHS)
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{...}{\emph{Matching expressions}
+
+\verb{<multiple expressions>} --- \strong{required}
+
+A sequence of two-sided formulas. The left hand side (LHS)
 determines which values match this case. The right hand side (RHS) provides
 the replacement text (it must resolve to a value of the \code{character} class).
 The LHS inputs must evaluate to logical vectors.}
 
-\item{.default}{The replacement text to use when cell values aren't matched
-by any of the LHS inputs. If \code{NULL}, the default, no replacement text will
-be used.}
+\item{.default}{\emph{Default replacement text}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The replacement text to use when cell values aren't matched by any of the
+LHS inputs. If \code{NULL}, the default, no replacement text will be used.}
+
+\item{.locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \emph{default:} \code{cells_body()}
 
-\item{.locations}{The cell or set of cells to be associated with the text
-transformation. Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}},
-\code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, and
-\code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can be used here. We can enclose
-several of these calls within a \code{list()} if we wish to make the
-transformation happen at different locations.}
+The cell or set of cells to be associated with the text transformation.
+Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, and \code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can
+be used here. We can enclose several of these calls within a \code{list()} if we
+wish to make the transformation happen at different locations.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/text_replace.Rd b/man/text_replace.Rd
index 060f991b2b..54ded7e243 100644
--- a/man/text_replace.Rd
+++ b/man/text_replace.Rd
@@ -7,19 +7,35 @@
 text_replace(data, pattern, replacement, locations = cells_body())
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
+\item{data}{\emph{The gt table data object}
 
-\item{pattern}{A regex pattern used to target text fragments in the cells
-resolved in locations.}
+\verb{obj:<gt_tbl>} --- \strong{required}
 
-\item{replacement}{The replacement text for any matched text fragments.}
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
 
-\item{locations}{The cell or set of cells to be associated with the text
-transformation. Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}},
-\code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, and
-\code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can be used here. We can enclose
-several of these calls within a \code{list()} if we wish to make the
-transformation happen at different locations.}
+\item{pattern}{\emph{Regex pattern to match with}
+
+\verb{scalar<character>} --- \strong{required}
+
+A regex pattern used to target text fragments in the cells resolved in
+locations.}
+
+\item{replacement}{\emph{Replacement text}
+
+\verb{scalar<character>} --- \strong{required}
+
+The replacement text for any matched text fragments.}
+
+\item{locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \emph{default:} \code{cells_body()}
+
+The cell or set of cells to be associated with the text transformation.
+Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, and \code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can
+be used here. We can enclose several of these calls within a \code{list()} if we
+wish to make the transformation happen at different locations.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/text_transform.Rd b/man/text_transform.Rd
index ebd488f062..47df4d0212 100644
--- a/man/text_transform.Rd
+++ b/man/text_transform.Rd
@@ -7,18 +7,29 @@
 text_transform(data, fn, locations = cells_body())
 }
 \arguments{
-\item{data}{A table object that is created using the \code{\link[=gt]{gt()}} function.}
-
-\item{fn}{The function to use for text transformation. It should include \code{x}
-as an argument and return a character vector of the same length as the
-input \code{x}.}
-
-\item{locations}{The cell or set of cells to be associated with the text
-transformation. Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}},
-\code{\link[=cells_row_groups]{cells_row_groups()}}, \code{\link[=cells_column_labels]{cells_column_labels()}}, and
-\code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can be used here. We can enclose
-several of these calls within a \code{list()} if we wish to make the
-transformation happen at different locations.}
+\item{data}{\emph{The gt table data object}
+
+\verb{obj:<gt_tbl>} --- \strong{required}
+
+This is the \strong{gt} table object that is commonly created through use of the
+\code{\link[=gt]{gt()}} function.}
+
+\item{fn}{\emph{Function for text transformation}
+
+\verb{<function>} --- \strong{required}
+
+The function to use for text transformation. It should include \code{x} as an
+argument and return a character vector of the same length as the input \code{x}.}
+
+\item{locations}{\emph{Locations to target}
+
+\verb{<locations expressions>} --- \emph{default:} \code{cells_body()}
+
+The cell or set of cells to be associated with the text transformation.
+Only the \code{\link[=cells_body]{cells_body()}}, \code{\link[=cells_stub]{cells_stub()}}, \code{\link[=cells_row_groups]{cells_row_groups()}},
+\code{\link[=cells_column_labels]{cells_column_labels()}}, and \code{\link[=cells_column_spanners]{cells_column_spanners()}} helper functions can
+be used here. We can enclose several of these calls within a \code{list()} if we
+wish to make the transformation happen at different locations.}
 }
 \value{
 An object of class \code{gt_tbl}.
diff --git a/man/vec_fmt_bytes.Rd b/man/vec_fmt_bytes.Rd
index 3134dc901d..e1077a1e30 100644
--- a/man/vec_fmt_bytes.Rd
+++ b/man/vec_fmt_bytes.Rd
@@ -22,63 +22,127 @@ vec_fmt_bytes(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{standard}{The way to express large byte sizes.}
-
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{1}.}
-
-\item{n_sigfig}{A option to format numbers to \emph{n} significant figures. By
-default, this is \code{NULL} and thus number values will be formatted according
-to the number of decimal places set via \code{decimals}. If opting to format
-according to the rules of significant figures, \code{n_sigfig} must be a number
-greater than or equal to \code{1}. Any values passed to the \code{decimals} and
-\code{drop_trailing_zeros} arguments will be ignored.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive numbers
-(effectively showing a sign for all numbers except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the units. The default of \code{TRUE} uses a space character for separation.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{standard}{\emph{Standard used to express byte sizes}
+
+\verb{singl-kw:[decimal|binary]} --- \emph{default:} \code{"decimal"}
+
+The form of expressing large byte sizes is divided between: (1) decimal
+units (powers of 1000; e.g., \code{"kB"} and \code{"MB"}), and (2) binary units
+(powers of 1024; e.g., \code{"KiB"} and \code{"MiB"}).}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{1}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}.}
+
+\item{n_sigfig}{\emph{Number of significant figures}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+A option to format numbers to \emph{n} significant figures. By default, this is
+\code{NULL} and thus number values will be formatted according to the number of
+decimal places set via \code{decimals}. If opting to format according to the
+rules of significant figures, \code{n_sigfig} must be a number greater than or
+equal to \code{1}. Any values passed to the \code{decimals} and \code{drop_trailing_zeros}
+arguments will be ignored.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive numbers (effectively showing
+a sign for all numbers except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.}
+
+\item{incl_space}{\emph{Include a space between the value and the units}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option for whether to include a space between the value and the units.
+The default is to use a space character for separation.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_currency.Rd b/man/vec_fmt_currency.Rd
index f68ded2686..0d3e002f0a 100644
--- a/man/vec_fmt_currency.Rd
+++ b/man/vec_fmt_currency.Rd
@@ -25,9 +25,18 @@ vec_fmt_currency(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{currency}{The currency to use for the numeric value. This input can be
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{currency}{\emph{Currency to use}
+
+\verb{scalar<character>|obj:<gt_currency>} --- \emph{default:} \code{"USD"}
+
+The currency to use for the numeric value. This input can be
 supplied as a 3-letter currency code (e.g., \code{"USD"} for U.S. Dollars,
 \code{"EUR"} for the Euro currency). Use \code{\link[=info_currencies]{info_currencies()}} to get an
 information table with all of the valid currency codes and examples of
@@ -42,87 +51,159 @@ currency, where the string could vary across output contexts. For example,
 using \code{currency(html = "&fnof;", default = "f")} would give us a suitable
 glyph for the Dutch guilder in an HTML output table, and it would simply be
 the letter "f" in all other output contexts). Please note that \code{decimals}
-will default to \code{2} when using the \code{\link[=currency]{currency()}} helper function.
+will default to \code{2} when using the \code{\link[=currency]{currency()}} helper function.}
+
+\item{use_subunits}{\emph{Show or hide currency subunits}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option for whether the subunits portion of a currency value should be
+displayed. For example, with an input value of \code{273.81}, the default
+formatting will produce \code{"$273.81"}. Removing the subunits (with
+\code{use_subunits = FALSE}) will give us \code{"$273"}.}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
 
-If nothing is provided to \code{currency} then \code{"USD"} (U.S. dollars) will be
-used.}
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{use_subunits}{An option for whether the subunits portion of a currency
-value should be displayed. By default, this is \code{TRUE}.}
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\item{use_seps}{\emph{Use digit group separators}
 
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
 
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
 
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
+\item{accounting}{\emph{Use accounting style}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
-transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
-billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
+
+\item{suffixing}{\emph{Specification for large-number suffixing}
+
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
+
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
+transformation and \code{TRUE} will apply thousands (\code{"K"}), millions (\code{"M"}),
+billions (\code{"B"}), and trillions (\code{"T"}) suffixes after automatic value
+scaling.
+
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
 that any value provided to \code{scale_by} will be ignored.}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{placement}{The placement of the currency symbol. This can be either be
-\code{left} (the default) or \code{right}.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the currency symbol. The default is to not introduce a space character.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{placement}{\emph{Currency symbol placement}
+
+\verb{scalar<character>} --- \emph{default:} \code{"left"}
+
+The placement of the currency symbol. This can be either be \code{left} (as
+in \code{"$450"}) or \code{right} (which yields \code{"450$"}).}
+
+\item{incl_space}{\emph{Include a space between the value and the currency symbol}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option for whether to include a space between the value and the currency
+symbol. The default is to not introduce a space character.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_date.Rd b/man/vec_fmt_date.Rd
index 32176abcbf..0eec87a943 100644
--- a/man/vec_fmt_date.Rd
+++ b/man/vec_fmt_date.Rd
@@ -13,27 +13,50 @@ vec_fmt_date(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{date_style}{The date style to use. By default this is \code{"iso"} which
-corresponds to ISO 8601 date formatting. The other date styles can be
-viewed using \code{\link[=info_date_style]{info_date_style()}}.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{date_style}{\emph{Predefined style for dates}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=41)} --- \emph{default:} \code{"iso"}
+
+The date style to use. By default this is the short name \code{"iso"} which
+corresponds to ISO 8601 date formatting. There are 41 date styles in total
+and their short names can be viewed using \code{\link[=info_date_style]{info_date_style()}}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_datetime.Rd b/man/vec_fmt_datetime.Rd
index d95165b741..5a1e1a06d5 100644
--- a/man/vec_fmt_datetime.Rd
+++ b/man/vec_fmt_datetime.Rd
@@ -17,46 +17,86 @@ vec_fmt_datetime(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{date_style}{The date style to use. By default this is \code{"iso"} which
-corresponds to ISO 8601 date formatting. The other date styles can be
-viewed using \code{\link[=info_date_style]{info_date_style()}}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{time_style}{The time style to use. By default this is \code{"iso"} which
-corresponds to how times are formatted within ISO 8601 datetime values. The
-other time styles can be viewed using \code{\link[=info_time_style]{info_time_style()}}.}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{sep}{The separator string to use between the date and time components.
-By default, this is a single space character (\code{" "}). Only used when not
+\item{date_style}{\emph{Predefined style for dates}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=41)} --- \emph{default:} \code{"iso"}
+
+The date style to use. By default this is the short name \code{"iso"} which
+corresponds to ISO 8601 date formatting. There are 41 date styles in total
+and their short names can be viewed using \code{\link[=info_date_style]{info_date_style()}}.}
+
+\item{time_style}{\emph{Predefined style for times}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=25)} --- \emph{default:} \code{"iso"}
+
+The time style to use. By default this is the short name \code{"iso"} which
+corresponds to how times are formatted within ISO 8601 datetime values.
+There are 25 time styles in total and their short names can be viewed using
+\code{\link[=info_time_style]{info_time_style()}}.}
+
+\item{sep}{\emph{Separator between date and time components}
+
+\verb{scalar<character>} --- \emph{default:} \code{" "}
+
+The separator string to use between the date and time components. By
+default, this is a single space character (\code{" "}). Only used when not
 specifying a \code{format} code.}
 
-\item{format}{An optional format code used for generating custom dates/times.
-If used then the arguments governing preset styles (\code{date_style} and
+\item{format}{\emph{Date/time formatting string}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional formatting string used for generating custom dates/times. If
+used then the arguments governing preset styles (\code{date_style} and
 \code{time_style}) will be ignored in favor of formatting via the \code{format}
 string.}
 
-\item{tz}{The time zone for printing dates/times (i.e., the output). The
+\item{tz}{\emph{Time zone}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+The time zone for printing dates/times (i.e., the output). The
 default of \code{NULL} will preserve the time zone of the input data in the
 output. If providing a time zone, it must be one that is recognized by the
 user's operating system (a vector of all valid \code{tz} values can be produced
 with \code{\link[=OlsonNames]{OlsonNames()}}).}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_duration.Rd b/man/vec_fmt_duration.Rd
index 8ce0a08438..0d183fa9ab 100644
--- a/man/vec_fmt_duration.Rd
+++ b/man/vec_fmt_duration.Rd
@@ -20,76 +20,127 @@ vec_fmt_duration(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{input_units}{If one or more selected columns contains numeric values, a
-keyword must be provided for \code{input_units} for \strong{gt} to determine how
-those values are to be interpreted in terms of duration. The accepted units
-are: \code{"seconds"}, \code{"minutes"}, \code{"hours"}, \code{"days"}, and \code{"weeks"}.}
-
-\item{output_units}{Controls the output time units. The default, \code{NULL},
-means that \strong{gt} will automatically choose time units based on the input
-duration value. To control which time units are to be considered for output
-(before trimming with \code{trim_zero_units}) we can specify a vector of one or
-more of the following keywords: \code{"weeks"}, \code{"days"}, \code{"hours"},
-\code{"minutes"}, or \code{"seconds"}.}
-
-\item{duration_style}{A choice of four formatting styles for the output
-duration values. With \code{"narrow"} (the default style), duration values will
-be formatted with single letter time-part units (e.g., 1.35 days will be
-styled as \verb{"1d 8h 24m}). With \code{"wide"}, this example value will be expanded
-to \code{"1 day 8 hours 24 minutes"} after formatting. The \code{"colon-sep"} style
-will put days, hours, minutes, and seconds in the \code{"([D]/)[HH]:[MM]:[SS]"}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{input_units}{\emph{Declaration of duration units for numerical values}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+If one or more selected columns contains numeric values (not \code{difftime}
+values, which contain the duration units), a keyword must be provided for
+\code{input_units} for \strong{gt} to determine how those values are to be
+interpreted in terms of duration. The accepted units are: \code{"seconds"},
+\code{"minutes"}, \code{"hours"}, \code{"days"}, and \code{"weeks"}.}
+
+\item{output_units}{\emph{Choice of output units}
+
+\verb{mult-kw:[weeks|days|hours|minutes|seconds]} --- \emph{default:} \code{NULL} (\code{optional})
+
+Controls the output time units. The default, \code{NULL}, means that \strong{gt} will
+automatically choose time units based on the input duration value. To
+control which time units are to be considered for output (before trimming
+with \code{trim_zero_units}) we can specify a vector of one or more of the
+following keywords: \code{"weeks"}, \code{"days"}, \code{"hours"}, \code{"minutes"}, or
+\code{"seconds"}.}
+
+\item{duration_style}{\emph{Style for representing duration values}
+
+\verb{singl-kw:[narrow|wide|colon-sep|iso]} --- \emph{default:} \code{"narrow"}
+
+A choice of four formatting styles for the output duration values. With
+\code{"narrow"} (the default style), duration values will be formatted with
+single letter time-part units (e.g., 1.35 days will be styled as
+\code{"1d 8h 24m"}). With \code{"wide"}, this example value will be expanded to
+\code{"1 day 8 hours 24 minutes"} after formatting. The \code{"colon-sep"} style will
+put days, hours, minutes, and seconds in the \code{"([D]/)[HH]:[MM]:[SS]"}
 format. The \code{"iso"} style will produce a value that conforms to the ISO
 8601 rules for duration values (e.g., 1.35 days will become \code{"P1DT8H24M"}).}
 
-\item{trim_zero_units}{Provides methods to remove output time units that have
-zero values. By default this is \code{TRUE} and duration values that might
-otherwise be formatted as \code{"0w 1d 0h 4m 19s"} with
-\code{trim_zero_units = FALSE} are instead displayed as \code{"1d 4m 19s"}. Aside
-from using \code{TRUE}/\code{FALSE} we could provide a vector of keywords for more
-precise control. These keywords are: (1) \code{"leading"}, to omit all leading
-zero-value time units (e.g., \code{"0w 1d"} -> \code{"1d"}), (2) \code{"trailing"}, to
-omit all trailing zero-value time units (e.g., \code{"3d 5h 0s"} -> \code{"3d 5h"}),
-and \code{"internal"}, which removes all internal zero-value time units (e.g.,
-\code{"5d 0h 33m"} -> \code{"5d 33m"}).}
-
-\item{max_output_units}{If \code{output_units} is \code{NULL}, where the output time
-units are unspecified and left to \strong{gt} to handle, a numeric value
-provided for \code{max_output_units} will be taken as the maximum number of time
-units to display in all output time duration values. By default, this is
-\code{NULL} and all possible time units will be displayed. This option has no
-effect when \code{duration_style = "colon-sep"} (only \code{output_units} can be used
-to customize that type of duration output).}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative value will
-display a minus sign.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{trim_zero_units}{\emph{Trimming of zero values}
+
+\verb{scalar<logical>|mult-kw:[leading|trailing|internal]} --- \emph{default:} \code{TRUE}
+
+Provides methods to remove output time units that have zero values. By
+default this is \code{TRUE} and duration values that might otherwise be
+formatted as \code{"0w 1d 0h 4m 19s"} with \code{trim_zero_units = FALSE} are instead
+displayed as \code{"1d 4m 19s"}. Aside from using \code{TRUE}/\code{FALSE} we could
+provide a vector of keywords for more precise control. These keywords are:
+(1) \code{"leading"}, to omit all leading zero-value time units (e.g., \code{"0w 1d"}
+-> \code{"1d"}), (2) \code{"trailing"}, to omit all trailing zero-value time units
+(e.g., \code{"3d 5h 0s"} -> \code{"3d 5h"}), and \code{"internal"}, which removes all
+internal zero-value time units (e.g., \code{"5d 0h 33m"} -> \code{"5d 33m"}).}
+
+\item{max_output_units}{\emph{Maximum number of time units to display}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+If \code{output_units} is \code{NULL}, where the output time units are unspecified
+and left to \strong{gt} to handle, a numeric value provided for
+\code{max_output_units} will be taken as the maximum number of time units to
+display in all output time duration values. By default, this is \code{NULL} and
+all possible time units will be displayed. This option has no effect when
+\code{duration_style = "colon-sep"} (only \code{output_units} can be used to
+customize that type of duration output).}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. By
+default only negative values will display a minus sign.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_engineering.Rd b/man/vec_fmt_engineering.Rd
index b0d94acd0b..c912d46265 100644
--- a/man/vec_fmt_engineering.Rd
+++ b/man/vec_fmt_engineering.Rd
@@ -20,53 +20,107 @@ vec_fmt_engineering(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.}
+\item{decimals}{\emph{Number of decimal places}
 
-\item{exp_style}{Style of formatting to use for the engineering notation
-formatting. By default this is \code{"x10n"} but other options include using
-a single letter (e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to
-signal a minimum digit width of one, or \code{"low-ten"} for using a stylized
-\code{"10"} marker.}
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
 
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
 
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{force_sign_m, force_sign_n}{Should the plus sign be shown for positive
-values of the mantissa (first component) or the exponent? This would
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied.}
+
+\item{exp_style}{\emph{Style declaration for exponent formatting}
+
+\verb{scalar<character>} --- \emph{default:} \code{"x10n"}
+
+Style of formatting to use for the scientific notation formatting. By
+default this is \code{"x10n"} but other options include using a single letter
+(e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to signal a
+minimum digit width of one, or \code{"low-ten"} for using a stylized \code{"10"}
+marker.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign_m, force_sign_n}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the plus sign be shown for positive values of the mantissa (first
+component, \code{force_sign_m}) or the exponent (\code{force_sign_n})? This would
 effectively show a sign for all values except zero on either of those
 numeric components of the notation. If so, use \code{TRUE} for either one of
 these options. The default for both is \code{FALSE}, where only negative numbers
 will display a sign.}
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_fraction.Rd b/man/vec_fmt_fraction.Rd
index bdb164f4b4..3f18e0d67d 100644
--- a/man/vec_fmt_fraction.Rd
+++ b/man/vec_fmt_fraction.Rd
@@ -17,49 +17,89 @@ vec_fmt_fraction(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{accuracy}{The type of fractions to generate. This can either be one of
-the keywords \code{"low"}, \code{"med"}, or \code{"high"} (to generate fractions with
-denominators of up to 1, 2, or 3 digits, respectively) or an integer value
-greater than zero to obtain fractions with a fixed denominator (\code{2} yields
-halves, \code{3} is for thirds, \code{4} is quarters, etc.). For the latter option,
-using \code{simplify = TRUE} will simplify fractions where possible (e.g., \code{2/4}
-will be simplified as \code{1/2}). By default, the \code{"low"} option is used.}
-
-\item{simplify}{If choosing to provide a numeric value for \code{accuracy}, the
-option to simplify the fraction (where possible) can be taken with \code{TRUE}
-(the default). With \code{FALSE}, denominators in fractions will be fixed to the
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{accuracy}{\emph{Accuracy of fractions}
+
+\verb{singl-kw:[low|med|high]|scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{"low"}
+
+The type of fractions to generate. This can either be one of the keywords
+\code{"low"}, \code{"med"}, or \code{"high"} (to generate fractions with denominators of
+up to 1, 2, or 3 digits, respectively) or an integer value greater than
+zero to obtain fractions with a fixed denominator (\code{2} yields halves, \code{3}
+is for thirds, \code{4} is quarters, etc.). For the latter option, using
+\code{simplify = TRUE} will simplify fractions where possible (e.g., \code{2/4} will
+be simplified as \code{1/2}). By default, the \code{"low"} option is used.}
+
+\item{simplify}{\emph{Simplify the fraction}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+If choosing to provide a numeric value for \code{accuracy}, the option to
+simplify the fraction (where possible) can be taken with \code{TRUE} (the
+default). With \code{FALSE}, denominators in fractions will be fixed to the
 value provided in \code{accuracy}.}
 
-\item{layout}{For HTML output, the \code{"inline"} layout is the default. This
-layout places the numerals of the fraction on the baseline and uses a
-standard slash character. The \code{"diagonal"} layout will generate fractions
-that are typeset with raised/lowered numerals and a virgule.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{layout}{\emph{Layout of fractions in HTML output}
+
+\verb{singl-kw:[inline|diagonal]} --- \emph{default:} \code{"inline"}
+
+For HTML output, the \code{"inline"} layout is the default. This layout places
+the numerals of the fraction on the baseline and uses a standard slash
+character. The \code{"diagonal"} layout will generate fractions that are typeset
+with raised/lowered numerals and a virgule.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_index.Rd b/man/vec_fmt_index.Rd
index c4d2f5e50e..04f7f2e91c 100644
--- a/man/vec_fmt_index.Rd
+++ b/man/vec_fmt_index.Rd
@@ -14,33 +14,59 @@ vec_fmt_index(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{case}{Should resulting index characters be rendered as uppercase
-(\code{"upper"}) or lowercase (\code{"lower"}) letters? By default, this is set to
-\code{"upper"}.}
-
-\item{index_algo}{The indexing algorithm for handling the recycling of the
-index character set. By default, the \code{"repeat"} option is used where
-characters are doubled, tripled, and so on, when moving past the character
-set limit. The alternative is the \code{"excel"} option, where Excel-based
-column naming is adapted and used here (e.g., \verb{[..., Y, Z, AA, AB, ...]}).}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{case}{\emph{Use uppercase or lowercase letters}
+
+\verb{singl-kw:[upper|lower]} --- \emph{default:} \code{"upper"}
+
+Should the resulting index characters be rendered as uppercase (\code{"upper"})
+or lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
+
+\item{index_algo}{\emph{Indexing algorithm}
+
+\verb{singl-kw:[repeat|excel]} --- \emph{default:} \code{"repeat"}
+
+The indexing algorithm handles the recycling of the index character set. By
+default, the \code{"repeat"} option is used where characters are doubled,
+tripled, and so on, when moving past the character set limit. The
+alternative is the \code{"excel"} option, where Excel-based column naming is
+adapted and used here (e.g., \verb{[..., Y, Z, AA, AB, ...]}).}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_integer.Rd b/man/vec_fmt_integer.Rd
index 0313753dd4..b204ef8647 100644
--- a/man/vec_fmt_integer.Rd
+++ b/man/vec_fmt_integer.Rd
@@ -18,63 +18,112 @@ vec_fmt_integer(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
+\item{use_seps}{\emph{Use digit group separators}
 
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{2M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
+
+\item{suffixing}{\emph{Specification for large-number suffixing}
+
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
+
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{2M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
 transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
 billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
 that any value provided to \code{scale_by} will be ignored.}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_markdown.Rd b/man/vec_fmt_markdown.Rd
index e4b9990280..f4356301f9 100644
--- a/man/vec_fmt_markdown.Rd
+++ b/man/vec_fmt_markdown.Rd
@@ -11,17 +11,30 @@ vec_fmt_markdown(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{md_engine}{The engine preference for Markdown rendering. By default,
-this is set to \code{"markdown"} where \strong{gt} will use the \strong{markdown} package
-for Markdown conversion to HTML and LaTeX. The other option is
-\code{"commonmark"} and with that the \strong{commonmark} package will be used.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{md_engine}{\emph{Choice of Markdown engine}
+
+\verb{singl-kw:[markdown|commonmark]} --- \emph{default:} \code{"markdown"}
+
+The engine preference for Markdown rendering. By default, this is set to
+\code{"markdown"} where \strong{gt} will use the \strong{markdown} package for Markdown
+conversion to HTML and LaTeX. The other option is \code{"commonmark"} and with
+that the \strong{commonmark} package will be used.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_number.Rd b/man/vec_fmt_number.Rd
index 25856a3213..7473948aa1 100644
--- a/man/vec_fmt_number.Rd
+++ b/man/vec_fmt_number.Rd
@@ -23,85 +23,159 @@ vec_fmt_number(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
-
-\item{n_sigfig}{A option to format numbers to \emph{n} significant figures. By
-default, this is \code{NULL} and thus number values will be formatted according
-to the number of decimal places set via \code{decimals}. If opting to format
-according to the rules of significant figures, \code{n_sigfig} must be a number
-greater than or equal to \code{1}. Any values passed to the \code{decimals} and
-\code{drop_trailing_zeros} arguments will be ignored.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
-
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.
-This value will be ignored if using any of the \code{suffixing} options (i.e.,
-where \code{suffixing} is not set to \code{FALSE}).}
-
-\item{suffixing}{An option to scale and apply suffixes to larger numbers
-(e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can accept a
-logical value, where \code{FALSE} (the default) will not perform this
-transformation and \code{TRUE} will apply thousands (\code{K}), millions (\code{M}),
-billions (\code{B}), and trillions (\code{T}) suffixes after automatic value scaling.
-We can also specify which symbols to use for each of the value ranges by
-using a character vector of the preferred symbols to replace the defaults
-(e.g., \code{c("k", "Ml", "Bn", "Tr")}).
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{n_sigfig}{\emph{Number of significant figures}
+
+\code{scalar<numeric|integer>(val>=1)} --- \emph{default:} \code{NULL} (\code{optional})
+
+A option to format numbers to \emph{n} significant figures. By default, this is
+\code{NULL} and thus number values will be formatted according to the number of
+decimal places set via \code{decimals}. If opting to format according to the
+rules of significant figures, \code{n_sigfig} must be a number greater than or
+equal to \code{1}. Any values passed to the \code{decimals} and \code{drop_trailing_zeros}
+arguments will be ignored.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied. This value will be
+ignored if using any of the \code{suffixing} options (i.e., where \code{suffixing} is
+not set to \code{FALSE}).}
+
+\item{suffixing}{\emph{Specification for large-number suffixing}
+
+\verb{scalar<logical>|vector<character>} --- \emph{default:} \code{FALSE}
+
+The \code{suffixing} option allows us to scale and apply suffixes to larger
+numbers (e.g., \code{1924000} can be transformed to \verb{1.92M}). This option can
+accept a logical value, where \code{FALSE} (the default) will not perform this
+transformation and \code{TRUE} will apply thousands (\code{"K"}), millions (\code{"M"}),
+billions (\code{"B"}), and trillions (\code{"T"}) suffixes after automatic value
+scaling.
+
+We can alternatively provide a character vector that serves as a
+specification for which symbols are to used for each of the value ranges.
+These preferred symbols will replace the defaults (e.g.,
+\code{c("k", "Ml", "Bn", "Tr")} replaces \code{"K"}, \code{"M"}, \code{"B"}, and \code{"T"}).
 
 Including \code{NA} values in the vector will ensure that the particular range
-will either not be included in the transformation (e.g, \code{c(NA, "M", "B", "T")} won't modify numbers in the thousands range) or the range will
-inherit a previous suffix (e.g., with \code{c("K", "M", NA, "T")}, all numbers
-in the range of millions and billions will be in terms of millions).
+will either not be included in the transformation (e.g.,
+\code{c(NA, "M", "B", "T")} won't modify numbers at all in the thousands range)
+or the range will inherit a previous suffix (e.g., with
+\code{c("K", "M", NA, "T")}, all numbers in the range of millions and billions
+will be in terms of millions).
 
 Any use of \code{suffixing} (where it is not set expressly as \code{FALSE}) means
 that any value provided to \code{scale_by} will be ignored.}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_partsper.Rd b/man/vec_fmt_partsper.Rd
index 1b0c6e1b53..760d83627a 100644
--- a/man/vec_fmt_partsper.Rd
+++ b/man/vec_fmt_partsper.Rd
@@ -23,72 +23,140 @@ vec_fmt_partsper(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{to_units}{A keyword that signifies the desired output quantity. This
-can be any from the following set: \code{"per-mille"}, \code{"per-myriad"}, \code{"pcm"},
-\code{"ppm"}, \code{"ppb"}, \code{"ppt"}, or \code{"ppq"}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{symbol}{The symbol/units to use for the quantity. By default, this is
-set to \code{"auto"} and \strong{gt} will choose the appropriate symbol based on the
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{to_units}{\emph{Output Quantity}
+
+\verb{singl-kw:[per-mille|per-myriad|pcm|ppm|ppb|ppt|ppq]} --- \emph{default:} \code{"per-mille"}
+
+A keyword that signifies the desired output quantity. This can be any from
+the following set: \code{"per-mille"}, \code{"per-myriad"}, \code{"pcm"}, \code{"ppm"},
+\code{"ppb"}, \code{"ppt"}, or \code{"ppq"}.}
+
+\item{symbol}{\emph{Symbol or units to use in output display}
+
+\verb{scalar<character>} --- \emph{default:} \code{"auto"}
+
+The symbol/units to use for the quantity. By default, this is set to
+\code{"auto"} and \strong{gt} will choose the appropriate symbol based on the
 \code{to_units} keyword and the output context. However, this can be changed by
 supplying a string (e.g, using \code{symbol = "ppbV"} when \code{to_units = "ppb"}).}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
-
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
-
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
-
-\item{scale_values}{Should the values be scaled through multiplication
-according to the keyword set in \code{to_units}? By default this is \code{TRUE} since
-the expectation is that normally values are proportions. Setting to \code{FALSE}
-signifies that the values are already scaled and require only the
-appropriate symbol/units when formatted.}
-
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the symbol/units. The default is \code{"auto"} which provides spacing
-dependent on the mark itself. This can be directly controlled by using
-either \code{TRUE} or \code{FALSE}.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{decimals}{\emph{Number of decimal places}
+
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{scale_values}{\emph{Scale input values accordingly}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the values be scaled through multiplication according to the keyword
+set in \code{to_units}? By default this is \code{TRUE} since the expectation is that
+normally values are proportions. Setting to \code{FALSE} signifies that the
+values are already scaled and require only the appropriate symbol/units
+when formatted.}
+
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{incl_space}{\emph{Include a space between the value and the symbol/units}
+
+\verb{scalar<character>|scalar<logical>} --- \emph{default:} \code{"auto"}
+
+An option for whether to include a space between the value and the
+symbol/units. The default is \code{"auto"} which provides spacing dependent on
+the mark itself. This can be directly controlled by using either \code{TRUE} or
+\code{FALSE}.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_percent.Rd b/man/vec_fmt_percent.Rd
index 5208811b61..09a9d43866 100644
--- a/man/vec_fmt_percent.Rd
+++ b/man/vec_fmt_percent.Rd
@@ -23,67 +23,135 @@ vec_fmt_percent(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{drop_trailing_dec_mark}{A logical value that determines whether decimal
-marks should always appear even if there are no decimal digits to display
-after formatting (e.g, \code{23} becomes \code{23.}). The default for this is \code{TRUE},
-which means that trailing decimal marks are not shown.}
+\item{decimals}{\emph{Number of decimal places}
 
-\item{scale_values}{Should the values be scaled through multiplication by
-100? By default this is \code{TRUE} since the expectation is that normally
-values are proportions. Setting to \code{FALSE} signifies that the values are
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
+
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
+
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{drop_trailing_dec_mark}{\emph{Drop the trailing decimal mark}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+A logical value that determines whether decimal marks should always appear
+even if there are no decimal digits to display after formatting (e.g., \code{23}
+becomes \code{23.} if \code{FALSE}). By default trailing decimal marks are not shown.}
+
+\item{scale_values}{\emph{Multiply input values by 100}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+Should the values be scaled through multiplication by 100? By default this
+scaling is performed since the expectation is that incoming values are
+usually proportional. Setting to \code{FALSE} signifies that the values are
 already scaled and require only the percent sign when formatted.}
 
-\item{use_seps}{An option to use digit group separators. The type of digit
-group separator is set by \code{sep_mark} and overridden if a locale ID is
-provided to \code{locale}. This setting is \code{TRUE} by default.}
-
-\item{accounting}{An option to use accounting style for values. With \code{FALSE}
-(the default), negative values will be shown with a minus sign. Using
-\code{accounting = TRUE} will put negative values in parentheses.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
-
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
-
-\item{force_sign}{Should the positive sign be shown for positive values
-(effectively showing a sign for all values except zero)? If so, use \code{TRUE}
-for this option. The default is \code{FALSE}, where only negative numbers will
-display a minus sign. This option is disregarded when using accounting
-notation with \code{accounting = TRUE}.}
-
-\item{incl_space}{An option for whether to include a space between the value
-and the percent sign. The default is to not introduce a space character.}
-
-\item{placement}{The placement of the percent sign. This can be either be
-\code{right} (the default) or \code{left}.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{use_seps}{\emph{Use digit group separators}
+
+\verb{scalar<logical>} --- \emph{default:} \code{TRUE}
+
+An option to use digit group separators. The type of digit group separator
+is set by \code{sep_mark} and overridden if a locale ID is provided to \code{locale}.
+This setting is \code{TRUE} by default.}
+
+\item{accounting}{\emph{Use accounting style}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option to use accounting style for values. Normally, negative values
+will be shown with a minus sign but using accounting style will instead put
+any negative values in parentheses.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the positive sign be shown for positive values (effectively showing
+a sign for all values except zero)? If so, use \code{TRUE} for this option. The
+default is \code{FALSE}, where only negative numbers will display a minus sign.
+This option is disregarded when using accounting notation with
+\code{accounting = TRUE}.}
+
+\item{incl_space}{\emph{Include a space between the value and the \% sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+An option for whether to include a space between the value and the percent
+sign. The default is to not introduce a space character.}
+
+\item{placement}{\emph{Percent sign placement}
+
+\verb{scalar<character>} --- \emph{default:} \code{"right"}
+
+This option governs the placement of the percent sign. This can be either
+be \code{right} (the default) or \code{left}.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_roman.Rd b/man/vec_fmt_roman.Rd
index bc6c9ca48e..492b797aae 100644
--- a/man/vec_fmt_roman.Rd
+++ b/man/vec_fmt_roman.Rd
@@ -12,19 +12,37 @@ vec_fmt_roman(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{case}{Should Roman numerals should be rendered as uppercase (\code{"upper"})
-or lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{case}{\emph{Use uppercase or lowercase letters}
+
+\verb{singl-kw:[upper|lower]} --- \emph{default:} \code{"upper"}
+
+Should Roman numerals should be rendered as uppercase (\code{"upper"}) or
+lowercase (\code{"lower"}) letters? By default, this is set to \code{"upper"}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_scientific.Rd b/man/vec_fmt_scientific.Rd
index e90b15881c..579e27b556 100644
--- a/man/vec_fmt_scientific.Rd
+++ b/man/vec_fmt_scientific.Rd
@@ -20,53 +20,107 @@ vec_fmt_scientific(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
+\item{x}{\emph{The input vector}
 
-\item{decimals}{An option to specify the exact number of decimal places to
-use. The default number of decimal places is \code{2}.}
+\code{vector(numeric|integer)} --- \strong{required}
 
-\item{drop_trailing_zeros}{A logical value that allows for removal of
-trailing zeros (those redundant zeros after the decimal mark).}
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
 
-\item{scale_by}{A value to scale the input. The default is \code{1.0}. All numeric
-values will be multiplied by this value first before undergoing formatting.}
+\item{decimals}{\emph{Number of decimal places}
 
-\item{exp_style}{Style of formatting to use for the scientific notation
-formatting. By default this is \code{"x10n"} but other options include using
-a single letter (e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to
-signal a minimum digit width of one, or \code{"low-ten"} for using a stylized
-\code{"10"} marker.}
+\code{scalar<numeric|integer>(val>=0)} --- \emph{default:} \code{2}
 
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
+This corresponds to the exact number of decimal places to use. A value
+such as \code{2.34} can, for example, be formatted with \code{0} decimal places and
+it would result in \code{"2"}. With \code{4} decimal places, the formatted value
+becomes \code{"2.3400"}. The trailing zeros can be removed with
+\code{drop_trailing_zeros = TRUE}. If you always need \code{decimals = 0}, the
+\code{\link[=fmt_integer]{fmt_integer()}} function should be considered.}
 
-\item{sep_mark}{The mark to use as a separator between groups of digits
-(e.g., using \code{sep_mark = ","} with \code{1000} would result in a formatted value
-of \verb{1,000}).}
+\item{drop_trailing_zeros}{\emph{Drop any trailing zeros}
 
-\item{dec_mark}{The character to use as a decimal mark (e.g., using
-\code{dec_mark = ","} with \code{0.152} would result in a formatted value of
-\verb{0,152}).}
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
 
-\item{force_sign_m, force_sign_n}{Should the plus sign be shown for positive
-values of the mantissa (first component) or the exponent? This would
+A logical value that allows for removal of trailing zeros (those redundant
+zeros after the decimal mark).}
+
+\item{scale_by}{\emph{Scale values by a fixed multiplier}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{1}
+
+All numeric values will be multiplied by the \code{scale_by} value before
+undergoing formatting. Since the \code{default} value is \code{1}, no values will be
+changed unless a different multiplier value is supplied.}
+
+\item{exp_style}{\emph{Style declaration for exponent formatting}
+
+\verb{scalar<character>} --- \emph{default:} \code{"x10n"}
+
+Style of formatting to use for the scientific notation formatting. By
+default this is \code{"x10n"} but other options include using a single letter
+(e.g., \code{"e"}, \code{"E"}, etc.), a letter followed by a \code{"1"} to signal a
+minimum digit width of one, or \code{"low-ten"} for using a stylized \code{"10"}
+marker.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{sep_mark}{\emph{Separator mark for digit grouping}
+
+\verb{scalar<character>} --- \emph{default:} \code{","}
+
+The string to use as a separator between groups of digits. For example,
+using \code{sep_mark = ","} with a value of \code{1000} would result in a formatted
+value of \code{"1,000"}. This argument is ignored if a \code{locale} is supplied
+(i.e., is not \code{NULL}).}
+
+\item{dec_mark}{\emph{Decimal mark}
+
+\verb{scalar<character>} --- \emph{default:} \code{"."}
+
+The string to be used as the decimal mark. For example, using
+\code{dec_mark = ","} with the value \code{0.152} would result in a formatted value
+of \code{"0,152"}). This argument is ignored if a \code{locale} is supplied (i.e., is
+not \code{NULL}).}
+
+\item{force_sign_m, force_sign_n}{\emph{Forcing the display of a positive sign}
+
+\verb{scalar<logical>} --- \emph{default:} \code{FALSE}
+
+Should the plus sign be shown for positive values of the mantissa (first
+component, \code{force_sign_m}) or the exponent (\code{force_sign_n})? This would
 effectively show a sign for all values except zero on either of those
 numeric components of the notation. If so, use \code{TRUE} for either one of
 these options. The default for both is \code{FALSE}, where only negative numbers
 will display a sign.}
 
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_spelled_num.Rd b/man/vec_fmt_spelled_num.Rd
index f6e00a5fad..85fa73dbd0 100644
--- a/man/vec_fmt_spelled_num.Rd
+++ b/man/vec_fmt_spelled_num.Rd
@@ -12,23 +12,42 @@ vec_fmt_spelled_num(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/vec_fmt_time.Rd b/man/vec_fmt_time.Rd
index 530ee717cd..bae9410b97 100644
--- a/man/vec_fmt_time.Rd
+++ b/man/vec_fmt_time.Rd
@@ -13,27 +13,51 @@ vec_fmt_time(
 )
 }
 \arguments{
-\item{x}{A numeric vector.}
-
-\item{time_style}{The time style to use. By default this is \code{"iso"} which
-corresponds to how times are formatted within ISO 8601 datetime values. The
-other time styles can be viewed using \code{\link[=info_time_style]{info_time_style()}}.}
-
-\item{pattern}{A formatting pattern that allows for decoration of the
-formatted value. The value itself is represented by \code{{x}} and all other
-characters are taken to be string literals.}
-
-\item{locale}{An optional locale identifier that can be used for formatting
-the value according the locale's rules. Examples include \code{"en"} for English
-(United States) and \code{"fr"} for French (France). The use of a locale ID will
-override any locale-specific values provided. We can use the
-\code{\link[=info_locales]{info_locales()}} function as a useful reference for all of the locales that
-are supported.}
-
-\item{output}{The output style of the resulting character vector. This can
-either be \code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"},
-or \code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the
-\code{"auto"} option will choose the correct \code{output} value}
+\item{x}{\emph{The input vector}
+
+\code{vector(numeric|integer)} --- \strong{required}
+
+This is the input vector that will undergo transformation to a character
+vector of the same length. Values within the vector will be formatted.}
+
+\item{time_style}{\emph{Predefined style for times}
+
+\verb{scalar<character>|scalar<numeric|integer>(1<=val<=25)} --- \emph{default:} \code{"iso"}
+
+The time style to use. By default this is the short name \code{"iso"} which
+corresponds to how times are formatted within ISO 8601 datetime values.
+There are 25 time styles in total and their short names can be viewed using
+\code{\link[=info_time_style]{info_time_style()}}.}
+
+\item{pattern}{\emph{Specification of the formatting pattern}
+
+\verb{scalar<character>} --- \emph{default:} \code{"{x}"}
+
+A formatting pattern that allows for decoration of the formatted value. The
+formatted value is represented by the \code{{x}} (which can be used multiple
+times, if needed) and all other characters will be interpreted as string
+literals.}
+
+\item{locale}{\emph{Locale identifier}
+
+\verb{scalar<character>} --- \emph{default:} \code{NULL} (\code{optional})
+
+An optional locale identifier that can be used for formatting values
+according the locale's rules. Examples include \code{"en"} for English (United
+States) and \code{"fr"} for French (France). We can use the \code{\link[=info_locales]{info_locales()}}
+function as a useful reference for all of the locales that are supported. A
+locale ID can be also set in the initial \code{\link[=gt]{gt()}} function call (where it
+would be used automatically by any function with a \code{locale} argument) but a
+\code{locale} value provided here will override that global locale.}
+
+\item{output}{\emph{Output format}
+
+\verb{singl-kw:[auto|plain|html|latex|rtf|word]} --- \emph{default:} \code{"auto"}
+
+The output style of the resulting character vector. This can either be
+\code{"auto"} (the default), \code{"plain"}, \code{"html"}, \code{"latex"}, \code{"rtf"}, or
+\code{"word"}. In \strong{knitr} rendering (i.e., Quarto or R Markdown), the \code{"auto"}
+option will choose the correct \code{output} value}
 }
 \value{
 A character vector.
diff --git a/man/web_image.Rd b/man/web_image.Rd
index 9430c85a12..93286caa26 100644
--- a/man/web_image.Rd
+++ b/man/web_image.Rd
@@ -7,9 +7,18 @@
 web_image(url, height = 30)
 }
 \arguments{
-\item{url}{A url that resolves to an image file.}
+\item{url}{\emph{An image URL}
 
-\item{height}{The absolute height (px) of the image in the table cell.}
+\verb{scalar<character>} --- \strong{required}
+
+A url that resolves to an image file.}
+
+\item{height}{\emph{Height of image}
+
+\verb{scalar<numeric|integer>} --- \emph{default:} \code{30}
+
+The absolute height of the image in the table cell (in \code{"px"} units). By
+default, this is set to \code{"30px"}.}
 }
 \value{
 A character object with an HTML fragment that can be placed inside of
diff --git a/pkgdown/extra.css b/pkgdown/extra.css
new file mode 100644
index 0000000000..9467b2537f
--- /dev/null
+++ b/pkgdown/extra.css
@@ -0,0 +1,8 @@
+dt {
+  font-family: monospace;
+  border-top-style: dotted;
+  border-top-width: 2px;
+  border-top-color: lightgray;
+  margin-bottom: 5px;
+  padding-top: 5px;
+}