From 7dac72d589aca1ab0241a98fed912b512d4ddeb6 Mon Sep 17 00:00:00 2001
From: Thomas Young <35565423+HexToString@users.noreply.github.com>
Date: Mon, 15 Nov 2021 22:45:48 +0800
Subject: [PATCH] fix dead link

fix dead link
---
 doc/Python_Pipeline/Pipeline_Design_EN.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/Python_Pipeline/Pipeline_Design_EN.md b/doc/Python_Pipeline/Pipeline_Design_EN.md
index ce33d73d..e30d09dc 100644
--- a/doc/Python_Pipeline/Pipeline_Design_EN.md
+++ b/doc/Python_Pipeline/Pipeline_Design_EN.md
@@ -18,7 +18,7 @@ Paddle Serving provides a user-friendly programming framework for multi-model co
 The Server side is built based on <b>RPC Service</b> and <b>graph execution engine</b>. The relationship between them is shown in the following figure.
 
 <div align=center>
-<img src='images/pipeline_serving-image1.png' height = "250" align="middle"/>
+<img src='../images/pipeline_serving-image1.png' height = "250" align="middle"/>
 </div>
 
 ### 1.1 RPC Service
@@ -61,7 +61,7 @@ The graph execution engine consists of OPs and Channels, and the connected OPs s
 - For cases where large data needs to be transferred between OPs, consider RAM DB external memory for global storage and data transfer by passing index keys in Channel.
 
 <div align=center>
-<img src='images/pipeline_serving-image2.png' height = "300" align="middle"/>
+<img src='../images/pipeline_serving-image2.png' height = "300" align="middle"/>
 </div>
 
 
@@ -80,7 +80,7 @@ The graph execution engine consists of OPs and Channels, and the connected OPs s
 - The following illustration shows the design of Channel in the graph execution engine, using input buffer and output buffer to align data between multiple OP inputs and multiple OP outputs, with a queue in the middle to buffer.
 
 <div align=center>
-<img src='images/pipeline_serving-image3.png' height = "500" align="middle"/>
+<img src='../images/pipeline_serving-image3.png' height = "500" align="middle"/>
 </div>
 
 
@@ -314,7 +314,7 @@ The default implementation of **pack_response_package** is to convert the dictio
 All examples of pipelines are in [examples/pipeline/](../../examples/Pipeline) directory, There are 7 types of model examples currently:
 - [PaddleClas](../../examples/Pipeline/PaddleClas) 
 - [Detection](../../examples/Pipeline/PaddleDetection)  
-- [bert](../../examples/Pipeline/bert)
+- [bert](../../examples/Pipeline/PaddleNLP/bert)
 - [imagenet](../../examples/Pipeline/PaddleClas/imagenet)
 - [imdb_model_ensemble](../../examples/Pipeline/imdb_model_ensemble)
 - [ocr](../../examples/Pipeline/PaddleOCR/ocr)
@@ -323,7 +323,7 @@ All examples of pipelines are in [examples/pipeline/](../../examples/Pipeline) d
 Here, we build a simple imdb model enable example to show how to use Pipeline Serving. The relevant code can be found in the `Serving/examples/Pipeline/imdb_model_ensemble` folder. The Server-side structure in the example is shown in the following figure:
 
 <div align=center>
-<img src='images/pipeline_serving-image4.png' height = "200" align="middle"/>
+<img src='../images/pipeline_serving-image4.png' height = "200" align="middle"/>
 </div>
 
 ### 3.1 Files required for pipeline deployment
-- 
GitLab