Clarify signatory usage (digital-asset#6204)

* Clarify signatory usage * Address review comments * Double backticks per review Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org> * Update docs/source/daml/reference/templates.rst Co-authored-by: Gerolf Seitz <gerolf.seitz@daml.com> Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org> Co-authored-by: Gerolf Seitz <gerolf.seitz@daml.com>
kgeonw · Jun 8, 2020 · 1836905 · 1836905
1 parent f2d0679
commit 1836905
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/source/daml/reference/templates.rst b/docs/source/daml/reference/templates.rst
@@ -71,7 +71,7 @@ Signatory parties
   ``NameOfTemplate requires authorizers Party1,Party2,Party, but only Party1 were given.``
 - When a signatory consents to the contract creation, this means they also authorize the consequences of :ref:`choices <daml-ref-choices>` that can be exercised on this contract.
 - The contract instance is visible to all signatories (as well as the other stakeholders of the contract). That is, the compiler automatically adds signatories as observers.
-- You **must** have least one signatory per template. You can have many, either as a comma-separated list or reusing the keyword. You could pass in a list (of type ``[Party]``).
+- Each template **must** have at least one signatory. A signatory declaration consists of the `signatory` keyword followed by a comma-separated list of one or more expressions, each expression denoting a ``Party`` or collection thereof.
 
 .. _daml-ref-observers: