Skip to content
Permalink
Browse files

typos

  • Loading branch information...
simonjohnthompson committed Apr 15, 2019
1 parent 6afc49c commit 1e5cbfc3293bc68709fca19582393f84a93b6f77
Showing with 3 additions and 3 deletions.
  1. +1 −1 docs/tutorial-v1.3/checklist.md
  2. +2 −2 docs/tutorial-v2.0/using-marlowe.md
@@ -48,7 +48,7 @@ The [overview](./differences.md) describes the differences between Marlowe 2.0 a

## Where to go to find out more

- The discussions about _embedded Marlowe_ in the tutorials: [v1.3](embedded-marlowe.md), [V2.0](../tutorial-v2.0/embedded-marlowe.md), give a complete example of a contract in both versions of the language.
- The discussions about _embedded Marlowe_ in the tutorials: [v1.3](embedded-marlowe.md), [v2.0](../tutorial-v2.0/embedded-marlowe.md), give a complete example of a contract in both versions of the language.

- Here are tutorials on [Marlowe v1.3](./README.md) and [Marlowe v2.0](../tutorial-v2.0/README.md), and [Meadow in the cloud](https://prod.meadow.marlowe.iohkdev.io).

@@ -37,7 +37,7 @@ To single step, you can work in `ghci` like this, using the facility to make loc

Where `inputList`s are lists of inputs that may include any number of inputs depending on the context, and `sigList`s are lists of participant identifiers that represent the signatories of the transaction and there may also be any number of them.

And we can then explore the values produced. Note, however, that the local bindings are lost each time a `:load` or `:l` command is performed.
We can then explore the values produced. Note, however, that the local bindings are lost each time a `:load` or `:l` command is performed.

An alternative way of doing this is to add these definitions to a working file, e.g. `Build.hs`, where these definitions will be preserved. Indeed, it would be very sensible to include some of the definitions used above in such a file.

@@ -71,7 +71,7 @@ data CommitInfo = CommitInfo { redeemedPerPerson :: M.Map Person Integer

## Inputs

For the contract to progress, it needs to be presented with inputs, as represented by the AnyInput type, which has four types grouped in two supertypes:
For the contract to progress, it needs to be presented with inputs, as represented by the `AnyInput` type, which has four types grouped in two supertypes:

```haskell
data AnyInput = Action IdAction

0 comments on commit 1e5cbfc

Please sign in to comment.
You can’t perform that action at this time.