Make WordPress Core


Ignore:
Timestamp:
01/17/2023 09:32:42 PM (21 months ago)
Author:
audrasjb
Message:

Administration: Use a consistent capitalization in Privacy Policy related strings.

This changeset fixes a few use case:

  • When referring to the Privacy Policy page, "Privacy Policy" should use capitalization on "Privacy Policy", but "page" should remain lowercase;
  • When referring to the fact that a website needs, let's say "a relevant privacy policy", "privacy policy" should stay lowercase.

This changeset also updates other small capitalization issues.

Props aravindajith, audrasjb, sarathar, nithi22, costdev.
Fixes #57226.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-admin/options-privacy.php

    r53156 r55082  
    182182    <h2><?php _e( 'Privacy Settings' ); ?></h2>
    183183    <p>
    184         <?php _e( 'As a website owner, you may need to follow national or international privacy laws. For example, you may need to create and display a Privacy Policy.' ); ?>
     184        <?php _e( 'As a website owner, you may need to follow national or international privacy laws. For example, you may need to create and display a privacy policy.' ); ?>
    185185        <?php _e( 'If you already have a Privacy Policy page, please select it below. If not, please create one.' ); ?>
    186186    </p>
    187187    <p>
    188         <?php _e( 'The new page will include help and suggestions for your Privacy Policy.' ); ?>
    189         <?php _e( 'However, it is your responsibility to use those resources correctly, to provide the information that your Privacy Policy requires, and to keep that information current and accurate.' ); ?>
     188        <?php _e( 'The new page will include help and suggestions for your privacy policy.' ); ?>
     189        <?php _e( 'However, it is your responsibility to use those resources correctly, to provide the information that your privacy policy requires, and to keep that information current and accurate.' ); ?>
    190190    </p>
    191191    <p>
    192192        <?php _e( 'After your Privacy Policy page is set, you should edit it.' ); ?>
    193         <?php _e( 'You should also review 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.' ); ?>
     193        <?php _e( 'You should also review 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.' ); ?>
    194194    </p>
    195195    <p>
     
    228228        printf(
    229229            /* translators: 1: Privacy Policy guide URL, 2: Additional link attributes, 3: Accessibility text. */
    230             __( 'Need help putting together your new Privacy Policy page? <a href="%1$s" %2$s>Check out our Privacy Policy guide%3$s</a> for recommendations on what content to include, along with policies suggested by your plugins and theme.' ),
     230            __( 'Need help putting together your new Privacy Policy page? <a href="%1$s" %2$s>Check out our privacy policy guide%3$s</a> for recommendations on what content to include, along with policies suggested by your plugins and theme.' ),
    231231            esc_url( admin_url( 'options-privacy.php?tab=policyguide' ) ),
    232232            '',
     
    254254                <?php
    255255                if ( $has_pages ) {
    256                     _e( 'Create a new Privacy Policy Page' );
     256                    _e( 'Create a new Privacy Policy page' );
    257257                } else {
    258258                    _e( 'There are no pages.' );
Note: See TracChangeset for help on using the changeset viewer.