Fix docs build error

Change-Id: I25558ff48b6236773f765aad8d1fc150f7011aef

2 files changed, 5 insertions, 5 deletions

diff --git a/doc/source/contributor/architecture.rst b/doc/source/contributor/architecture.rst
index cda99243..896e517d 100644
--- a/doc/source/contributor/architecture.rst
+++ b/doc/source/contributor/architecture.rst
@@ -59,9 +59,9 @@ How is data collected?
 
 The Ceilometer project created 2 methods to collect data:
 
-1. :term:`Notification agent` which takes messages generated on the
+1. :term:`notification agent` which takes messages generated on the
    notification bus and transforms them into Ceilometer samples or events.
-2. :term:`Polling agent`, will poll some API or other tool to collect
+2. :term:`polling agent`, will poll some API or other tool to collect
    information at a regular interval. The polling approach may impose
    significant on the API services so should only be used on optimised
    endpoints.
diff --git a/doc/source/contributor/overview.rst b/doc/source/contributor/overview.rst
index 794a73e6..ebc03554 100644
--- a/doc/source/contributor/overview.rst
+++ b/doc/source/contributor/overview.rst
@@ -26,9 +26,9 @@ Metering
 If you divide a billing process into a 3 step process, as is commonly done in
 the telco industry, the steps are:
 
-1. :term:`Metering`
-2. :term:`Rating`
-3. :term:`Billing`
+1. :term:`metering`
+2. :term:`rating`
+3. :term:`billing`
 
 Ceilometer's initial goal was, and still is, strictly limited to step
 one. This is a choice made from the beginning not to go into rating or billing,