Docs: Avoid using “CPT” instead of “custom post type”.

Additionally, when referring to built in Core post types, “custom” is unnecessary.

This also adds a period to the end of the `wp_global_styles` post type description.

Follow up to [38829], [51003], [52041], [52049], [52062].

See #53399, #54335, #54336.

git-svn-id: https://develop.svn.wordpress.org/trunk@52110 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Jonathan Desrosiers
2021-11-10 14:16:03 +00:00
parent 663666d6a4
commit c59c7dd5f9
5 changed files with 9 additions and 9 deletions
@@ -190,16 +190,16 @@ class WP_Theme_JSON_Resolver {
}
/**
* Returns the CPT that contains the user's origin config
* for the current theme or a void array if none found.
* Returns the custom post type that contains the user's origin config
* for the current theme or a void array if none are found.
*
* It can also create and return a new draft CPT.
* This can also create and return a new draft custom post type.
*
* @since 5.9.0
*
* @param bool $should_create_cpt Optional. Whether a new CPT should be created if no one was found.
* @param bool $should_create_cpt Optional. Whether a new custom post type should be created if none are found.
* False by default.
* @param array $post_status_filter Filter Optional. CPT by post status.
* @param array $post_status_filter Filter Optional. custom post type by post status.
* ['publish'] by default, so it only fetches published posts.
*
* @return array Custom Post Type for the user's origin config.