Update qute-reference.adoc

Fix markup in examples and a couple of typos (cherry picked from commit ecc32b7)
quarkusio · Jan 18, 2024 · 93c6490 · 93c6490
1 parent d5d162e
commit 93c6490
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/src/main/asciidoc/qute-reference.adoc b/docs/src/main/asciidoc/qute-reference.adoc
@@ -223,7 +223,7 @@ Likewise, a line that contains an _expression_ or a _non-whitespace character_ i
                           <3>
      {/for}               <4>
      </ul>
-   <body>
+   </body>
 </html>
 ----
 <1> This is a standalone line and will be removed.
@@ -240,7 +240,7 @@ Likewise, a line that contains an _expression_ or a _non-whitespace character_ i
        <li>Foo 100</li>
 
      </ul>
-   <body>
+   </body>
 </html>
 ----
 
@@ -258,7 +258,7 @@ In this case, all whitespace characters from a standalone line will be printed t
 
 
      </ul>
-   <body>
+   </body>
 </html>
 ----
 
@@ -273,7 +273,7 @@ In the `object.property` (dot notation) syntax, the `property` must be a <<ident
 In the `object[property_name]` (bracket notation) syntax, the `property_name` has to be a non-null <<literals,literal>> value.
 
 An expression can start with an optional namespace followed by a colon (`:`).
-A valid namespace consist of alphanumeric characters and underscores.
+A valid namespace consists of alphanumeric characters and underscores.
 Namespace expressions are resolved differently - see also <<expression_resolution>>.
 
 .Property Accessor Examples
@@ -336,7 +336,7 @@ You can learn more about virtual methods in the <<virtual_methods,following sect
 ==== Resolution
 
 The first part of the expression is always resolved against the <<current_context_object,current context object>>.
-If no result is found for the first part it's resolved against the parent context object (if available).
+If no result is found for the first part, it's resolved against the parent context object (if available).
 For an expression that starts with a namespace the current context object is found using all the available ``NamespaceResolver``s.
 For an expression that does not start with a namespace the current context object is *derived from the position* of the tag.
 All other parts of an expression are resolved using all ``ValueResolver``s against the result of the previous resolution.
@@ -1426,7 +1426,7 @@ template.data(foo).createUni().subscribe().with(System.out::println);
 `TemplateInstance.createMulti()` returns a new `Multi<String>` object.
 Each item represents a part/chunk of the rendered template.
 Again, `createMulti()` does not trigger rendering.
-Instead, every time a computation is triggered by a subscriber the template is rendered again.
+Instead, every time a computation is triggered by a subscriber, the template is rendered again.
 
 .`TemplateInstance.createMulti()` Example
 [source,java]