diff --git a/doc/adapting-existing.xml b/doc/adapting-existing.xml
index b8295f04..28cb26fe 100644
--- a/doc/adapting-existing.xml
+++ b/doc/adapting-existing.xml
@@ -177,9 +177,10 @@ d /run/media 0755 root root -
     </para>
     <para>
       The solution chosen for the <ulink
-      url="https://wiki.gnome.org/GnomeOSTree">gnome-ostree</ulink>
-      operating system is to create <filename>/lib/passwd</filename>,
-      and to include a NSS module <ulink
+      url="https://live.gnome.org/Projects/GnomeContinuous">gnome-continuous</ulink>
+      operating system is to create
+      <filename>/usr/lib/passwd</filename>, and to include a NSS
+      module <ulink
       url="https://github.com/aperezdc/nss-altfiles">nss-altfiles</ulink>
       which instructs glibc to read from it.  Then, the build system places
       all system users there, freeing up <filename>/etc/passwd</filename>
diff --git a/doc/atomic-upgrades.xml b/doc/atomic-upgrades.xml
index 1a1be839..33f98f20 100644
--- a/doc/atomic-upgrades.xml
+++ b/doc/atomic-upgrades.xml
@@ -40,9 +40,9 @@
     <para>
       To begin a simple upgrade, OSTree fetches the contents of the
       ref from the remote server.  Suppose we're tracking a ref named
-      <literal>gnome-ostree/buildmaster/x86_64-runtime</literal>.
+      <literal>exampleos/buildmaster/x86_64-runtime</literal>.
       OSTree fetches the URL
-      <literal>http://<replaceable>example.com</replaceable>/repo/refs/gnome-ostree/buildmaster/x86_64-runtime</literal>,
+      <literal>http://<replaceable>example.com</replaceable>/repo/refs/exampleos/buildmaster/x86_64-runtime</literal>,
       which contains a SHA256 checksum.  This determines the tree to
       deploy, and <filename class='directory'>/etc</filename> will be
       merged from currently booted tree.