From 360c8ea6e47062725d85fdeb5276b8e15d6f8d8a Mon Sep 17 00:00:00 2001 From: LeeRobertsMe Date: Thu, 8 Oct 2015 13:35:24 +0100 Subject: [PATCH] Update plugin-name-admin.js --- plugin-name/admin/js/plugin-name-admin.js | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/plugin-name/admin/js/plugin-name-admin.js b/plugin-name/admin/js/plugin-name-admin.js index 864fdb2..071048d 100644 --- a/plugin-name/admin/js/plugin-name-admin.js +++ b/plugin-name/admin/js/plugin-name-admin.js @@ -2,31 +2,31 @@ 'use strict'; /** - * All of the code for your admin-specific JavaScript source + * All of the code for your public-facing JavaScript source * should reside in this file. * - * Note that this assume you're going to use jQuery, so it prepares - * the $ function reference to be used within the scope of this - * function. + * Note: It has been assumed you will write jQuery code here, so the + * $ function reference has been prepared for usage within the scope + * of this function. * - * From here, you're able to define handlers for when the DOM is - * ready: + * This enables you to define handlers, for when the DOM is ready: * * $(function() { * * }); * - * Or when the window is loaded: + * When the window is loaded: * * $( window ).load(function() { * * }); * - * ...and so on. + * ...and/or other possibilities. * - * Remember that ideally, we should not attach any more than a single DOM-ready or window-load handler - * for any particular page. Though other scripts in WordPress core, other plugins, and other themes may - * be doing this, we should try to minimize doing that in our own work. + * Ideally, it is not considered best practise to attach more than a + * single DOM-ready or window-load handler for a particular page. + * Although scripts in the WordPress core, Plugins and Themes may be + * practising this, we should strive to set a better example in our own work. */ })( jQuery );