Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Commit

Permalink
doc edit
Browse files Browse the repository at this point in the history
  • Loading branch information
rafrombrc committed Apr 16, 2012
1 parent b97dc52 commit fa048b4
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/getstarted.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
useless.

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
Expand Down

0 comments on commit fa048b4

Please sign in to comment.