From aac252d7926a35417f38e2ba5e7e5329dbd58ddf Mon Sep 17 00:00:00 2001 From: Daniel Richards Date: Tue, 20 Jun 2023 17:19:57 +0800 Subject: [PATCH] Fix typo --- docs/reference-guides/block-api/block-patterns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference-guides/block-api/block-patterns.md b/docs/reference-guides/block-api/block-patterns.md index f6d80d5e1acd8e..a1da09d63a6c99 100644 --- a/docs/reference-guides/block-api/block-patterns.md +++ b/docs/reference-guides/block-api/block-patterns.md @@ -36,7 +36,7 @@ The properties available for block patterns are: - `postTypes` (optional): An array of post types that the pattern is restricted to be used with. The pattern will only be available when editing one of the post types passed on the array, for all the other post types the pattern is not available at all. - `templateTypes` (optional): An array of template types where the pattern makes sense e.g: '404' if the pattern is for a 404 page, single-post if the pattern is for showing a single post. - `inserter` (optional): By default, all patterns will appear in the inserter. To hide a pattern so that it can only be inserted programmatically, set the `inserter` to `false`. -- `source` (optional): A string that denotes the source of the pattern. For a plugin registering a pattern, pass the string 'pattern'. For a theme, pass the string 'theme'. +- `source` (optional): A string that denotes the source of the pattern. For a plugin registering a pattern, pass the string 'plugin'. For a theme, pass the string 'theme'. The following code sample registers a block pattern named 'my-plugin/my-awesome-pattern':