fix hyperlinks to edje PG

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

pages/program_guide/basic_application_structure_pg.txt

@@ -32,7 +32,7 @@ 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 [[/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]].
+  * **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 [[/program_guide/edje_pg|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 [[/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]].

pages/program_guide/containers/layout.txt

@@ -10,7 +10,7 @@ widgets used in Elementary.
 
 An Edje design file describes how the elements of the UI are positioned and
 how they behave when interacted with. For more information about Edje, see the
-[[/coming_soon|Edje guide]].
+[[/program_guide/edje_pg|Edje guide]].
 
 === Table of Contents ===
 

pages/program_guide/event_effect/edje_events.txt

@@ -7,7 +7,7 @@ Edje themes have ''program'' sections. These are small sections triggered upon
 the reception of a signal that can execute actions, such as changing the state
 of an edje part and running another program.
 
-For more information on themes and programs, see the [[/coming_soon|Edje
+For more information on themes and programs, see the [[/program_guide/edje_pg|Edje
 guide]].
 
 === Table of Contents ===

pages/tutorial/form_tutorial.txt

@@ -197,7 +197,7 @@ pointer.
 The ''_genlist_content_get'' function is called several times depending on the
 style of the created item. In this case, with the default style for the
 genlist item, there are two different swallow parts. A swallow part is a
-container in the [[/coming_soon|edje file]] of the genlist item, which may
+container in the [[/program_guide/edje_pg|edje file]] of the genlist item, which may
 contain an evas object. The following figure shows the layout of different
 parts in the theme.
 

pages/tutorial/genlist/modifications.txt

@@ -24,7 +24,7 @@ The Genlist Widget lists all available item styles:
 
 
 Further customization is achieved by modifying the theme as explained in the
-[[/coming_soon|Edje guide]].
+[[/program_guide/edje_pg|Edje guide]].
 
 In case the customization is only visual, it is good practice to keep the same
 item style names for new themes. This makes it possible to change theme and

pages/tutorial/genlist/set-up.txt

@@ -79,7 +79,7 @@ This callback returns a C string that is displayed in the part named after the
 according to the current theme.
 
 If you are not familiar with the concept of parts in the EFLs, read
-[[/coming_soon|the Write a Simple EDC File]] section.
+[[/program_guide/edje/basic_concepts##Writing_Simple_EDC_File|the Write a Simple EDC File]] section.
 
 <note>
 The value returned is freed by the EFLs: the value must be freshly-allocated, do not free it yourself and do not re-use it across list elements.
@@ -102,7 +102,10 @@ _genlist_text_get(void *data, Evas_Object *obj, const char *part)
 </code>
 
 <note>
-The names and positions of parts depends on the item_style chosen when adding new items to the genlist. Setting a custom theme makes it possible to completely change genlists by adding and moving parts. The [[/coming_soon|Edje]] guide explains how to do that.
+The names and positions of parts depends on the item_style chosen when adding
+new items to the genlist. Setting a custom theme makes it possible to
+completely change genlists by adding and moving parts. The
+[[/program_guide/edje_pg|Edje]] guide explains how to do that.
 </note>
 
 It is possible to behave differently according to data