sergiotarxz/Wordpress
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Docs: Use markdown instead of HTML for code formatting.

Browse Source 
Fixes phpdoc usage in [36622], [36608], [35724], [35307].

See #35898.
See #35869.
See #34738.
See #33552.


git-svn-id: https://develop.svn.wordpress.org/trunk@36645 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Weston Ruter 2016-02-23 19:17:11 +00:00
parent cab3a242f7
commit 773151a9bf
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/wp-includes/class-wp-customize-manager.php
View File

@ -246,7 +246,7 @@ final class WP_Customize_Manager {
*
* This allows Core components to be excluded from being instantiated by
* filtering them out of the array. Note that this filter generally runs
* during the <code>plugins_loaded</code> action, so it cannot be added
* during the `plugins_loaded` action, so it cannot be added
* in a theme.
*
* @since 4.4.0
@ -703,7 +703,7 @@ final class WP_Customize_Manager {
*
* Fires when the {@see WP_Customize_Manager::set_post_value()} method is called.
*
* This is useful for <code>WP_Customize_Setting</code> instances to watch
* This is useful for `WP_Customize_Setting` instances to watch
* in order to update a cached previewed value.
*
* @since 4.4.0

2
src/wp-includes/class-wp-customize-setting.php
View File

@ -358,7 +358,7 @@ class WP_Customize_Setting {
* Clear out the previewed-applied flag for a multidimensional-aggregated value whenever its post value is updated.
*
* This ensures that the new value will get sanitized and used the next time
* that <code>WP_Customize_Setting::_multidimensional_preview_filter()</code>
* that `WP_Customize_Setting::_multidimensional_preview_filter()`
* is called for this setting.
*
* @since 4.4.0

6
src/wp-includes/nav-menu.php
View File

@ -196,7 +196,7 @@ function is_nav_menu_item( $menu_item_id = 0 ) {
/**
* Creates a navigation menu.
*
* Note that <code>$menu_name</code> is expected to be pre-slashed.
* Note that `$menu_name` is expected to be pre-slashed.
*
* @since 3.0.0
*
@ -255,7 +255,7 @@ function wp_delete_nav_menu( $menu ) {
/**
* Save the properties of a menu or create a new menu with those properties.
*
* Note that <code>$menu_data</code> is expected to be pre-slashed.
* Note that `$menu_data` is expected to be pre-slashed.
*
* @since 3.0.0
*
@ -351,7 +351,7 @@ function wp_update_nav_menu_object( $menu_id = 0, $menu_data = array() ) {
* Save the properties of a menu item or create a new one.
*
* The menu-item-title, menu-item-description, and menu-item-attr-title are expected
* to be pre-slashed since they are passed directly into <code>wp_insert_post()</code>.
* to be pre-slashed since they are passed directly into `wp_insert_post()`.
*
* @since 3.0.0
*