diff --git a/pkgs/racket-pkgs/racket-doc/pkg/scribblings/strip.scrbl b/pkgs/racket-pkgs/racket-doc/pkg/scribblings/strip.scrbl
index 0db83a7180..dbcd82cbe7 100644
--- a/pkgs/racket-pkgs/racket-doc/pkg/scribblings/strip.scrbl
+++ b/pkgs/racket-pkgs/racket-doc/pkg/scribblings/strip.scrbl
@@ -32,7 +32,11 @@ A package is not specifically tagged as a @tech{source package},
 @tech{binary package}, or @tech{built package}. The different kinds of
 packages are just conventions based on the content of the package. All
 forms of packages can be mixed in an installation, and a package can
-be updated from any form to any other form.
+be updated from any form to any other form. Furthermore,
+@exec{raco pkg install} and @exec{raco pkg update} support
+@DFlag{source} and @DFlag{binary} flags, which can be used to convert
+a @tech{built package} to a @tech{source package} or @tech{binary
+package} on installation.
 
 Programmers normally supply only @tech{source packages}, while a
 package catalog service may convert each source package to a
diff --git a/racket/collects/pkg/main.rkt b/racket/collects/pkg/main.rkt
index f0f62cee06..d52eb7844e 100644
--- a/racket/collects/pkg/main.rkt
+++ b/racket/collects/pkg/main.rkt
@@ -523,7 +523,7 @@
    ([#:bool link () ("Link a directory package source in place (default for a directory)")]
     [#:bool static-link () ("Link in place, promising collections do not change")]
     [#:bool copy () ("Treat directory sources the same as other sources")]
-    [#:bool source () ("Strip package's built elements before installing; implies --copy")]
+    [#:bool source () ("Strip packages' built elements before installing; implies --copy")]
     [#:bool binary () ("Strip packages' source elements before installing; implies --copy")])
    #:install-copy-defns
    [(define link-dirs? (not (or copy source binary)))