[wp-trac] [WordPress Trac] #46057: Remove self-references ("we") in text in core

[WordPress Trac]

#46057: Remove self-references ("we") in text in core
------------------------------+----------------------
 Reporter:  johnbillion       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  5.9
Component:  Administration    |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  ui-copy
------------------------------+----------------------

Comment (by peterwilsoncc):

 I did a regex search in vscode for `we[^a-z]` and found a few additional
 strings containing we:


 {{{
 After your Privacy Policy page is set, we suggest that you edit it.

 Don’t you wish all software came with these freedoms? So do we! For
 more information, check out the <a href="https://www.fsf.org/">Free
 Software Foundation</a>.

 Every plugin and theme in WordPress.org’s directory is 100%% GPL or
 a similarly free and compatible license, so you can feel safe finding <a
 href="%1$s">plugins</a> and <a href="%2$s">themes</a> there. If you get a
 plugin or theme from another source, make sure to <a href="%3$s">ask them
 if it’s GPL</a> first. If they don’t respect the WordPress
 license, we don’t recommend them.

 If the root directory of your site was <a href="%1$s">writable</a>, we
 could do this automatically, but it isn’t so this is the url rewrite
 rule you should have in your %2$s file. Create a new file, called %2$s in
 the root directory of your site. Click in the field and press %3$s to
 select all. Then insert this code into the %2$s file.

 If your %1$s file was <a href="%2$s">writable</a>, we could do this
 automatically, but it isn’t so these are the mod_rewrite rules you
 should have in your %1$s file. Click in the field and press %3$s to select
 all.

 If your %1$s file was <a href="%2$s">writable</a>, we could do this
 automatically, but it isn’t so this is the url rewrite rule you
 should have in your %1$s file. Click in the field and press %3$s to select
 all. Then insert this rule inside of the %4$s element in %1$s file.

 It seems we can’t find what you’re looking for. Perhaps
 searching can help.

 Need more help? <a href="%s">We got it</a>.

 Sorry, we can’t load the video at the supplied URL. Please check
 that the URL is for a supported video file (%s) or stream (e.g. YouTube
 and Vimeo).

 This format, which we call WordPress eXtended RSS or WXR, will contain
 your posts, pages, comments, custom fields, categories, and tags.

 This means that we lost contact with the database server at %s. This could
 mean your host’s database server is down.

 We already have a ping from that URL for this post.

 We can’t find that audio file. Check your <a href="%s">media
 library</a> and make sure it wasn’t deleted.

 We can’t find that file. Check your <a href="%s">media library</a>
 and make sure it wasn’t deleted.

 We can’t find that image. Check your <a href="%s">media library</a>
 and make sure it wasn’t deleted.

 We can’t find that video. Check your <a href="%s">media library</a>
 and make sure it wasn’t deleted.

 We couldn’t locate %s. Please try another nearby city. For example: Kansas
 City; Springfield; Portland.

 We have suggested the sections you will need. Under each section heading
 you will find a short summary of what information you should provide,
 which will help you to get started. Some sections include suggested policy
 content, others will have to be completed with information from your theme
 and plugins.

 We send your registration email to this address. (Double-check your email
 address before continuing.)

 We were able to connect to the database server (which means your username
 and password is okay) but not able to select the %s database.

 We would also suggest reviewing your Privacy Policy from time to time,
 especially after installing or updating any themes or plugins. There may
 be changes or new suggested information for you to consider adding to your
 policy.

 We’re backing up this post in your browser, just in case.'
 'We’re going to use this information to create a %s file.

 Welcome to WordPress. Before getting started, we need some information on
 the database. You will need to know the following items before proceeding.

 WordPress grows when people like you tell their friends about it, and the
 thousands of businesses and services that are built on and around
 WordPress share that fact with their users. We’re flattered every
 time someone spreads the good word, just make sure to <a href="%s">check
 out our trademark guidelines</a> first.
 }}}


 In docs I also found the we in the following files:
 * src/js/_enqueues/vendor/README.md
 * src/readme.html
 * CONTRIBUTING.md
 * SECURITY.md

 ----

 There's quite a few comments with we in it, so there is a good chance I
 have missed a few instances.

 If we (the people discussion the phrase on this ticket) wish to commit
 what we have and come back to some of these strings, then that works for
 me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46057#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform