Update README.md

willdurand · willdurand · commit 71ed28d8f96b · 2014-12-18T11:37:35.000+01:00
diff --git a/README.md b/README.md
@@ -317,6 +317,27 @@ try {
 
 Everything is ok, enjoy!
 
+### TimedGeocoder
+
+We introduced a new feature as of Geocoder v3.0.0. The `TimedGeocoder` class
+profiles each `geocode` and `reverse` call. So you can easily figure out how
+many time/memory was spent for each geocoder/reverse call.
+
+```php
+// configure you geocoder object
+
+$stopwatch = new \Symfony\Component\Stopwatch\Stopwatch();
+$geocoder = new \Geocoder\TimedGeocoder($geocoder, $stopwatch);
+
+$geocoder->geocode('Paris, France');
+
+// Now you can debug your application
+```
+
+We use the [symfony/stopwatch](http://symfony.com/doc/current/components/stopwatch.html)
+component under the hood. Which means, if you use the Symfony framework the
+geocoder calls will appear in your timeline section in the Web Profiler.
+
 
 Dumpers
 -------
@@ -436,28 +457,6 @@ You can write your own `provider` by implementing the `Provider` interface.
 
 You can provide your own `dumper` by implementing the `Dumper` interface.
 
-TimedGeocoder
--------------
-
-We introduced a new feature in Geocoder 3. The `TimedGeocoder` profiles
-each `geocode` and `reverse` call. So you can easily figure out how many
-time/memory was spent for each geocoder/reverse call.
-
-```php
-// configure you geocoder object
-
-$stopwatch = new \Symfony\Component\Stopwatch\Stopwatch();
-$geocoder = new \Geocoder\TimedGeocoder($geocoder, $stopwatch);
-
-$geocoder->geocode('Paris, France');
-
-// Now you can debug your application
-```
-
-We use the [symfony/stopwatch](http://symfony.com/doc/current/components/stopwatch.html)
-component under the hood. Which means, if you use the symfony framework the
-geocoder calls will appear in your timeline section in the webprofiler.
-
 
 Versioning
 ----------
