[incubator-pulsar.wiki] branch master updated: Updated PIP 21: Pulsar Edge Component (markdown)

[sijie]

This is an automated email from the ASF dual-hosted git repository.

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-pulsar.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new f54917e  Updated PIP 21: Pulsar Edge Component (markdown)
f54917e is described below

commit f54917e9257084979e68a1a41f5b10da1ee67cef
Author: Sijie Guo <guosi...@gmail.com>
AuthorDate: Fri Aug 10 12:14:02 2018 -0700

    Updated PIP 21: Pulsar Edge Component (markdown)
---
 PIP-21:-Pulsar-Edge-Component.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/PIP-21:-Pulsar-Edge-Component.md b/PIP-21:-Pulsar-Edge-Component.md
index ab09e39..963b5b8 100644
--- a/PIP-21:-Pulsar-Edge-Component.md
+++ b/PIP-21:-Pulsar-Edge-Component.md
@@ -11,7 +11,7 @@ The current Pulsar function runtime environment is located on 
a Pulsar Broker in
 
 
 
-![Figure 1: Current State](images/pip21-image1.jpg) 
+![Figure 1: Current State](img/pip21-image1.jpg) 
 
 
 
@@ -21,7 +21,7 @@ In the desired state, we would be able to host simple Pulsar 
functions on the Io
 
 Events can still be forwarded to the downstream Pulsar cluster for longer-term 
storage, and additional Pulsar function execution.
 
-![Figure 2: Desired State](images/pip21-image2.jpg) 
+![Figure 2: Desired State](img/pip21-image2.jpg) 
 
 
 ## Requirements
@@ -43,7 +43,7 @@ The Pulsar Edge Component will wrap a standard pulsar client 
object, that it wil
 
 IoT applications would be used to capture the sensor data that is transmitted 
to the ioT gateway device over short-range protocols such as ZigBee, BlueTooth, 
convert it into the desired format, and publish it to the Pulsar Gateway object 
using the pub/sub API. 
 
-![Figure 3: Pulsar Edge Component Design](images/pip21-image3.jpg) 
+![Figure 3: Pulsar Edge Component Design](img/pip21-image3.jpg)