fix hyperlinks to evas, widgets, genlist and event guides

Signed-off-by: Clément Bénier <clement.benier@openwide.fr>

pages/program_guide/basic_application_structure_pg.txt

@@ -30,10 +30,11 @@ The EFL are a set of layered libraries, as shown in the following diagram:
 When you create a basic EFL application, you use the following main libraries
 as a basis:
 
-  * **Elementary** is the top-most library with which you create your EFL application. It provides all the functions you need to create a window, create simple and complex layouts, manage the life cycle of a view, and add widgets. Go to [[/coming_soon|Widgets program guide]]
+  * **Elementary** is the top-most library with which you create your EFL application. It provides all the functions you need to create a window, create simple and complex layouts, manage the life cycle of a view, and add widgets. Go to [[/program_guide/widgets_pg|Widgets program guide]]
+
   * **Edje**  is the library used by Elementary to provide a powerful theme. You can also use Edje to create your own objects and use them in your application. You may also want to extend the default theme. You will find more information about Edje and the EDC format in [[/coming_soon|Edje]] and [[/coming_soon|Customizing Widgets]].
   * **Ecore** is the library which manages the main loop of your application. The main loop is one of the most important concepts you need to know about to develop an application. The main loop is where events are handled, and where you interact with the user through the callback mechanism. The main loop mechanisms are explained in the [[/coming_soon|Main Loop guide]].
-  * **Evas**  is the canvas engine. Evas is responsible for managing the drawing of your content. All graphical objects that you create are Evas objects. Evas handles the entire state of the window by filling the canvas with objects and manipulating their states. In contrast to other canvas libraries, such as Cairo, OpenGL, and XRender, Evas is not a drawing library but a scene graph library that retains the state of all objects. The Evas concept is explained in [[/coming_soon|Rendering Concept and Method in Evas]]. Evas objects are created and then manipulated until they are no longer needed, at which point they are deleted. This allows the developer to work in the same terms that a designer thinks in: it is a direct mapping, as opposed to having to convert the concepts into drawing commands in the right order, calculate minimum drawing calls needed to get the job done, and so on.
+  * **Evas**  is the canvas engine. Evas is responsible for managing the drawing of your content. All graphical objects that you create are Evas objects. Evas handles the entire state of the window by filling the canvas with objects and manipulating their states. In contrast to other canvas libraries, such as Cairo, OpenGL, and XRender, Evas is not a drawing library but a scene graph library that retains the state of all objects. The Evas concept is explained in [[/program_guide/evas/rendering_concept_and_method_in_evas|Rendering Concept and Method in Evas]]. Evas objects are created and then manipulated until they are no longer needed, at which point they are deleted. This allows the developer to work in the same terms that a designer thinks in: it is a direct mapping, as opposed to having to convert the concepts into drawing commands in the right order, calculate minimum drawing calls needed to get the job done, and so on.
   * **Eina** is the basis of all the EFL libraries. Eina is a toolbox that implements an API for data types in an efficient way. It contains all the functions needed to create lists and hashes, manage shared strings, open shared libraries, and manage errors and memory pools. Eina concepts are explained in [[/coming_soon|Using Data Types]].
 
 The EFL include more than just the above libraries(here the complete
@@ -64,7 +65,7 @@ the content and where the Evas canvas is placed.
 
 There are three main groups of objects provided by Elementary:
 
-    * [[/coming_soon|Widgets]]: These are the widgets with which you build your application UI.
+    * [[/program_guide/widgets_pg|Widgets]]: These are the widgets with which you build your application UI.
     * [[[[program_guide/containers_pg|Containers]]: These are the containers that hold the widgets.
     * Infrastructure: These are the modules that deal with Elementary as a whole.
 

pages/program_guide/widgets/basics.txt

@@ -75,9 +75,10 @@ use it.
 
 Several callbacks can be registered on an Elementary object. The following is
 an overview of the different callback types and how they differ. For more
-information about events, see [[/coming_soon|Handling Events]]. For more
-information about Evas objects and smart objects, see [[/coming_soon|Rendering
-Concept and Method in Evas]].
+information about events, see [[/program_guide/event_effect_pg|Handling
+Events]]. For more information about Evas objects and smart objects, see
+[[/program_guide/evas/rendering_concept_and_method_in_evas|Rendering Concept
+and Method in Evas]].
 
 === Evas Event Callback ===
 

pages/tutorial/form_tutorial.txt

@@ -108,8 +108,8 @@ all functions that are called back when an item is created. In this case,
 create the callbacks _genlist_text_get (for labels) and _genlist_content_get
 (for icons). These functions are called when labels and icons of the genlist
 item are created. For more information go to the
-[[/tutorial/genlist_tutorial|genlist tutorial]] or the [[/coming_soon|genlist
-guide]].
+[[/tutorial/genlist_tutorial|genlist tutorial]] or the
+[[/program_guide/containers/genlist|genlist guide]].
 
 The list of contacts and their descriptions are contained in an array of
 Contacts and an array of form items.