Changeset 52110 for trunk/src/wp-includes/class-wp-theme-json-resolver.php

Timestamp:

11/10/2021 02:16:03 PM (3 years ago)

Author:

desrosj

Message:

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.

File:

• trunk/src/wp-includes/class-wp-theme-json-resolver.php (modified) (1 diff)

trunk/src/wp-includes/class-wp-theme-json-resolver.php

@@ -191 +191 @@
 
     /**
-     * Returns the CPT that contains the user's origin config
-     * for the current theme or a void array if none found.
-     *
-     * It can also create and return a new draft CPT.
+     * Returns the custom post type that contains the user's origin config
+     * for the current theme or a void array if none are found.
+     *
+     * 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.
      *