From 644d359d63a5b7ae8597e083ea92420ac3835e11 Mon Sep 17 00:00:00 2001 From: munapower Date: Fri, 17 Jan 2025 09:29:36 -0300 Subject: [PATCH] Correcting line in Fabric Gateway client to be like in Legacy Signed-off-by: munapower --- .../docs/ApplicationDev/01-FabricGateway.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/full-stack-asset-transfer-guide/docs/ApplicationDev/01-FabricGateway.md b/full-stack-asset-transfer-guide/docs/ApplicationDev/01-FabricGateway.md index 328b4938..93473eed 100644 --- a/full-stack-asset-transfer-guide/docs/ApplicationDev/01-FabricGateway.md +++ b/full-stack-asset-transfer-guide/docs/ApplicationDev/01-FabricGateway.md @@ -48,7 +48,7 @@ In order for the client application to operate effectively, it must make use of ## Fabric Gateway client API -The following diagram demonstrates for the transaction submit flow how it is executed for a client using the Fabric Gateway client API. Solid orange lines represent interactions between the client and a Gateway peer, which must cross the firewall at the boundary of the network deployment. Dashed green lines represent interactions between network nodes. +The following diagram demonstrates how the transaction submit flow is executed for a client using the Fabric Gateway client API. Solid orange lines represent interactions between the client and a Gateway peer, which must cross the firewall at the boundary of the network deployment. Dashed green lines represent interactions between network nodes. Notice that the client only needs to interact directly with the Gateway peer. The Gateway peer operates as a client driving the transaction submit flow from within the network deployment on behalf of the client application.