fix links

zkoss · Sep 4, 2024 · 73d17de · 73d17de
1 parent 138e1e9
commit 73d17de
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 25 deletions.
diff --git a/get_started/Get_ZK_Up_and_Running_with_MVC.md b/get_started/Get_ZK_Up_and_Running_with_MVC.md
@@ -11,10 +11,10 @@ approach to build the application here. This approach is very intuitive
 and flexible and gives you full control of components. In addition, you
 can also choose to go with the **MVVM** approach that is covered in [
 Get ZK Up and Running with
-MVVM](ZK_Getting_Started/Get_ZK_Up_and_Running_with_MVVM).
+MVVM](/get_started/Get_ZK_Up_and_Running_with_MVVM).
 
 You can download the complete source code under the [ Start from Example
-Project](#Start_from_Example_Project) section.
+Project](#start_from_example_project) section.
 
 {% include tutorial-common.md %}
 

diff --git a/get_started/Get_ZK_Up_and_Running_with_MVVM.md b/get_started/Get_ZK_Up_and_Running_with_MVVM.md
@@ -11,15 +11,16 @@ approach that is classified as the **Model-View-ViewModel (MVVM)**
 design pattern. Using this approach, ZK can control components for you
 automatically and it separates the UI from its controller clearly. In
 addition, you can also choose to go with the <b>MVC</b> approach that is
-covered in another tutorial [^1].
+covered in [another tutorial](/get_started/Get_ZK_Up_and_Running_with_MVC).
 
 {% include tutorial-common.md %}
 
 # Automatic UI Controlling
 
 The approach we introduce here to control user interaction is to **let
 ZK control UI components for you**. This approach is classified to
-**Model-View-ViewModel** (**MVVM**) design pattern. [^2] This pattern
+**Model-View-ViewModel** (**MVVM**) design pattern.(See [MVVM in Developer's
+Reference](ZK_Developer's_Reference/MVVM)) This pattern
 divides an application into three parts.
 
 The **Model** consists of application data and business rules.
@@ -254,14 +255,15 @@ specified in `@NotifyChange`.
 
 The way to display a collection of data with data binding is very
 similar to the way in the MVC approach. we will use a special tag,
-<template>[^3], to control the rendering of each item. The only
+[`<template>`](ZK_Developer's_Reference/MVC/View/Template), to control the rendering of each item. The only
 difference is we should use data binding expression instead of EL.
 
-Steps to use <template>:
+Steps to use `<template>`:
 
 1.  Use **<template>** to enclose components that we want to create
     iteratively.
-2.  Set template's "name" attribute to "model". [^4]
+2.  Set template's "name" attribute to "model".(See [ZK Developer's Reference/MVC/View/Template/Listbox
+    Template](ZK_Developer's_Reference/MVC/View/Template/Listbox_Template))
 3.  Use implicit variable, **each**, to assign domain object's
     properties to component's attributes.
 
@@ -316,21 +318,4 @@ previous sections.
         </hbox>
 ```
 
-You can view complete zul at
-[Github](https://github.com/zkoss-demo/gettingStarted/blob/master/src/main/webapp/searchMvvm.zul)
-
-# References
-
-<references/>
-
-[^1]: [ZK Getting Started/Get ZK Up and Running with
-    MVC](ZK_Getting_Started/Get_ZK_Up_and_Running_with_MVC)
-
-[^2]: [ MVVM in Developer's
-    Reference](ZK_Developer's_Reference/MVVM)
-
-[^3]: [ZK Developer's
-    Reference/MVC/View/Template](ZK_Developer's_Reference/MVC/View/Template)
-
-[^4]: [ZK Developer's Reference/MVC/View/Template/Listbox
-    Template](ZK_Developer's_Reference/MVC/View/Template/Listbox_Template)
+You can view complete zul at [Github](https://github.com/zkoss-demo/gettingStarted/blob/master/src/main/webapp/searchMvvm.zul)