update tutorial 1

Author: alexv-quant

assets/images/automated_transfer/add_automation.png

@@ -0,0 +1,23 @@
+---
+title: Concepts
+parent: Payscript
+layout: page
+nav_order: 4
+---
+
+
+## Automation
+An entity created by a [customer] into their bank account. The automation is created from a PayScript from among the ones that have been deployed by [developers]. If the selected payscript uses a trigger type that requires [trigger parameters], those need to be specified as part of creating the automation. If the selected payscript defines [script parameters], those need to be specified as part of creating the automation.
+
+## Reserve
+An abstract segregation of funds in a customer's account with a name and a purpose, so that those funds can be considered unavailable for other purposes, effectively reserving them. Funds can be added to and removed from the reserve by the account owner, or by whoever the account owner has given [consent] to do this.
+
+## Consent
+Consent is given by a [customer] to another customer perform specific actions on their accounts. The types of consent that can be given are:
+Fund check: Allows checking if the owner has more available funds than a given amount
+Automations: 
+Balance: Allows seeing the balance of the owner
+Transactions: Allows making transactions on behalf of the owner
+
+[customer]: /docs/quant_flow/personas#customer
+[developers]: /docs/quant_flow/personas#developer

assets/images/automated_transfer/developer_view.png

@@ -20,4 +20,7 @@ A string composed of 6 numerical characters.
 ### To Reserve 
 A string containing the UUID of a reserve.
 
-
+### Scan
+An account identifier composed of the following attributes:
+- String sortCode
+- String accountNumber

assets/images/automated_transfer/import_script.png

@@ -0,0 +1,32 @@
+---
+title: Automated Transfer
+parent: Example Scripts
+layout: page
+---
+
+```groovy
+trigger = "on_demand";
+
+
+def payer  = ${payer:scan};
+def payee = ${payee:scan};
+def amount = ${amount:decimal};
+
+def payment = PaymentInfo.builder()
+        .payer(AccountInfo.builder()
+                .type(AccountIdentifierType.SCAN)
+                .identifier(payer)
+                .build())
+        .payee(AccountInfo.builder()
+                .type(AccountIdentifierType.SCAN)
+                .identifier(payee)
+                .build())
+        .amountInfo(AmountInfo.builder()
+                .currency(CurrencyEnum.GBP)
+                .amount(amount)
+                .build())
+        .paymentReference("Automated transfer")
+        .build();
+
+def newPaymentId = createPayment(payment);
+```

assets/images/automated_transfer/run_automation_button.png

@@ -2,6 +2,4 @@
 title: Payscript
 layout: page
 nav_order: 2
----
-
-The 
+---

assets/images/automated_transfer/script_parameters.png

@@ -11,30 +11,11 @@ Payscript is a domain specific language (DSL) derived from Groovy. Using the Gro
 For Syntax, this version does not differ from Groovy. please consult the [Groovy syntax reference][groovy syntax]. 
 
 ## Script Structure
-A payscript is structured in such a way to best meet the needs of the architecture proposed by Quant Flow. During the script’s lifecycle it's expected to be deployed by developers into a collection, and to be made available to use with Automations. 
-
-[comment]: Add image 
-
-## Triggers
-Triggers specify which type of event will cause the script to run. They take parameters, which are only given during the creation of an Automation (not when the script is written or deployed). These are the types of triggers available:
-
-**time**: This trigger will cause the script to be run on a schedule, specified at the time when the automation is created. For example, daily at 14:00, or monthly on the first day of the month, at 00:00.
-
-**balance**: This trigger will cause the script to run whenever the balance oft  owns it is a certain number or above or below a specified number.
-
-**transaction**: This trigger will cause the script to run whenever a transaction happens on the account who owns the script.
-
-The actual values for these triggers (trigger parameters) will only be specified at the time when it is used in the creation of an automation.
-
-The trigger definition follows the syntax:
-
-trigger="[trigger]";
-
-where [trigger] is replaced by a trigger type name. Example: trigger="time";
-
+PayScript has two special structures, beyond the programming logic; A [trigger] definition and [script parameters]. The trigger specifies what type of event will cause the script to run. When an automation is created with the script, the parameters of the trigger will be specified. For example, if the script's trigger type is "time", the parameters would be which date and time it should run on.
+Also during the creation of the automation, the script parameters required by the script will be supplied.
 
 ## Parameters
-The script parameters are values which will be used by the script but will be specified by the user who creates an automation which uses this script. At that time they will be prompted for the values, much like the trigger parameters.
+The script parameters are values which will be used by the script but will be specified by the customer who creates an automation which uses this script. At that time they will be prompted for the values, much like the trigger parameters.
 
 Parameters are specified in the script using the following syntax:
 
@@ -49,4 +30,7 @@ The logic section contains what the script needs to accomplish, utilizing groovy
 
 
 [groovy syntax]: https://groovy-lang.org/single-page-documentation.html
-[built-in functions]: built_in_functions
+[built-in functions]: built_in_functions
+[callScript]: built_in_functions#callScript
+[trigger]: /docs/payscript/triggers
+[script parameters]: #parameters