libcurl: reworded the "basic design" chapter slightly

libcurl.md

@@ -23,23 +23,23 @@ First you create an "easy handle", which is your handle to a transfer really.
 
     CURL *curl_handle = curl_easy_init();
 
-Then you set several options for that handle, that controls how the upcoming
-transfer will pan out.
+Then you set various options in that handle, to control how the upcoming
+transfer. Like this example sets the URL:
 
     /* set URL to operate on */
     res = curl_easy_setopt( curl_handle, CURLOPT_URL, "http://example.com/");
 
-Finally you fire off the transfer.
-
-After the transfer has completed, you can figure out if it succeeded or not
-and you can extract stats and various information that libcurl gathered during
-the transfer. (See curl_easy_getinfo description.)
+Finally you fire off the actual transfer.
 
 The actual "perform the transfer phase" can be done using different different
 means and function calls, depending on what kind of behavior you want in your
 application and how libcurl is best integrated into your architecture. Those
 are further described later in this chapter.
 
+After the transfer has completed, you can figure out if it succeeded or not
+and you can extract stats and various information that libcurl gathered during
+the transfer. (See curl_easy_getinfo description.)
+
 While the transfer is ongoing, using any of the functions you can use to drive
 the transfer (or in fact transfers - in plural), libcurl calls your specified
 functions - known as *callbacks* - to deliver data, to read data or to do a