Minor updates

WordPress · Mar 20, 2024 · 079088b · 079088b
1 parent dde4df9
commit 079088b
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 8 deletions.
diff --git a/README.md b/README.md
@@ -1,7 +1,7 @@
 # Performance Lab
 ![Performance Lab plugin banner with icon](https://user-images.githubusercontent.com/3531426/159084476-af352db4-192e-4927-a383-7f76bb3641df.png)
 
-Monorepo for the [WordPress Performance Team](https://make.wordpress.org/performance/), primarily for the Performance Lab plugin, which is a collection of standalone performance modules.
+Monorepo for the [WordPress Performance Team](https://make.wordpress.org/performance/), primarily for the Performance Lab plugin, which is a collection of standalone performance features.
 
 Details about the Performance Lab plugin, including instructions for getting started and contributing, are available in the [Performance Team Handbook here](https://make.wordpress.org/performance/handbook/performance-lab/).
 

diff --git a/admin/load.php b/admin/load.php
@@ -26,7 +26,7 @@ function perflab_add_features_page() {
 
 	// Add the following hooks only if the screen was successfully added.
 	if ( false !== $hook_suffix ) {
-		add_action( "load-{$hook_suffix}", 'perflab_load_settings_page', 10, 0 );
+		add_action( "load-{$hook_suffix}", 'perflab_load_features_page', 10, 0 );
 		add_filter( 'plugin_action_links_' . plugin_basename( PERFLAB_MAIN_FILE ), 'perflab_plugin_action_links_add_settings' );
 	}
 
@@ -38,10 +38,10 @@ function perflab_add_features_page() {
  * Initializes settings sections and fields for the modules page.
  *
  * @since 1.0.0
- * @since n.e.x.t Renamed to perflab_load_settings_page(), and the
+ * @since n.e.x.t Renamed to perflab_load_features_page(), and the
  *                $module and $hook_suffix parameters were removed.
  */
-function perflab_load_settings_page() {
+function perflab_load_features_page() {
 	// Handle script enqueuing for settings page.
 	add_action( 'admin_enqueue_scripts', 'perflab_enqueue_modules_page_scripts' );
 

diff --git a/composer.json b/composer.json
@@ -2,7 +2,7 @@
   "name": "wordpress/performance",
   "type": "wordpress-plugin",
   "license": "GPL-2.0-or-later",
-  "description": "Performance plugin from the WordPress Performance Team, which is a collection of standalone performance modules.",
+  "description": "Performance plugin from the WordPress Performance Team, which is a collection of standalone performance features.",
   "homepage": "https://wordpress.org/plugins/performance-lab/",
   "keywords": [
     "performance",

diff --git a/load.php b/load.php
@@ -2,7 +2,7 @@
 /**
  * Plugin Name: Performance Lab
  * Plugin URI: https://github.com/WordPress/performance
- * Description: Performance plugin from the WordPress Performance Team, which is a collection of standalone performance modules.
+ * Description: Performance plugin from the WordPress Performance Team, which is a collection of standalone performance features.
  * Requires at least: 6.4
  * Requires PHP: 7.0
  * Version: 2.9.0

diff --git a/readme.txt b/readme.txt
@@ -9,7 +9,7 @@ License:           GPLv2 or later
 License URI:       https://www.gnu.org/licenses/gpl-2.0.html
 Tags:              performance, images, javascript, site health, measurement, object caching
 
-Performance plugin from the WordPress Performance Team, which is a collection of standalone performance plugins.
+Performance plugin from the WordPress Performance Team, which is a collection of standalone performance features.
 
 == Description ==
 
@@ -42,7 +42,7 @@ The primary purpose of the Performance Lab plugin is to allow testing of various
 
 = Can I use this plugin on my production site? =
 
-Per the primary purpose of the plugin (see above), it can mostly be considered a beta testing plugin for the various performance modules it includes. However, unless a module is explicitly marked as "experimental", it has been tested and established to a degree where it should be okay to use in production. Still, as with every plugin, you are doing so at your own risk.
+Per the primary purpose of the plugin (see above), it can mostly be considered a beta testing plugin for the various performance features it includes. However, it's essential to understand that utilizing it comes with inherent risks. Users are encouraged to proceed with caution and understand that they are doing so at their own risk.
 
 = Where can I submit my plugin feedback? =