Merge pull request #984 from dhruvinparikh/develop

wbnns · web-flow · commit 0cd48ef2e113 · 2021-03-11T12:28:31.000+01:00
angular4-truffle: image path TransferToFriend.gif
diff --git a/contrib/angular4-truffle.asciidoc b/contrib/angular4-truffle.asciidoc
@@ -710,7 +710,7 @@ export class AppComponent {
 ----
 
 //TODO:While moving to DAPPS this needs to linked properly
-    image::/images/TransferToFriend.gif["Transfer To Friends In Action"]
+    image::../images/TransferToFriend.gif["Transfer To Friends In Action"]
 
 
  - Hurray !!! we completed our TransferToFriends project.
diff --git a/contrib/aws-network-setup.asciidoc b/contrib/aws-network-setup.asciidoc
@@ -13,7 +13,7 @@ The nodes to be launched for this set-up will be for the topology shown in figur
 
 [[_image_aws_topology_simple_bootnode]]
 .AWS Topology - Simple Ethereum network with boot node 
-image::images/aws-topology-simple-bootnode.png["Simple topology of Ethereum nodes with bootnode"]
+image::../images/aws-topology-simple-bootnode.png["Simple topology of Ethereum nodes with bootnode"]
 
 In the table below, the nodes in the topology are described. These nodes will be referred to by the name as mentioned in this table.
 
diff --git a/contrib/node-communication-interaction.asciidoc b/contrib/node-communication-interaction.asciidoc
@@ -19,7 +19,7 @@ such as IRC, SMTP, or HTTP. Binary protocols have the advantage of
 terseness, which translates into speed of transmission and
 interpretation.
 
-image:images/rlpx_rpc_xs.png[RLPx and JSONRPC]
+image:../images/rlpx_rpc_xs.png[RLPx and JSONRPC]
 
 https://github.com/ethereum/wiki/wiki/%C3%90%CE%9EVp2p-Wire-Protocol
 
@@ -57,7 +57,7 @@ and the rules around their processing. It is transport agnostic in that
 the concepts can be used within the same process, over sockets, over
 http, or in many various message passing environments.
 
-image:images/http_ws_ipc_jsonrpc.png[JSONRPC Transports]
+image:../images/http_ws_ipc_jsonrpc.png[JSONRPC Transports]
 
 [[jsonrpc2.0-http]]
 JSONRPC2.0 HTTP
diff --git a/contrib/upgradability-patterns.asciidoc b/contrib/upgradability-patterns.asciidoc
@@ -273,7 +273,7 @@ drawbacks:
 * Need to use Assembly
 * You need to keep the same storage footprint
 
-image::images/proxy-lib.png["Proxy-libraries"]
+image::../images/proxy-lib.png["Proxy-libraries"]
 
 ==== Implementation
 
