Merge branch 'main' into patch-1

Author: fabiankaegy

reference/03-Blocks/block-transforms.md

@@ -12,7 +12,7 @@ This is super useful to allow editors to quickly switch between different types
 
 ## When to use Block Transforms
 
-In theory most blocks should have block transformations defined. They make the live of the editors much easier. With the ability to transform one block into another one this can also be leveraged in order to not build overly complex blocks with too many options. Instead it is often easier and faster to build two separate blocks and allow the user to transform between them.
+In theory most blocks should have block transformations defined. They make the lives of the editors much easier. With the ability to transform one block into another one this can also be leveraged in order to not build overly complex blocks with too many options. Instead it is often easier and faster to build two separate blocks and allow the user to transform between them.
 
 Finally one more use-case is using the transforms in order to add a controlled update path for users. Let's imagine you have a project where you build a block two different blocks that work in slightly different ways. Further down the line in the project you find that the client now has new requirements that make these two blocks obsolete. Instead they want to replace the two blocks with one that can solve for both use-cases at the same time.
 

training/04-patterns.md

@@ -97,7 +97,7 @@ In the paragraph for example the text content within the `p` tag is automaticall
 The `className` attribute on the other hand is impossible to parse because there may be other classnames coming from the block itself or some extension that only works when the attribute is stored in the JSON object.
 </details>
 
-Since WordPress 6.0 patterns can be registered super easily by _just_ creating a PHP file inside the `pattern` folder at the root directory of a theme. This PHP file needs to have a comment header with some metadata and then just the markup of the blocks themselves.
+Since WordPress 6.0 patterns can be registered super easily by _just_ creating a PHP file inside the `patterns` folder at the root directory of a theme. This PHP file needs to have a comment header with some metadata and then just the markup of the blocks themselves.
 
 ### Pattern document headers