Browse files

doc edit

  • Loading branch information...
1 parent b97dc52 commit fa048b42bcea5c5f1c159c8bb4630e27cd539e78 @rafrombrc rafrombrc committed Apr 16, 2012
Showing with 4 additions and 4 deletions.
  1. +4 −4 docs/getstarted.rst
@@ -5,10 +5,10 @@ There are two primary components with which users of the metlog-py library
should be aware. The first is the :doc:`api/client` client class. The
MetlogClient exposes the main Metlog API, and is generally your main point of
interaction with the Metlog system. The client doesn't do very much, however;
-it merely pulls together the relevant parts of the message constructs a
-properly structured dictionary representing the message. Actual message
-delivery is handled by a :doc:`sender <api/senders>`. Without a properly
-configured sender, a MetlogClient is useless.
+it just constructs a properly structured dictionary representing the message
+and passes it on. Actual message delivery is handled by a :doc:`sender
+<api/senders>`. Without a properly configured sender, a MetlogClient is
The first question you're likely to face when using metlog-py, then, is likely
to be "How the heck do I get my hands on a properly configured MetlogClient

0 comments on commit fa048b4

Please sign in to comment.