diff --git a/doc/backends.txt b/doc/backends.txt
index ffe2d5e88..b78397913 100644
--- a/doc/backends.txt
+++ b/doc/backends.txt
@@ -335,18 +335,18 @@ Nimcache and C like targets
 
 The C like backends will place their temporary ``.c``, ``.cpp`` or ``.m`` files
 in the ``nimcache`` directory. The naming of these files follows the pattern
-``babelPackageName_`` + ``nimSource``:
+``nimblePackageName_`` + ``nimSource``:
 
-* Filenames for modules imported from `Babel packages
-  <https://github.com/nim-code/babel>`_ will end up with
-  ``babelPackageName_module.c``. For example, if you import the
-  ``argument_parser`` module from the same name Babel package you
+* Filenames for modules imported from `nimble packages
+  <https://github.com/nim-code/nimble>`_ will end up with
+  ``nimblePackageName_module.c``. For example, if you import the
+  ``argument_parser`` module from the same name nimble package you
   will end up with a ``argument_parser_argument_parser.c`` file
-  under ``nimcache``.  The name of the Babel package comes from the
-  ``proj.babel`` file, the actual contents are not read by the
+  under ``nimcache``.  The name of the nimble package comes from the
+  ``proj.nimble`` file, the actual contents are not read by the
   compiler.
 
-* Filenames for non babel packages (like your project) will be
+* Filenames for non nimble packages (like your project) will be
   renamed from ``.nim`` to have the extension of your target backend
   (from now on ``.c`` for these examples), but otherwise nothing
   else will change. This will quickly break if your project consists
@@ -360,13 +360,13 @@ in the ``nimcache`` directory. The naming of these files follows the pattern
   module <system.html>`_ is always imported automatically. Same for
   the `hashes module <hashes.html>`_ which will be named
   ``stdlib_hashes.c``. The ``stdlib_`` prefix comes from the *fake*
-  ``lib/stdlib.babel`` file.
+  ``lib/stdlib.nimble`` file.
 
-To find the name of a Babel package the compiler searches for a ``*.babel``
+To find the name of a nimble package the compiler searches for a ``*.nimble``
 file in the parent directory hierarchy of whatever module you are compiling.
-Even if you are in a subdirectory of your project, a parent ``*.babel`` file
+Even if you are in a subdirectory of your project, a parent ``*.nimble`` file
 will influence the naming of the nimcache name. This means that on Unix systems
-creating the file ``~/foo.babel`` will automatically prefix all nimcache files
+creating the file ``~/foo.nimble`` will automatically prefix all nimcache files
 not part of another package with the string ``foo_``.
 
 
diff --git a/doc/intern.txt b/doc/intern.txt
index 26dd49444..d9da863f5 100644
--- a/doc/intern.txt
+++ b/doc/intern.txt
@@ -136,7 +136,7 @@ are also lots of procs that aid in debugging:
   debug(someType)
   echo symbol.name.s
   debug(symbol)
-  # pretty prints the nimrod ast, but annotates symbol IDs:
+  # pretty prints the Nim ast, but annotates symbol IDs:
   echo renderTree(someNode, {renderIds})
   if n.info ?? "temp.nim":
     # only output when it comes from "temp.nim"
diff --git a/doc/lib.txt b/doc/lib.txt
index 45d9dfd2a..57107b0db 100644
--- a/doc/lib.txt
+++ b/doc/lib.txt
@@ -586,7 +586,7 @@ Nimble
 
 Nimble is a package manager for the Nim programming language.
 For instructions on how to install Nimble packages see
-`its README <https://github.com/nim-lang/babel#readme>`_.
+`its README <https://github.com/nim-lang/nimble#readme>`_.
 
 Official packages
 -----------------