Commit e775d664 authored by alexpott's avatar alexpott

Issue #1971208 by calebtr, dsayswhat, metzlerd, agentrickard: Replace "utilize" with a proper verb.

parent b56718de
......@@ -132,7 +132,7 @@ Drupal 8.0, xxxx-xx-xx (development version)
Drupal 7.0, 2011-01-05
----------------------
- Database:
* Fully rewritten database layer utilizing PHP 5's PDO abstraction layer.
* Fully rewritten database layer using PHP 5's PDO abstraction layer.
* Drupal now requires MySQL >= 5.0.15 or PostgreSQL >= 8.3.
* Added query builders for INSERT, UPDATE, DELETE, MERGE, and SELECT queries.
* Support for primary/replica replication, transactions, multi-insert
......
......@@ -124,7 +124,7 @@ following the instructions in the INTRODUCTION section at the top of this file:
MAJOR VERSION MIGRATION
-----------------------
Upgrading from a prior major version of Drupal to Drupal 8.x is not possible.
The process now requires a migration to a Drupal 8.x site, utilizing the Migrate
The process now requires a migration to a Drupal 8.x site, using the Migrate
module in Drupal core.
Note that migration support in Drupal 8 is currently only partially implemented.
......@@ -1768,7 +1768,7 @@ function template_preprocess_html(&$variables) {
*
* Default template: page.html.twig.
*
* Most themes utilize their own copy of page.html.twig. The default is located
* Most themes use their own copy of page.html.twig. The default is located
* inside "modules/system/page.html.twig". Look in there for the full list of
* variables.
*
......
......@@ -12,8 +12,8 @@
/**
* Defines a Plugin annotation object.
*
* Annotations in plugin classes can utilize this class in order to pass
* various metadata about the plugin through the parser to
* Annotations in plugin classes can use this class in order to pass various
* metadata about the plugin through the parser to
* DiscoveryInterface::getDefinitions() calls. This allows the metadata
* of a class to be located with the class itself, rather than in module-based
* info hooks.
......
......@@ -26,8 +26,8 @@ class SettingsCommand implements CommandInterface {
/**
* An array of key/value pairs of JavaScript settings.
*
* This will be utilized for all commands after this if they do not include
* their own settings array.
* This will be used for all commands after this if they do not include their
* own settings array.
*
* @var array
*/
......
......@@ -43,7 +43,7 @@ abstract class ConfigEntityBase extends Entity implements ConfigEntityInterface
/**
* The name of the property that is used to store plugin configuration.
*
* This is needed when the entity utilizes a LazyPluginCollection, to dictate
* This is needed when the entity uses a LazyPluginCollection, to dictate
* where the plugin configuration should be stored.
*
* @var string
......
......@@ -8,7 +8,7 @@
namespace Drupal\Core\Entity;
/**
* Provides an interface for an object utilizing a plugin collection.
* Provides an interface for an object using a plugin collection.
*
* @see \Drupal\Component\Plugin\LazyPluginCollection
*
......
......@@ -570,9 +570,9 @@ function node_theme_suggestions_node(array $variables) {
*
* Default template: node.html.twig.
*
* Most themes utilize their own copy of node.html.twig. The default is located
* inside "/core/modules/node/templates/node.html.twig". Look in there for the full
* list of variables.
* Most themes use their own copy of node.html.twig. The default is located
* inside "/core/modules/node/templates/node.html.twig". Look in there for the
* full list of variables.
*
* @param array $variables
* An associative array containing:
......
......@@ -35,8 +35,8 @@ public function acquireGrants(NodeInterface $node);
* Writes a list of grants to the database, deleting any previously saved ones.
*
* If a realm is provided, it will only delete grants from that realm, but it
* will always delete a grant from the 'all' realm. Modules that utilize
* node access can use this function when doing mass updates due to widespread
* will always delete a grant from the 'all' realm. Modules that use node
* access can use this function when doing mass updates due to widespread
* permission changes.
*
* Note: Don't call this function directly from a contributed module. Call
......
......@@ -1535,13 +1535,13 @@
* would be an in-memory queue backend which might lose items if it crashes.
* However, such a backend would be able to deal with significantly more writes
* than a reliable queue and for many tasks this is more important. See
* aggregator_cron() for an example of how to effectively utilize a
* non-reliable queue. Another example is doing Twitter statistics -- the small
* possibility of losing a few items is insignificant next to power of the
* queue being able to keep up with writes. As described in the processing
* section, regardless of the queue being reliable or not, the processing code
* should be aware that an item might be handed over for processing more than
* once (because the processing code might time out before it finishes).
* aggregator_cron() for an example of how to effectively use a non-reliable
* queue. Another example is doing Twitter statistics -- the small possibility
* of losing a few items is insignificant next to power of the queue being able
* to keep up with writes. As described in the processing section, regardless
* of the queue being reliable or not, the processing code should be aware that
* an item might be handed over for processing more than once (because the
* processing code might time out before it finishes).
* @}
*/
......
......@@ -79,7 +79,7 @@ function testEnableTargetLogging() {
}
/**
* Tests that logs to separate targets utilize the same connection properly.
* Tests that logs to separate targets use the same connection properly.
*
* This test is identical to the one above, except that it doesn't create
* a fake target so the query should fall back to running on the default
......
......@@ -19,7 +19,7 @@
* information about render arrays and rendering.
*
* @section sec_twig_theme Twig Templating Engine
* Drupal 8 utilizes the templating engine Twig. Twig offers developers a fast,
* Drupal 8 uses the templating engine Twig. Twig offers developers a fast,
* secure, and flexible method for building templates for Drupal 8 sites. Twig
* also offers substantial usability improvements over PHPTemplate, and does
* not require front-end developers to know PHP to build and manipulate Drupal
......
......@@ -82,7 +82,7 @@ public function getViewsData() {
$data['users_field_data']['name']['help'] = t('The user or author name.');
$data['users_field_data']['name']['field']['id'] = 'user_name';
$data['users_field_data']['name']['filter']['title'] = t('Name (raw)');
$data['users_field_data']['name']['filter']['help'] = t('The user or author name. This filter does not check if the user exists and allows partial matching. Does not utilize autocomplete.');
$data['users_field_data']['name']['filter']['help'] = t('The user or author name. This filter does not check if the user exists and allows partial matching. Does not use autocomplete.');
// Note that this field implements field level access control.
$data['users_field_data']['mail']['help'] = t('Email address for a given user. This field is normally not shown to users, so be cautious when using it.');
......
......@@ -95,7 +95,7 @@ protected function initializePlugin($display_id) {
$this->pluginInstances[$display_id]->initDisplay($this->view, $display);
// If this is not the default display handler, let it know which is since
// it may well utilize some data from the default.
// it may well use some data from the default.
if ($display_id != 'default') {
$this->pluginInstances[$display_id]->default_display = $this->pluginInstances['default'];
}
......
......@@ -103,7 +103,7 @@ public function getField($field = NULL);
*
* This gives all the handlers some time to modify values. This is primarily
* used so that handlers that pull up secondary data can put it in the
* $values so that the raw data can be utilized externally.
* $values so that the raw data can be used externally.
*/
public function postExecute(&$values);
......
......@@ -32,14 +32,14 @@
* Simple relationship handler that allows a new version of the primary table
* to be linked in.
*
* The base relationship handler can only handle a single join. Some relationships
* are more complex and might require chains of joins; for those, you must
* utilize a custom relationship handler.
* The base relationship handler can only handle a single join. Some
* relationships are more complex and might require chains of joins; for those,
* you must use a custom relationship handler.
*
* Definition items:
* - base: The new base table this relationship will be adding. This does not
* have to be a declared base table, but if there are no tables that
* utilize this base table, it won't be very effective.
* use this base table, it won't be very effective.
* - base field: The field to use in the relationship; if left out this will be
* assumed to be the primary field.
* - relationship table: The actual table this relationship operates against.
......@@ -86,7 +86,8 @@ public function usesGroupBy() {
protected function defineOptions() {
$options = parent::defineOptions();
// Relationships definitions should define a default label, but if they aren't get another default value.
// Relationships definitions should define a default label, but if they
// aren't get another default value.
if (!empty($this->definition['label'])) {
// Cast the label to a string since it is an object.
// @see \Drupal\Core\StringTranslation\TranslationWrapper
......
......@@ -720,7 +720,7 @@ function hook_views_post_execute(ViewExecutable $view) {
*
* At this point the query has been executed, and the preRender() phase has
* already happened for handlers, so all data should be available. This hook
* can be utilized by themes.
* can be used by themes.
*
* Output can be added to the view by setting $view->attachment_before
* and $view->attachment_after.
......@@ -743,7 +743,7 @@ function hook_views_pre_render(ViewExecutable $view) {
* This can be valuable to be able to cache a view and still have some level of
* dynamic output. In an ideal world, the actual output will include HTML
* comment-based tokens, and then the post process can replace those tokens.
* This hook can be utilized by themes.
* This hook can be used by themes.
*
* Example usage. If it is known that the view is a node view and that the
* primary field will be a nid, you can do something like this:
......
......@@ -125,7 +125,7 @@ public function testDisplayAreas() {
// Assert that the expected text is found in each area category.
foreach ($areas as $type => $class) {
$element = $this->xpath('//div[contains(@class, :class)]/div', array(':class' => $class));
$this->assertEqual((string) $element[0], String::format('The selected display type does not utilize @type plugins', array('@type' => $type)));
$this->assertEqual((string) $element[0], String::format('The selected display type does not use @type plugins', array('@type' => $type)));
}
}
......
......@@ -64,7 +64,7 @@ public function testStyleUI() {
$this->drupalPostForm("admin/structure/views/view/$view_name/edit", array(), 'Add Page');
$this->drupalPostForm("admin/structure/views/nojs/display/$view_name/page_1/row", array('row[type]' => 'fields'), t('Apply'));
// If fields are being used this text will not be shown.
$this->assertNoText(t('The selected style or row format does not utilize fields.'));
$this->assertNoText(t('The selected style or row format does not use fields.'));
}
}
......@@ -966,7 +966,7 @@ public function getFormBucket(ViewUI $view, $type, $display) {
$uses_fields = $style_plugin && $style_plugin->usesFields();
if (!$uses_fields) {
$build['fields'][] = array(
'#markup' => $this->t('The selected style or row format does not utilize fields.'),
'#markup' => $this->t('The selected style or row format does not use fields.'),
'#theme_wrappers' => array('views_ui_container'),
'#attributes' => array('class' => array('views-display-setting')),
);
......@@ -978,7 +978,7 @@ public function getFormBucket(ViewUI $view, $type, $display) {
case 'empty':
if (!$executable->display_handler->usesAreas()) {
$build[$type][] = array(
'#markup' => $this->t('The selected display type does not utilize @type plugins', array('@type' => $type)),
'#markup' => $this->t('The selected display type does not use @type plugins', array('@type' => $type)),
'#theme_wrappers' => array('views_ui_container'),
'#attributes' => array('class' => array('views-display-setting')),
);
......
/**
* @file
* Responsive navigation tabs.
* Utilizes jquery.intrinsic.js to calculate if the tabs are larger than their
* Uses jquery.intrinsic.js to calculate if the tabs are larger than their
* container and toggles the 'is-horizontal' class.
*
* This also supports collapsible navigable is the 'is-collapsible' class is
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment