Skip to content

Commit c597e1f

Browse files
authored
Update README.md
1 parent 7d2cf00 commit c597e1f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Basic/flow-send-msg/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ We define a state (the "ping" to be shared), define a contract (the way to make
2020
You'll notice in our code we call these two classes ping and pong, the flow that sends the `"ping"`, and the flow that returns with a `"pong"`.
2121

2222

23-
Take a look at [Ping.java](https://github.com/corda/samples-java/blob/master/basic-cordapps/flow-send-msg/workflows-java/src/main/java/net/corda/examples/pingpong/flows/Ping.java#L20-L28).
23+
Take a look at [Ping.java](./workflows-java/src/main/java/net/corda/examples/pingpong/flows/Ping.java#L20-L28).
2424

2525
You'll notice that this flow does what we expect, which is to send an outbound ping, and expect to receive a pong. If we receive a pong, then our flow is sucessful.
2626

@@ -37,7 +37,7 @@ You'll notice that this flow does what we expect, which is to send an outbound p
3737
```
3838

3939

40-
And of course we see a similar behavior in [Pong.java](https://github.com/corda/samples-java/blob/master/basic-cordapps/flow-send-msg/workflows-java/src/main/java/net/corda/examples/pingpong/flows/Pong.java#L22-L30).
40+
And of course we see a similar behavior in [Pong.java](./workflows-java/src/main/java/net/corda/examples/pingpong/flows/Pong.java#L22-L30).
4141

4242
We expect to receive data from a counterparty that contains a ping, when we receive it, we respond with a pong.
4343

0 commit comments

Comments
 (0)