diff --git a/DESCRIPTION b/DESCRIPTION
index 64cf923..64dad2f 100644
--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -10,10 +10,10 @@ Authors@R:
       person('Luis', 'Morís Fernández', email = 'luis.moris.fernandez.ext@boehringer-ingelheim.com', role = c('aut')),
       person('Jessica', 'Knizia', email = 'jessica.knizia@boehringer-ingelheim.com', role = c('ctb'))
     )
-Description: DaVinci’s dv.listings module displays a data listing of different dataset domains in tabular form. 
+Description: DaVinci’s dv.listings package provides modules to display different dataset domains as listings. 
     Users can select the dataset to be shown, and specify which columns of the dataset should be displayed.
     The displayed columns can be sorted and filtered.
-    Moreover, the listing can be filtered to show only entries containing a keyword entered by the user.
+    Moreover, the listing can be filtered to show only entries containing a keyword specified by the user.
     The module is not limited to usage of one data source, most notably, it can handle data from ADaM or SDTM. 
 License: Apache License (>= 2)
 Encoding: UTF-8
@@ -41,7 +41,7 @@ Imports:
     shinyWidgets (>= 0.8.0),
     tibble (>= 3.2.1),
     dv.manager (>= 2.0.0-17)
-RoxygenNote: 7.3.0
+RoxygenNote: 7.3.1
 Roxygen: list(markdown = TRUE)
 Remotes: boehringer-ingelheim/dv.manager@main
 VignetteBuilder: knitr
diff --git a/NAMESPACE b/NAMESPACE
index 90287bb..cbcb544 100644
--- a/NAMESPACE
+++ b/NAMESPACE
@@ -4,8 +4,6 @@ export("%>%")
 export(convert_data)
 export(listings_UI)
 export(listings_server)
-export(mock_listings_mm)
-export(mock_simple_listing_mm)
 export(mod_listings)
 import(shiny)
 importFrom(magrittr,"%>%")
diff --git a/NEWS.md b/NEWS.md
index 9522275..a4c29a6 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,6 +1,6 @@
 # dv.listings 3.1.0
 
-package was renamed to dv.listings
+Package was renamed to dv.listings.
 
 # dv.table 3.0.1
 
diff --git a/R/helpers.R b/R/helpers.R
index 2962f44..d9ebbb1 100644
--- a/R/helpers.R
+++ b/R/helpers.R
@@ -8,8 +8,6 @@
 #' "No label" for missing labels.
 #'
 #' @keywords internal
-#'
-
 get_labels <- function(dataset) {
   # Catch special cases (e.g. when global filter returns empty dataset)
   return_null <- any(length(dataset) == 0, is.null(dataset))
@@ -55,7 +53,6 @@ get_labels <- function(dataset) {
 #' @return Character vector of the type `<name> [<label>]`. Adds "No label" as placeholder for missing labels.
 #'
 #' @keywords internal
-#'
 generate_choices <- function(dataset) {
   # No checkmate checks since it is catched in get_labels()
 
@@ -79,7 +76,7 @@ generate_choices <- function(dataset) {
 #'   datasets.
 #' @param dataset `[list(data.frame)]`
 #'
-#' A list of data.framish dataset(s) that will be shown in tabular format.
+#' A list of data.framish dataset(s) that will be shown as listings.
 #'
 #' @return Named list of character vectors which Contain the names of columns to be displayed at module launch for
 #'   every dataset. List entries are named according to the \code{dataset} names.
@@ -135,7 +132,6 @@ fill_default_vars <- function(default_vars, dataset) {
 #'   vector of column names created by combining the variable names with their labels.
 #'   \code{row_names} is a character vector containing the number of the corresponding row.
 #' @keywords internal
-#'
 set_data <- function(base_data, selector) {
   # Check validity of parameters
   checkmate::assert(
@@ -201,7 +197,7 @@ set_labels <- function(dataset, labels) {
 #' Converts data types of data.frame columns to logical, integer, numeric, complex, character or factor as appropriate.
 #' Re-assigns column labels after converting data type.
 #'
-#' @param dataset  `[data.frame]`
+#' @param dataset `[data.frame]`
 #'
 #' Single data.frame to convert the column data types
 #'
diff --git a/R/mock_listings.R b/R/mock_listings.R
index b5c8039..89df723 100644
--- a/R/mock_listings.R
+++ b/R/mock_listings.R
@@ -7,7 +7,6 @@
 #'
 #' @keywords internal
 #' @family mock apps
-#'
 mock_listings_app <- function(mode = "single") {
   stopifnot(mode %in% c("single", "multi"))
 
@@ -57,9 +56,8 @@ mock_listings_app <- function(mode = "single") {
 #' \code{mock_listings_mm} launches a mock app for the dv.listings shiny module by means of
 #' the module manager (dv.manager).
 #'
+#' @keywords internal
 #' @family mock apps
-#' @export
-#'
 mock_listings_mm <- function() {
   data <- list()
   data[["adsl"]] <- convert_data(pharmaverseadam::adsl)
diff --git a/R/mock_simple_listing.R b/R/mock_simple_listing.R
index 682942b..b5b8a26 100644
--- a/R/mock_simple_listing.R
+++ b/R/mock_simple_listing.R
@@ -16,13 +16,12 @@ mock_simple_listing_UI <- function(id) { # nolint
   )
 }
 
-#'
 mock_simple_listing_server <- function(input, output, session) {
   simple_listing_server("listing", dataset = reactive(datasets::mtcars))
 }
 
 #' Mock function for simple listing
-#' @export
+#' @keywords internal
 mock_simple_listing_mm <- function() {
   stopifnot(
     requireNamespace("dv.manager", quietly = TRUE),
diff --git a/R/mod_listings.R b/R/mod_listings.R
index 572751e..df751dd 100644
--- a/R/mod_listings.R
+++ b/R/mod_listings.R
@@ -71,11 +71,10 @@ listings_UI <- function(module_id) { # nolint
 #' @param pagination `[logical(1) | NULL]` Either a boolean indicating if pagination should be activated, or
 #' NULL for which pagination will be activated for large datasets (nrows > 1000) automatically.
 #'
-#' @param intended_use_label `[character(1) | NULL]` Either a character indicating the intended use for the download, or
-#' NULL. If a label is provided it will be shown before the download and will also be included in the downloaded file.
+#' @param intended_use_label `[character(1) | NULL]` Either a string indicating the intended use for export, or
+#' NULL. The provided label will be displayed prior to the download and will also be included in the exported file.
 #'
 #' @export
-#'
 listings_server <- function(module_id,
                             dataset_list,
                             default_vars = NULL,
@@ -265,15 +264,15 @@ listings_server <- function(module_id,
 }
 
 
-#' Data listings function for module manager
+#' Data listings module for DaVinci's module manager
 #'
 #' @description
 #'
-#' This module will present the dataset in a tabular form using the DT package.
+#' This module will present the dataset as listing using the DT package.
 #' @param dataset_names `[character(1+)]`
 #'
 #' Name(s) of the dataset(s) that will be displayed.
-#' Can not be used together with the parameter \code{dataset_disp}.
+#' Cannot be used together with the parameter \code{dataset_disp}.
 #'
 #' @inheritParams listings_server
 #'
@@ -330,7 +329,6 @@ listings_server <- function(module_id,
 #'   module_list = module_list,
 #'   filter_data = "adsl"
 #' )
-#'
 mod_listings <- function(
     module_id,
     dataset_names,
@@ -347,7 +345,6 @@ mod_listings <- function(
   }
 
   # skip assertions/checks for module_id and default_vars since they will be checked directly in listings_server()
-
   if (!missing(dataset_disp)) {
     checkmate::assert(
       checkmate::check_class(dataset_disp, "mm_dispatcher"),
diff --git a/R/mod_simple_listing.R b/R/mod_simple_listing.R
index 2f6d527..a6ed04b 100644
--- a/R/mod_simple_listing.R
+++ b/R/mod_simple_listing.R
@@ -8,8 +8,6 @@
 #' @import shiny
 #'
 #' @name simple_listing
-#'
-
 NULL
 
 #' @describeIn simple_listing UI
@@ -24,8 +22,6 @@ simple_listing_UI <- function(module_id) { # nolint
 #' @describeIn simple_listing server
 #'
 #' @param dataset a data.framish dataset that will be shown as a table
-#'
-#'
 simple_listing_server <- function(module_id, dataset) {
   module <- function(input, output, session) {
     output$table <- DT::renderDataTable({
@@ -42,9 +38,7 @@ utils::globalVariables("filtered_datasets")
 #' @param dataset_disp An mm_dispatch object.
 #' @template module_id-arg
 #'
-#'
 #' @family data_table
-
 mod_simple_listing <- function(dataset_disp, module_id) {
   mod <- list(
     ui = simple_listing_UI,
diff --git a/README.md b/README.md
index 1ea642f..c620ba5 100644
--- a/README.md
+++ b/README.md
@@ -1,40 +1,41 @@
 
 # dv.listings
 
-DaVinci's *dv.listings* module displays arbitrary datasets as listings. 
+The listings module from DaVinci's {dv.listings} package displays arbitrary datasets as listings. 
 Users can select the dataset to be shown, and specify
 which columns of the dataset should be displayed as well as their order.
 The displayed columns can be sorted and filtered. Moreover, the
-table can be filtered to show only entries containing a keyword entered by the user. 
+listing can be filtered to show only entries containing a keyword specified by the user. 
 The module is not limited to usage of one data source,
 most notably, it can handle data from ADaM or SDTM.
 
 <img src="man/figures/table_main_view.PNG" width="100%" />
 
-The module is prepared to be used in combination with *dv.manager* and
+The module is prepared to be used in combination with DaVinci's {dv.manager} package and
 supports its bookmarking functionality.
 
 ## Installation
 
-Feel free to copy the following code chunk to install the latest version of *dv.listings*.
+Feel free to copy the following code chunk to install the latest version of {dv.listings}.
 
 ``` r
 if (!require("remotes")) install.packages("remotes")
 remotes::install_github("Boehringer-Ingelheim/dv.listings")
 ```
 
-Since the *dv.listings* module is intended to be used within an application
-created by means of DaVinci’s *dv.manager* package, make sure that you
-have installed *dv.manager* with a version number equally to or higher than 2.1.0
+Since the listings module is intended to be used within an application
+created by means of DaVinci's module manager, make sure that you
+have installed {dv.manager} with a version number equally to or higher than 2.1.0.
 
 ## Data requirements
 
-As stated above, *dv.listings* can display data from various data sources,
-such as (but not limited to) SDTM and ADaM. However, in order for the
-column filters to work, columns need to be converted to appropriate
-types, e.g. categorial data should be stored as factors, numbers as
-numeric, etc. The easiest way to convert the data is by using
-`convert_data()` which comes along the package. An example can be found
+As stated above, the listings module can display data from various data sources.
+However, for the column filters to function correctly, 
+columns need to be converted to the appropriate data
+types, e.g., categorical data should be stored as factor, numbers as
+numeric, etc. To simplify data conversion, 
+the package provides a convenient function called
+`convert_data()`. An example demonstrating the usage of this function can be found
 in the section below.
 
 Note that `dv.listings` drops row names. In case your dataset is equipped
@@ -49,19 +50,18 @@ attributes(my_data$index)$label <- "Former row names"
 
 ## Example
 
-To define an app containing *dv.listings* using *dv.manager*, you need to
+To define an app based on {dv.listings} and {dv.manager}, you need to
 
 1.  load data,
-2.  make sure that the provided data comply with the requirements of
-    *dv.listings*,
-3.  define a list of modules,
-4.  and launch the app via `run_app()` from *dv.manager*.
+2.  make sure that the provided data comply with the requirements of the listings module,
+3.  define a list of modules that contains the listings module,
+4.  and launch the app via `run_app()` from {dv.manager}.
 
 The following example contains the listed steps. For data protection
-purposes, the example uses dummy data from the *pharmaverseadam* package.
+purposes, the example uses dummy data from {pharmaverseadam}.
 
 ``` r
-library(dv.listing)
+library(dv.listings)
 
 # 1. Create a data list with example data
 data_list <- list(
@@ -105,10 +105,10 @@ dv.manager::run_app(
 ```
 ## Export functionality 
 
-The *dv.listings* module allows users to export listings. Users have the option to either download the currently displayed listing or all available listings.
+The listings module allows users to export listings. Users have the option to either download only the currently displayed listing or all available listings.
 
-For downloading only the currently active listing, the listing will be saved as it is displayed, either in .xlsx or .pdf format. In case any filters have been applied, the downloaded file will reflect this and only include the filtered data.
+To download the currently active listing, it will be saved exactly as it appears on the screen, either in .xlsx or .pdf format. In case any filters have been applied, the downloaded file will reflect these and only include the filtered data.
 
-For users who wish to download all listings, the module allows saving in .xlsx format exclusively. This process disregards any local filters, and each listing is saved in a separate worksheet within the file 
+For users who wish to download all listings, the module allows saving in .xlsx format exclusively. This process disregards any local filters, and each listing is saved in a separate worksheet within the file. 
 
 Please be aware that the PDF download feature is implemented using an RMarkdown file that is rendered into a PDF through LaTeX. As such, it is important to note that a LaTeX installation, along with the necessary packages, is required to use this feature.
diff --git a/_pkgdown.yml b/_pkgdown.yml
index 26c2475..afc77ed 100644
--- a/_pkgdown.yml
+++ b/_pkgdown.yml
@@ -11,16 +11,12 @@ home:
     href: https://github.com/Boehringer-Ingelheim/dv.listings
 
 reference:
-- title: "Module usage"
+- title: "Modules and utils"
 - contents:
   - mod_listings
-  - mock_listings_mm
   - convert_data
 - title: "For developers"
 - contents:
-  - simple_listing_UI
-  - simple_listing_server
-  - mod_simple_listing
   - listings_UI
   - listings_server
-  - mock_simple_listing_mm
+  - mod_simple_listing
diff --git a/man/fill_default_vars.Rd b/man/fill_default_vars.Rd
index 2218627..28487f2 100644
--- a/man/fill_default_vars.Rd
+++ b/man/fill_default_vars.Rd
@@ -15,7 +15,7 @@ datasets.}
 
 \item{dataset}{\verb{[list(data.frame)]}
 
-A list of data.framish dataset(s) that will be shown in tabular format.}
+A list of data.framish dataset(s) that will be shown as listings.}
 }
 \value{
 Named list of character vectors which Contain the names of columns to be displayed at module launch for
diff --git a/man/listings_UI.Rd b/man/listings_UI.Rd
index 4b0db89..242c86b 100644
--- a/man/listings_UI.Rd
+++ b/man/listings_UI.Rd
@@ -38,8 +38,8 @@ Usually obtained from module manager.}
 \item{pagination}{\verb{[logical(1) | NULL]} Either a boolean indicating if pagination should be activated, or
 NULL for which pagination will be activated for large datasets (nrows > 1000) automatically.}
 
-\item{intended_use_label}{\verb{[character(1) | NULL]} Either a character indicating the intended use for the download, or
-NULL. If a label is provided it will be shown before the download and will also be included in the downloaded file.}
+\item{intended_use_label}{\verb{[character(1) | NULL]} Either a string indicating the intended use for export, or
+NULL. The provided label will be displayed prior to the download and will also be included in the exported file.}
 }
 \description{
 This module displays a given dataset as listing. It allows switching between datasets if it receives
diff --git a/man/mock_listings_mm.Rd b/man/mock_listings_mm.Rd
index c9b0769..268c1f1 100644
--- a/man/mock_listings_mm.Rd
+++ b/man/mock_listings_mm.Rd
@@ -15,3 +15,4 @@ Other mock apps:
 \code{\link{mock_listings_app}()}
 }
 \concept{mock apps}
+\keyword{internal}
diff --git a/man/mock_simple_listing_mm.Rd b/man/mock_simple_listing_mm.Rd
index 9697144..84542df 100644
--- a/man/mock_simple_listing_mm.Rd
+++ b/man/mock_simple_listing_mm.Rd
@@ -9,3 +9,4 @@ mock_simple_listing_mm()
 \description{
 Mock function for simple listing
 }
+\keyword{internal}
diff --git a/man/mod_listings.Rd b/man/mod_listings.Rd
index 49262c9..1096f60 100644
--- a/man/mod_listings.Rd
+++ b/man/mod_listings.Rd
@@ -2,7 +2,7 @@
 % Please edit documentation in R/mod_listings.R
 \name{mod_listings}
 \alias{mod_listings}
-\title{Data listings function for module manager}
+\title{Data listings module for DaVinci's module manager}
 \usage{
 mod_listings(
   module_id,
@@ -20,7 +20,7 @@ mod_listings(
 \item{dataset_names}{\verb{[character(1+)]}
 
 Name(s) of the dataset(s) that will be displayed.
-Can not be used together with the parameter \code{dataset_disp}.}
+Cannot be used together with the parameter \code{dataset_disp}.}
 
 \item{default_vars}{\verb{[list(characters(1+)) | NULL]}
 
@@ -31,8 +31,8 @@ dataset.}
 \item{pagination}{\verb{[logical(1) | NULL]} Either a boolean indicating if pagination should be activated, or
 NULL for which pagination will be activated for large datasets (nrows > 1000) automatically.}
 
-\item{intended_use_label}{\verb{[character(1) | NULL]} Either a character indicating the intended use for the download, or
-NULL. If a label is provided it will be shown before the download and will also be included in the downloaded file.}
+\item{intended_use_label}{\verb{[character(1) | NULL]} Either a string indicating the intended use for export, or
+NULL. The provided label will be displayed prior to the download and will also be included in the exported file.}
 
 \item{dataset_disp}{\verb{[dv.manager::mm_dispatch()]}
 
@@ -40,7 +40,7 @@ This is only for advanced usage. An mm_dispatch object.
 Can not be used together with the parameter \code{dataset_names}.}
 }
 \description{
-This module will present the dataset in a tabular form using the DT package.
+This module will present the dataset as listing using the DT package.
 }
 \examples{
 \dontshow{if (interactive()) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf}
diff --git a/tests/testthat/apps/simple_listing/app.R b/tests/testthat/apps/simple_listing/app.R
index 8e1da92..fdaa543 100644
--- a/tests/testthat/apps/simple_listing/app.R
+++ b/tests/testthat/apps/simple_listing/app.R
@@ -11,4 +11,4 @@ if (use_load_all) {
   devtools::load_all(pkg_path, quiet = TRUE)
 }
 
-dv.listings::mock_simple_listing_mm()
+dv.listings:::mock_simple_listing_mm()
diff --git a/vignettes/disp.Rmd b/vignettes/disp.Rmd
index 957a989..4788b5e 100644
--- a/vignettes/disp.Rmd
+++ b/vignettes/disp.Rmd
@@ -1,8 +1,8 @@
 ---
-title: "Usage of dv.manager dispatchers"
+title: "Usage of {dv.manager} dispatchers"
 output: rmarkdown::html_vignette
 vignette: >
-  %\VignetteIndexEntry{Usage of dv.manager dispatchers}
+  %\VignetteIndexEntry{Usage of {dv.manager} dispatchers}
   %\VignetteEngine{knitr::rmarkdown}
   %\VignetteEncoding{UTF-8}
 ---
@@ -15,13 +15,13 @@ knitr::opts_chunk$set(
 )
 ```
 
-## How to set up a *dv.listings* module using dispatchers
+## How to set up a listings module using dispatchers
 
-**Dispatchers** are helper functions that allow accessing data and utility functions inside module manager in a dynamic way. Refer to `?dv.manager::mm_dispatch` for more information about their functionalities. The boxes below show two examples on how they can be used to set up a *dv.listings* module. Note that it is not possible to use both arguments, `dataset_names` and `dataset_disp`, at the same time in a `mod_listings()` call.
+**Dispatchers** are helper functions that allow accessing data and utility functions inside module manager in a dynamic way. Refer to `?dv.manager::mm_dispatch` for more information about their functionalities. The boxes below show two examples on how they can be used to set up a listings module. Note that it is not possible to use both arguments, `dataset_names` and `dataset_disp`, at the same time in a `mod_listings()` call.
 
 ### a. Filtered data
 
-This code piece produces essentially the same app behavior as using the `dataset_names` argument. That is, any selection made by the user in the global filter menu affects the module display. 
+This code chunk produces essentially the same app behavior as using the `dataset_names` argument. That is, any selection made by the user in the global filter menu affects the module display. 
 
 ```{r filtered, eval = FALSE}
 dv.listings::mod_listings(
@@ -36,7 +36,7 @@ dv.listings::mod_listings(
 
 ### b. Unfiltered data
 
-In case it is undesirable that global filter settings affect the listings displayed in a *dv.listings* module, it is possible to define the dispatcher such that it delivers always unfiltered data. This means that [any global filter will be ignored]{.ul}!
+In case it is undesirable that global filter settings affect the listings displayed in a listings module, it is possible to define the dispatcher such that it delivers always unfiltered data. This means that [any global filter will be ignored]{.ul}!
 
 ```{r unfiltered, eval = FALSE}
 dv.listings::mod_listings(