From a49526649da54403c5e743bccc8b7a73b5f735e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philip=20K=2EF=2E=20H=C3=B6lzenspies?= Date: Tue, 13 Feb 2024 21:22:55 +0000 Subject: [PATCH] Update docs/modules/language-tutorial/pages/02_filling_out_a_template.adoc --- .../language-tutorial/pages/02_filling_out_a_template.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/language-tutorial/pages/02_filling_out_a_template.adoc b/docs/modules/language-tutorial/pages/02_filling_out_a_template.adoc index 4c19f886..5414d6fe 100644 --- a/docs/modules/language-tutorial/pages/02_filling_out_a_template.adoc +++ b/docs/modules/language-tutorial/pages/02_filling_out_a_template.adoc @@ -385,7 +385,7 @@ If the name `foo` didn't occur before, `foo { ... }` _creates_ a property called If `foo` is an existing object, this notation is an _amend expression_; resulting in a new _object_ (value), but _not_ a new (named) property. Since `pipelines` is a listing, you can _add_ elements by writing expressions in an amend expression. -In this case, though, there is no object to amend. Writing `pipelines { ... }` defines a _property_, but listings may only include _elements_. +In this case, though, there is no object to amend. Writing `myNewPipeline { ... }` defines a _property_, but listings may only include _elements_. This is where you can use the keyword `new`. `new` gives you an object to amend.