diff --git a/R/browser.R b/R/browser.R
index c6a793c..a32a1c9 100644
--- a/R/browser.R
+++ b/R/browser.R
@@ -2,10 +2,12 @@ globals <- new.env()
 
 #' Browser base class
 #'
+#' @description
 #' Base class for browsers like Chrome, Chromium, etc. Defines the interface
 #' used by various browser implementations. It can represent a local browser
 #' process or one running remotely.
 #'
+#' @details
 #' The \code{initialize()} method of an implementation should set private$host
 #' and private$port. If the process is local, the \code{initialize()} method
 #' should also set private$process.
diff --git a/R/chrome.R b/R/chrome.R
index f7a82fa..b7643a2 100644
--- a/R/chrome.R
+++ b/R/chrome.R
@@ -1,5 +1,6 @@
 #' Local Chrome process
 #'
+#' @description
 #' This is a subclass of [`Browser`] that represents a local browser. It extends
 #' the [`Browser`] class with a [`processx::process`] object, which represents
 #' the browser's system process.
@@ -231,7 +232,8 @@ launch_chrome_impl <- function(path, args, port) {
 
 #' Remote Chrome process
 #'
-#'
+#' @description
+#' Remote Chrome process
 #'
 #' @export
 ChromeRemote <- R6Class("ChromeRemote",
diff --git a/R/chromote.R b/R/chromote.R
index 76cb060..6f6633f 100644
--- a/R/chromote.R
+++ b/R/chromote.R
@@ -1,7 +1,6 @@
 #' Chromote class
 #'
-#' This class represents the browser as a whole.
-#'
+#' @description
 #' A `Chromote` object represents the browser as a whole, and it can have
 #' multiple _targets_, which each represent a browser tab. In the Chrome
 #' DevTools Protocol, each target can have one or more debugging _sessions_ to
diff --git a/man/Browser.Rd b/man/Browser.Rd
index 2354fbb..1f6338c 100644
--- a/man/Browser.Rd
+++ b/man/Browser.Rd
@@ -4,15 +4,11 @@
 \alias{Browser}
 \title{Browser base class}
 \description{
-Browser base class
-
-Browser base class
-}
-\details{
 Base class for browsers like Chrome, Chromium, etc. Defines the interface
 used by various browser implementations. It can represent a local browser
 process or one running remotely.
-
+}
+\details{
 The \code{initialize()} method of an implementation should set private$host
 and private$port. If the process is local, the \code{initialize()} method
 should also set private$process.
diff --git a/man/Chrome.Rd b/man/Chrome.Rd
index dc312b4..f3a5180 100644
--- a/man/Chrome.Rd
+++ b/man/Chrome.Rd
@@ -4,11 +4,6 @@
 \alias{Chrome}
 \title{Local Chrome process}
 \description{
-Local Chrome process
-
-Local Chrome process
-}
-\details{
 This is a subclass of \code{\link{Browser}} that represents a local browser. It extends
 the \code{\link{Browser}} class with a \code{\link[processx:process]{processx::process}} object, which represents
 the browser's system process.
diff --git a/man/ChromeRemote.Rd b/man/ChromeRemote.Rd
index 683ca01..0d5cc49 100644
--- a/man/ChromeRemote.Rd
+++ b/man/ChromeRemote.Rd
@@ -4,8 +4,6 @@
 \alias{ChromeRemote}
 \title{Remote Chrome process}
 \description{
-Remote Chrome process
-
 Remote Chrome process
 }
 \section{Super class}{
diff --git a/man/Chromote.Rd b/man/Chromote.Rd
index 9594cdc..861be18 100644
--- a/man/Chromote.Rd
+++ b/man/Chromote.Rd
@@ -4,13 +4,6 @@
 \alias{Chromote}
 \title{Chromote class}
 \description{
-Chromote class
-
-Chromote class
-}
-\details{
-This class represents the browser as a whole.
-
 A \code{Chromote} object represents the browser as a whole, and it can have
 multiple \emph{targets}, which each represent a browser tab. In the Chrome
 DevTools Protocol, each target can have one or more debugging \emph{sessions} to