Commits

James Mills  committed 33486b3

Fixed more spelling and grammar errors

  • Participants
  • Parent commits 60e3305

Comments (0)

Files changed (8)

 with a strong **Component** Architecture.
 
 circuits also includes a lightweight, high performance and scalable
-HTTP/WSGI web server as well as various I/O and Networking components.
+HTTP/WSGI compliant web server as well as various I/O and Networking
+components.
 
 To take full advantage of circuits and its architecture, circuits
 requires that your application be designed in terms of components
 written using the circuits application framework is maintainable,
 scalable and easy to develop.
 
-The circuits framework has a certain elegance making it a rather
-attracting feature. New features are built into the framework with
-this in mind and circuits "eats its own dog food" by having a
-feature-rich library of components built atop the core components.
+circuits' **Loosely Coupled** **Component Architecture** allows for a
+high level of **Reuse** and **Scalability**. Components are **Componsable**
+and much of the component library that circuits ships with are implemented
+as composed components.
 
 - **Documentation**: http://packages.python.org/circuits or `circuits Read the Docs`_.
 - **Project website**: https://bitbucket.org/prologic/circuits/

File docs/source/changes.rst

 - Fixes Server socket being discarded twice on close + disconnect
 - Socket.write now expects bytes (bytes for python3 and str for python2)
 - Better handling of encoding in HTTP Component (allow non utf-8 encoding)
-- Always encode http headers in utf-8
+- Always encode HTTP headers in utf-8
 - Fixes error after getting socket.ERRCONNREFUSED
 - Allows TCPClient to bind to a specific port
 - Improved docs
-- Handles closing of udpserver socket when no client is connected
-- Adds an unregister handler for components
+- Handles closing of UDPServer socket when no client is connected
+- Adds an un-register handler for components
 - Allows utils.kill to work from a different thread
 - Fixes bug when handling "*" in channels and targets
-- Fixes a bug that could occur when unregistering components
+- Fixes a bug that could occur when un-registering components
 - Fixes for CPU usage problems when using circuits with no I/O pollers
   and using a Timer for timed events

File docs/source/dev/testing.rst

 Testing
 =======
 
-Here's how we do testing in circutis:
+Here's how we do testing in circuits:
 
 .. todo :: flesh this out

File docs/source/howtos/simple_server.rst

 4. Register a ``TCPServer`` Component and configure it.
 5. Create Event Handlers for:
 
-   - Dealiig with new connecting clients.
+   - Dealing with new connecting clients.
    - Dealing with clients whom have disconnected.
    - Dealing with messages from connected clients.
 

File docs/source/man/components.rst

 with Complex Components being a subtree within that structure.
 
 A Component is attached to the tree by registering with the parent and
-detached by unregistering itself (methods
+detached by un-registering itself (methods
 :meth:`~circuits.core.components.BaseComponent.register` and
 :meth:`~circuits.core.components.BaseComponent.unregister` of 
 ``BaseComponent``).

File docs/source/tutorial/index.rst

 
 :download:`Download 002.py <002.py>`
 
-Okay, so this still isn't very sueful! But at least we can create
+Okay, so this still isn't very useful! But at least we can create
 components with the behavior we want.
 
 Let's move on to something more interesting...
 
 Alright! We have something slightly more useful! Whoohoo it says hello!
 
-.. note:: Press ^C (*Ctrl + C*) to exit.
+.. note:: Press ^C (*CTRL + C*) to exit.
 
 
 Registering Components
 -------------
 
 So far in our tutorial we have been defining an Event Handler for a builtin
-Event called ``Started`` (*which incidently gets fired on a channel called
+Event called ``Started`` (*which incidentally gets fired on a channel called
 "started"*). What if we wanted to define our own Event Handlers and our own
 Events ? You've already seen how easy it is to create a new Event Handler
 by simply defining a normal Python method on a Component.
    class MyEvent(Event):
       """MyEvent"""
 
-So here's our example where we'll define a new Event claled ``Bark``
+So here's our example where we'll define a new Event called ``Bark``
 and make our ``Dog`` fire a ``Bark`` event when our application starts up.
 
 .. literalinclude:: 008.py
 
 Lastly...
 
-Asynchronous programming has many advntages but can be a little harder to
+Asynchronous programming has many advantages but can be a little harder to
 write and follow. A silently caught exception in an Event Handler, or an Event
 that never gets fired, or any number of other weird things can cause your
 application to fail and leave you scratching your head.
 unwanted behavior in a system so we expect to be able to recover from
 horrible situations.
 
-SO what do we do ? Welll that's easy. circuits come with a ``Debugger``
+SO what do we do ? Well that's easy. circuits come with a ``Debugger``
 that lets you log all events as well as all errors so you can quickly and
 easily discover which Event is causing a problem and which Event Handler to
 look at.
    def bark(self):
        print("Woof! I'm %s!" % self.name)
 
-Running again with our coorection results in the expected output::
+Running again with our correction results in the expected output::
    
    Woof! I'm Bob!
    Woof! I'm Fred!

File docs/source/users.rst

   Worked on by Toni Alatalo and Petri Aura at `Playsign
   <http://www.playsign.net/>` in collaboration with other realXtend developers.
 - `PriceWaterHouseCoopers <http://www.pwc.com/>`
-  TAMS Report Generator <http://www.tams.com.au>` written by James Milsl
+  TAMS Report Generator <http://www.tams.com.au>` written by James Mills
   and Michael Anton.
 - `Mangahelpers <http://mangahelpers.com/>`
-  Profiler for checking our webpages generation times, sql and cache queries
+  Profiler for checking our webpages generation times, SQL and cache queries
   times, project page on <https://launchpad.net/website-profiler>
 
 Other Users

File docs/source/web/gettingstarted.rst

 This completes our simple web application which will respond with
 "Hello World!" when anyone accesses it.
 
-*Admitedly this is a stupidly simple web application! But circuits.web is
+*Admittedly this is a stupidly simple web application! But circuits.web is
 very powerful and plays nice with other tools.*
 
 Now we need to run the application: