Clean up some old docstrings

diff --git a/pdns/dnsbackend.hh b/pdns/dnsbackend.hh
index 0d35c919b5e3a8917b2b7131083b7b42febcaeb2..901987f66aa8246a3a8aeb1c4011225a7d5da367 100644 (file)
--- a/pdns/dnsbackend.hh
+++ b/pdns/dnsbackend.hh
@@ -106,7 +106,7 @@ struct TSIGKey {
 
 class DNSPacket;
 
-//! This virtual base class defines the interface for backends for the ahudns.
+//! This virtual base class defines the interface for backends for PowerDNS.
 /** To create a backend, inherit from this class and implement functions for all virtual methods.
     Methods should not throw an exception if they are sure they did not find the requested data. However,
     if an error occurred which prevented them temporarily from performing a lockup, they should throw a DBException,

diff --git a/pdns/nameserver.cc b/pdns/nameserver.cc
index ef7eef4c66d603bd87488ba37ecd4cafb11df803..3ce54d92f6aa90f69e05424966f4d5f9c3d4d371 100644 (file)
--- a/pdns/nameserver.cc
+++ b/pdns/nameserver.cc
@@ -61,8 +61,8 @@ extern StatBag S;
 
     A DNSBackend is an entity that returns DNSResourceRecord objects in return to explicit questions for domains with a specified QType
 
-    PowerDNS uses the UeberBackend as its DNSBackend. The UeberBackend by default has no DNSBackends within itself, those are loaded
-    using the pdns_control tool. This way DNSBackend implementations can be kept completely separate (but they often aren't).s
+    PowerDNS uses the UeberBackend, which hosts DNSBackends. By default it has no DNSBackends within itself, those are loaded
+    by setting --load=<list of backends>. This way DNSBackend implementations can be kept completely separate, but most aren't.
 
     If one or more DNSBackends are loaded, the UeberBackend fields the queries to all of them until one answers.