<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[44894] trunk/src/wp-includes: Docs: Correct various spelling mistakes.</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { white-space: pre-line; overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta" style="font-size: 105%">
<dt style="float: left; width: 6em; font-weight: bold">Revision</dt> <dd><a style="font-weight: bold" href="https://core.trac.wordpress.org/changeset/44894">44894</a><script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","description":"Review this Commit","action":{"@type":"ViewAction","url":"https://core.trac.wordpress.org/changeset/44894","name":"Review Commit"}}</script></dd>
<dt style="float: left; width: 6em; font-weight: bold">Author</dt> <dd>desrosj</dd>
<dt style="float: left; width: 6em; font-weight: bold">Date</dt> <dd>2019-03-13 19:31:49 +0000 (Wed, 13 Mar 2019)</dd>
</dl>
<pre style='padding-left: 1em; margin: 2em 0; border-left: 2px solid #ccc; line-height: 1.25; font-size: 105%; font-family: sans-serif'>Docs: Correct various spelling mistakes.
Props man4toman.
Fixes <a href="https://core.trac.wordpress.org/ticket/46339">#46339</a>.</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#trunksrcwpincludescachephp">trunk/src/wp-includes/cache.php</a></li>
<li><a href="#trunksrcwpincludesclassjsonphp">trunk/src/wp-includes/class-json.php</a></li>
<li><a href="#trunksrcwpincludesclasssmtpphp">trunk/src/wp-includes/class-smtp.php</a></li>
<li><a href="#trunksrcwpincludescommenttemplatephp">trunk/src/wp-includes/comment-template.php</a></li>
<li><a href="#trunksrcwpincludestaxonomyphp">trunk/src/wp-includes/taxonomy.php</a></li>
<li><a href="#trunksrcwpincludesthemephp">trunk/src/wp-includes/theme.php</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunksrcwpincludescachephp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/cache.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/cache.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/cache.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -646,7 +646,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> /**
</span><span class="cx" style="display: block; padding: 0 10px"> * Sets the data contents into the cache.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * The cache contents is grouped by the $group parameter followed by the
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * The cache contents are grouped by the $group parameter followed by the
</ins><span class="cx" style="display: block; padding: 0 10px"> * $key. This allows for duplicate ids in unique groups. Therefore, naming of
</span><span class="cx" style="display: block; padding: 0 10px"> * the group should be used with care and should follow normal function
</span><span class="cx" style="display: block; padding: 0 10px"> * naming guidelines outside of core WordPress usage.
</span></span></pre></div>
<a id="trunksrcwpincludesclassjsonphp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/class-json.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/class-json.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/class-json.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -805,7 +805,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> ($top['what'] == SERVICES_JSON_IN_STR) &&
</span><span class="cx" style="display: block; padding: 0 10px"> (($this->strlen8($this->substr8($chrs, 0, $c)) - $this->strlen8(rtrim($this->substr8($chrs, 0, $c), '\\'))) % 2 != 1)) {
</span><span class="cx" style="display: block; padding: 0 10px"> // found a quote, we're in a string, and it's not escaped
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- // we know that it's not escaped becase there is _not_ an
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ // we know that it's not escaped because there is _not_ an
</ins><span class="cx" style="display: block; padding: 0 10px"> // odd number of backslashes at the end of the string so far
</span><span class="cx" style="display: block; padding: 0 10px"> array_pop($stk);
</span><span class="cx" style="display: block; padding: 0 10px"> //print("Found end of string at {$c}: ".$this->substr8($chrs, $top['where'], (1 + 1 + $c - $top['where']))."\n");
</span></span></pre></div>
<a id="trunksrcwpincludesclasssmtpphp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/class-smtp.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/class-smtp.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/class-smtp.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -564,10 +564,10 @@
</span><span class="cx" style="display: block; padding: 0 10px"> /**
</span><span class="cx" style="display: block; padding: 0 10px"> * Send an SMTP DATA command.
</span><span class="cx" style="display: block; padding: 0 10px"> * Issues a data command and sends the msg_data to the server,
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * finializing the mail transaction. $msg_data is the message
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * finalizing the mail transaction. $msg_data is the message
</ins><span class="cx" style="display: block; padding: 0 10px"> * that is to be send with the headers. Each header needs to be
</span><span class="cx" style="display: block; padding: 0 10px"> * on a single line followed by a <CRLF> with the message headers
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * and the message body being separated by and additional <CRLF>.
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * and the message body being separated by an additional <CRLF>.
</ins><span class="cx" style="display: block; padding: 0 10px"> * Implements rfc 821: DATA <CRLF>
</span><span class="cx" style="display: block; padding: 0 10px"> * @param string $msg_data Message data to send
</span><span class="cx" style="display: block; padding: 0 10px"> * @access public
</span></span></pre></div>
<a id="trunksrcwpincludescommenttemplatephp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/comment-template.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/comment-template.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/comment-template.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -102,7 +102,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> * Display the email of the author of the current global $comment.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><span class="cx" style="display: block; padding: 0 10px"> * Care should be taken to protect the email address and assure that email
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * harvesters do not capture your commentors' email address. Most assume that
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * harvesters do not capture your commenter's email address. Most assume that
</ins><span class="cx" style="display: block; padding: 0 10px"> * their email address will not appear in raw form on the site. Doing so will
</span><span class="cx" style="display: block; padding: 0 10px"> * enable anyone, including those that people don't want to get the email
</span><span class="cx" style="display: block; padding: 0 10px"> * address and use it for their own means good and bad.
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -133,7 +133,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> * Display the html email link to the author of the current comment.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><span class="cx" style="display: block; padding: 0 10px"> * Care should be taken to protect the email address and assure that email
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * harvesters do not capture your commentors' email address. Most assume that
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * harvesters do not capture your commenter's email address. Most assume that
</ins><span class="cx" style="display: block; padding: 0 10px"> * their email address will not appear in raw form on the site. Doing so will
</span><span class="cx" style="display: block; padding: 0 10px"> * enable anyone, including those that people don't want to get the email
</span><span class="cx" style="display: block; padding: 0 10px"> * address and use it for their own means good and bad.
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -157,7 +157,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> * Return the html email link to the author of the current comment.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><span class="cx" style="display: block; padding: 0 10px"> * Care should be taken to protect the email address and assure that email
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * harvesters do not capture your commentors' email address. Most assume that
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * harvesters do not capture your commenter's email address. Most assume that
</ins><span class="cx" style="display: block; padding: 0 10px"> * their email address will not appear in raw form on the site. Doing so will
</span><span class="cx" style="display: block; padding: 0 10px"> * enable anyone, including those that people don't want to get the email
</span><span class="cx" style="display: block; padding: 0 10px"> * address and use it for their own means good and bad.
</span></span></pre></div>
<a id="trunksrcwpincludestaxonomyphp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/taxonomy.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/taxonomy.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/taxonomy.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -2666,7 +2666,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> * The way this works is that if the taxonomy that the term belongs to is
</span><span class="cx" style="display: block; padding: 0 10px"> * hierarchical and has a parent, it will append that parent to the $slug.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * If that still doesn't return an unique slug, then it try to append a number
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * If that still doesn't return a unique slug, then it tries to append a number
</ins><span class="cx" style="display: block; padding: 0 10px"> * until it finds a number that is truly unique.
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><span class="cx" style="display: block; padding: 0 10px"> * The only purpose for `$term` is for appending a parent, if one exists.
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -4127,7 +4127,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> *
</span><span class="cx" style="display: block; padding: 0 10px"> * @param int $term_id Term ID.
</span><span class="cx" style="display: block; padding: 0 10px"> * @return bool Returns false if a term is not shared between multiple taxonomies or
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * if splittng shared taxonomy terms is finished.
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * if splitting shared taxonomy terms is finished.
</ins><span class="cx" style="display: block; padding: 0 10px"> */
</span><span class="cx" style="display: block; padding: 0 10px"> function wp_term_is_shared( $term_id ) {
</span><span class="cx" style="display: block; padding: 0 10px"> global $wpdb;
</span></span></pre></div>
<a id="trunksrcwpincludesthemephp"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/src/wp-includes/theme.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/src/wp-includes/theme.php 2019-03-13 01:59:57 UTC (rev 44893)
+++ trunk/src/wp-includes/theme.php 2019-03-13 19:31:49 UTC (rev 44894)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -3057,7 +3057,7 @@
</span><span class="cx" style="display: block; padding: 0 10px"> * Trash the changeset post if revisions are not enabled. Unpublished
</span><span class="cx" style="display: block; padding: 0 10px"> * changesets by default get garbage collected due to the auto-draft status.
</span><span class="cx" style="display: block; padding: 0 10px"> * When a changeset post is published, however, it would no longer get cleaned
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">- * out. Ths is a problem when the changeset posts are never displayed anywhere,
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+ * out. This is a problem when the changeset posts are never displayed anywhere,
</ins><span class="cx" style="display: block; padding: 0 10px"> * since they would just be endlessly piling up. So here we use the revisions
</span><span class="cx" style="display: block; padding: 0 10px"> * feature to indicate whether or not a published changeset should get trashed
</span><span class="cx" style="display: block; padding: 0 10px"> * and thus garbage collected.
</span></span></pre>
</div>
</div>
</body>
</html>