diff --git a/docs/book/src/conf.py b/docs/book/src/conf.py
index bcd82987d49..9e83337ce10 100644
--- a/docs/book/src/conf.py
+++ b/docs/book/src/conf.py
@@ -44,9 +44,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = "2.2"
+version = "2.5"
 # The full version, including alpha/beta/rc tags.
-release = "2.4"
+release = "2.5"
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/docs/book/src/integrations/librenms.rst b/docs/book/src/integrations/librenms.rst
index f3c8cadcb86..0eb04255122 100644
--- a/docs/book/src/integrations/librenms.rst
+++ b/docs/book/src/integrations/librenms.rst
@@ -50,14 +50,13 @@ On the CAPEv2 side, you will need to make a few tweaks to ``reporting.conf``.
 ``litereport`` will need enabled and  ``keys_to_copy`` should include
 'signatures' and 'detections'.
 
-Finally will need to enable the extend for your
+Finally, you will need to enable the extend in your snmpd configuration file:
 
 ::
 
     extend cape /etc/snmp/extends/cape
 
-Once snmpd is restarted and the the device rediscovered via LibreNMS,
-you will then be able to
+Once snmpd is restarted and the device is rediscovered via LibreNMS, you will then be able to view the CAPE statistics.
 
 For more detailed monitoring, if using KVM, you will likely want to
 also considering using `HV::Monitor`, which will allow detailed