diff --git a/source/reference/built-in-roles.txt b/source/reference/built-in-roles.txt
index a1b37fdf93f..054d8d06ffe 100644
--- a/source/reference/built-in-roles.txt
+++ b/source/reference/built-in-roles.txt
@@ -558,7 +558,7 @@ Cluster Administration Roles
    .. versionchanged:: 4.4
    
       Starting in version 4.4, :authrole:`hostManager` no longer
-      provides the :authrole:`cpuProfiler` privilege action on the
+      provides the :authaction:`cpuProfiler` privilege action on the
       cluster.
 
    On *all* databases in the cluster, provides the following actions:
diff --git a/source/reference/command/compact.txt b/source/reference/command/compact.txt
index 1650aa546f3..8c19da91b7f 100644
--- a/source/reference/command/compact.txt
+++ b/source/reference/command/compact.txt
@@ -91,17 +91,17 @@ Definition
 -------------------------------
 
 For clusters enforcing :ref:`authentication <authentication>`,
-you must authenticate as a user with the :authrole:`compact` privilege
+you must authenticate as a user with the :authaction:`compact` privilege
 action on the target collection. The :authrole:`dbAdmin` role provides 
 the required privileges for running :dbcommand:`compact` against
 non-system collections. 
 
 For :ref:`system collections <metadata-system-collections>`, create a 
-custom role that grants the :authrole:`compact` action on the system 
+custom role that grants the :authaction:`compact` action on the system 
 collection. You can then grant that role to a new or existing user and 
 authenticate as that user to perform the :dbcommand:`compact` command. 
 For example, the following operations create a custom role that grants 
-the :authrole:`compact` action against specified database and
+the :authaction:`compact` action against specified database and
 collection:
 
 .. code-block:: javascript