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

Docs: Remove "the the" dittography from inline comments.

Browse Source 
Props Presskopp.
Fixes #41835.

git-svn-id: https://develop.svn.wordpress.org/trunk@41350 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Sergey Biryukov 2017-09-08 18:20:22 +00:00
parent a55222fe0f
commit 357532ab64
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/wp-admin/js/widgets/media-widgets.js
View File

@ -1069,7 +1069,7 @@ wp.mediaWidgets = ( function( $ ) {
/* /*
* Create a container element for the widget control (Backbone.View). * Create a container element for the widget control (Backbone.View).
* This is inserted into the DOM immediately before the the .widget-content * This is inserted into the DOM immediately before the .widget-content
* element because the contents of this element are essentially "managed" * element because the contents of this element are essentially "managed"
* by PHP, where each widget update cause the entire element to be emptied * by PHP, where each widget update cause the entire element to be emptied
* and replaced with the rendered output of WP_Widget::form() which is * and replaced with the rendered output of WP_Widget::form() which is

2
src/wp-admin/js/widgets/text-widgets.js
View File

@ -388,7 +388,7 @@ wp.textWidgets = ( function( $ ) {
/* /*
* Create a container element for the widget control fields. * Create a container element for the widget control fields.
* This is inserted into the DOM immediately before the the .widget-content * This is inserted into the DOM immediately before the .widget-content
* element because the contents of this element are essentially "managed" * element because the contents of this element are essentially "managed"
* by PHP, where each widget update cause the entire element to be emptied * by PHP, where each widget update cause the entire element to be emptied
* and replaced with the rendered output of WP_Widget::form() which is * and replaced with the rendered output of WP_Widget::form() which is

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

@ -4107,7 +4107,7 @@ final class WP_Customize_Manager {
/* /*
* Static Front Page * Static Front Page
* See also https://core.trac.wordpress.org/ticket/19627 which introduces the the static-front-page theme_support. * See also https://core.trac.wordpress.org/ticket/19627 which introduces the static-front-page theme_support.
* The following replicates behavior from options-reading.php. * The following replicates behavior from options-reading.php.
*/ */

2
src/wp-includes/theme.php
View File

@ -2904,7 +2904,7 @@ function _wp_customize_publish_changeset( $new_status, $old_status, $changeset_p
/* /*
* The following re-formulates the logic from wp_trash_post() as done in * The following re-formulates the logic from wp_trash_post() as done in
* wp_publish_post(). The reason for bypassing wp_trash_post() is that it * wp_publish_post(). The reason for bypassing wp_trash_post() is that it
* will mutate the the post_content and the post_name when they should be * will mutate the post_content and the post_name when they should be
* untouched. * untouched.
*/ */
if ( ! EMPTY_TRASH_DAYS ) { if ( ! EMPTY_TRASH_DAYS ) {