diff --git a/README.md b/README.md
index fa49c37..36c8019 100644
--- a/README.md
+++ b/README.md
@@ -80,7 +80,7 @@ and you will see an output like this:
 [fmount@buildbot cephadm]$ make
 sed SPECS/cephadm.spec.in \
   -e "s/89ceb19fd8609fd4c99d10dd63f42e6786e37c86/dcf77bd9ff89dfef682c4a2dda05ac5c8651dbe5/" \
-  -e 's/@VERSION@/15.2.10/' \
+  -e 's/@VERSION@/16.1.0/' \
   -e 's/@RELEASE@/2/' \
  > SPECS/cephadm.spec
 cp SPECS/cephadm.spec SPECS/cephadm.spec.in
@@ -94,7 +94,7 @@ rpmbuild -bs /home/fmount/cephadm/SPECS/cephadm.spec \
   --define "_sourcedir /home/fmount/cephadm/SOURCES" \
   --define "_srcrpmdir /home/fmount/cephadm" \
   --define "dist .el8"
-Wrote: /home/fmount/cephadm/cephadm-15.2.10-2.el8.src.rpm
+Wrote: /home/fmount/cephadm/cephadm-16.1.0-2.el8.src.rpm
 ```
 
 In addition, a cephadm.spec file is generated from the input `SPECS/cephadm.spec.in` and it can be
@@ -103,7 +103,7 @@ found under the SPECS directory.
 At the end of this process, as described in the previous section, you can run the cbs build:
 
 ```
-$ cbs build [--scratch] storage8-ceph-octopus-el8 cephadm-15.2.10-2.el8.src.rpm
+$ cbs build [--scratch] storage8-ceph-pacific-el8 cephadm-16.1.0-2.el8.src.rpm
 ```
 
 
@@ -121,18 +121,18 @@ For instance, assuming you have the following data in the current spec:
 
 ```
 [fmount@buildbot cephadm]$ cat SPECS/cephadm.spec | grep -iE "(Release|Version)"
-Version: 15.2.10
+Version: 16.1.0
 Release: 2%{?dist}
 ```
 
 you can patch (and bump to a newer NVR) the current (existing) spec file by running:
 
 ```
-DIST=el8 RELEASE=1 VERSION=15.2.11 make
+DIST=el8 RELEASE=1 VERSION=16.1.0 make
 ```
 
 Then, running the regular cbs build command a new cephadm rpm can be built:
 
 ```
-$ cbs build [--scratch] storage8-ceph-octopus-el8 cephadm-15.2.11-1.el8.src.rpm
+$ cbs build [--scratch] storage8-ceph-pacific-el8 cephadm-16.1.0-2.el8.src.rpm
 ```