T4m
diff --git a/‎components/stopwatch.rst
Lines changed: 20 additions & 14 deletions b/‎components/stopwatch.rst
Lines changed: 20 additions & 14 deletions
@@ -7,6 +7,10 @@ The Stopwatch Component
 
     Stopwatch component provides a way to profile code.
 
+.. versionadded:: 2.2
+    The Stopwatch Component is new to Symfony 2.2. Previously, the ``Stopwatch``
+    class was located in the ``HttpKernel`` component.
+
 Installation
 ------------
 
@@ -19,8 +23,9 @@ Usage
 -----
 
 The Stopwatch component provides an easy and consistent way to measure execution
-time of certain parts of code, so that you don't constantly have to parse
-microtime by yourself. The basic usage is as simple as this::
+time of certain parts of code so that you don't constantly have to parse
+microtime by yourself. Instead, use the simple
+:class:`Symfony\\Component\\Stopwatch\\Stopwatch` class::
 
     use Symfony\Component\Stopwatch\Stopwatch;
 
@@ -35,14 +40,15 @@ You also can provide a category name to an event::
     $stopwatch->start('eventName', 'categoryName');
 
 You can consider categories as a way of tagging events. The Symfony Profiler
-tool uses categories to nicely colorcode different events. 
+tool, for example, uses categories to nicely color-code different events. 
 
 Periods
 -------
 
-As we all know from the real world, all stopwatches come with two buttons.
+As you know from the real world, all stopwatches come with two buttons.
 One for starting and stopping the stopwatch, another to measure the lap time.
-And that's exactly what lap method does. ::
+This is exactly what the :method:`Symfony\\Component\\Stopwatch\\Stopwatch::lap``
+method does::
 
     $stopwatch = new Stopwatch();
     // Start event named 'foo'
@@ -54,39 +60,39 @@ And that's exactly what lap method does. ::
     // some other code goes here
     $event = $stopwatch->stop('foo');
 
-Lap information is stored in periods within the event. To get lap information aka periods call ::
+Lap information is stored in periods within the event. To get lap information
+(aka periods) call::
 
     $event->getPeriods();
 
-Besides getting periods, we can get other useful information from the event object. E.g::
+Besides getting periods, you can get other useful information from the event object.
+For example::
 
     $event->getCategory();      // Returns the category the evenent was started in
     $event->getOrigin();        // Returns the start time of the Event in milliseconds
-    $event->ensureStopped();    // Stops all non already stopped periods
+    $event->ensureStopped();    // Stops all not-already-stopped periods
     $event->getStartTime();     // Returns the start of the very first period
     $event->getEndTime();       // Returns the end time of the very last period
     $event->getDuration();      // Gets the duration (including all periods) of the event
     $event->getMemory();        // Gets the max memory usage of all periods
 
-
 Sections
 --------
 
 Sections are a way to logically split the timeline into groups. You can see
 how Symfony uses sections to nicely visualize framework lifecycle in the
-Symfony Profiler tool. Here is a basic usage of sections.::
+Symfony Profiler tool. Here is a basic usage of sections::
 
     $stopwatch = new Stopwatch();
 
     $stopwatch->openSection();
-    $stopwatch->start('parisng_config_file', 'filesystem_operations');
+    $stopwatch->start('parsing_config_file', 'filesystem_operations');
     $stopwatch->stopSection('routing');
 
-    $events = $stopwatch->getSectionEvents('section');
-
+    $events = $stopwatch->getSectionEvents('routing');
 
 You can reopen a closed section by calling the openSection method and specifying
-an id of the section to be reopened. e.g.::
+an id of the section to be reopened::
     $stopwatch->openSection('routing');
     $stopwatch->start('building_config_tree');