diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f65c7205ab5..f0b1fed4bd5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -11,7 +11,7 @@ There are many ways that you can contribute to Moodle, not just through developm
All issues should be reported via, and patched provided to the [Moodle Tracker][3].
-The Moodle [Github][4] repository is a clone of the official Moodle repository, whcih can be found at https://git.moodle.org.
+The Moodle [Github][4] repository is a clone of the official Moodle repository, which can be found at https://git.moodle.org.
## Moodle core bug fixes and new features
@@ -23,7 +23,7 @@ Over the years, Moodle has developed a mature process for reporting, reviewing,
- New features are developed on the `main` branch. Bug fixes are also backported to currently supported maintenance (stable) branches.
> [!IMPORTANT]
-> Please do not publish security issues, or patches releating to them publicly.
+> Please do not publish security issues, or patches relating to them publicly.
> See our [Responsible Disclosure Policy][5] for more information.
diff --git a/UPGRADING.md b/UPGRADING.md
index ec842db191e..990c7892edc 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -36,7 +36,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
For more information see [MDL-75971](https://tracker.moodle.org/browse/MDL-75971)
- A new core\ip_utils::normalize_internet_address() method is created to sanitize an IP address, a range of IP addresses, a domain name or a wildcard domain matching pattern.
- Moodle previously allowed entries such as 192.168. or .moodle.org for certain variables (eg: $CFG->proxybypass). Since MDL-74289, these formats are no longer allowed. This method converts this informations into an authorized format. For example, 192.168. becomes 192.168.0.0/16 and .moodle.org becomes *.moodle.org.
+ Moodle previously allowed entries such as 192.168. or .moodle.org for certain variables (eg: $CFG->proxybypass). Since MDL-74289, these formats are no longer allowed. This method converts this information into an authorized format. For example, 192.168. becomes 192.168.0.0/16 and .moodle.org becomes *.moodle.org.
Also a new core\ip_utils::normalize_internet_address_list() method is created. Based on core\ip_utils::normalize_internet_address(), this method normalizes a string containing a series of Internet addresses.
@@ -60,7 +60,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- Add after_role_switched hook that is triggered when we switch role to a new role in a course.
For more information see [MDL-83542](https://tracker.moodle.org/browse/MDL-83542)
-- New generic collapsable section output added. Use core\output\local\collapsable_section or include the core/local/collapsable_section template to use it. See the full documentation in the component library.
+- New generic collapsible section output added. Use core\output\local\collapsable_section or include the core/local/collapsable_section template to use it. See the full documentation in the component library.
For more information see [MDL-83869](https://tracker.moodle.org/browse/MDL-83869)
- A new method get_instance_record has been added to cm_info object so core can get the activity table record without using the $DB object every time. Also, the method caches de result so getting more than once per execution is much faster.
@@ -146,7 +146,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- question_make_default_categories()
No longer creates a default category in either CONTEXT_SYSTEM, CONTEXT_COURSE, or CONTEXT_COURSECAT.
- Superceded by question_get_default_category which can optionally create one if it does not exist.
+ Superseded by question_get_default_category which can optionally create one if it does not exist.
For more information see [MDL-71378](https://tracker.moodle.org/browse/MDL-71378)
- question_delete_course()
@@ -177,7 +177,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- Remove support deprecated boolean 'primary' parameter in \core\output\single_button. The 4th parameter is now a string and not a boolean (the use was to set it to true to have a primary button)
For more information see [MDL-75875](https://tracker.moodle.org/browse/MDL-75875)
-- Final removal of the following constants/methods from the `\core\encyption` class, removing support for OpenSSL fallback:
+- Final removal of the following constants/methods from the `\core\encryption` class, removing support for OpenSSL fallback:
- `METHOD_OPENSSL`
- `OPENSSL_CIPHER`
@@ -389,7 +389,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Added
-- Now the core_courseformat\local\content\cm\completion output is more reusable. All the HTML has been moved to its own mustache file, and the output class has a new set_smallbutton method to decide wether to rendered it as a small button (like in the course page) or as a normal one (for other types of pages).
+- Now the core_courseformat\local\content\cm\completion output is more reusable. All the HTML has been moved to its own mustache file, and the output class has a new set_smallbutton method to decide whether to rendered it as a small button (like in the course page) or as a normal one (for other types of pages).
For more information see [MDL-83872](https://tracker.moodle.org/browse/MDL-83872)
- New core_course\output\activity_icon class to render activity icons with or without purpose color. This output will centralize the way Moodle renders activity icons
@@ -484,7 +484,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- Protected function `core_courseformat\output\local\content\section\availability::availability_info()` has been fully removed. Use `core_courseformat\output\local\content\section\availability::get_availability_data()` instead.
For more information see [MDL-78489](https://tracker.moodle.org/browse/MDL-78489)
-- The old UI for moving activities and sections without javascript is not avaiable anymore from the actions dropdown. From now, on the only UI to move activities and sections is using the move action in the course editor. Format plugins can still use the old links to make the "move here" elements appear, but they will show deprecated messages. All the non-ajax moving will be removed in Moodle 6.0.
+- The old UI for moving activities and sections without javascript is not available anymore from the actions dropdown. From now, on the only UI to move activities and sections is using the move action in the course editor. Format plugins can still use the old links to make the "move here" elements appear, but they will show deprecated messages. All the non-ajax moving will be removed in Moodle 6.0.
For more information see [MDL-83562](https://tracker.moodle.org/browse/MDL-83562)
@@ -639,7 +639,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
For more information see [MDL-68806](https://tracker.moodle.org/browse/MDL-68806)
- The definition of the abstract `core_question\local\bank\condition` class has changed to make it clearer which methods are required in child classes.
The `get_filter_class` method is no longer declared as abstract, and will return `null` by default to use the base `core/datafilter/filtertype` class. If you have defined this method to return `null` in your own class, it will continue to work, but it is no longer necessary.
- `build_query_from_filter` and `get_condition_key` are now declared as abstract, since all filter condition classes must define these (as well as existing abstract methods) to function. Again, exsiting child classes will continue to work if they did before, as they already needed these methods.
+ `build_query_from_filter` and `get_condition_key` are now declared as abstract, since all filter condition classes must define these (as well as existing abstract methods) to function. Again, existing child classes will continue to work if they did before, as they already needed these methods.
For more information see [MDL-83859](https://tracker.moodle.org/browse/MDL-83859)
@@ -953,7 +953,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- There is a new method `submission_summary_for_messages()` for submission sub-plugins to summarise what has been submitted for inclusion in confirmation messages to students.
For more information see [MDL-84387](https://tracker.moodle.org/browse/MDL-84387)
-- When the assignment activity sends notifications, it now sets more information in the $a object passed to the languages strings for the message subject and body. This is to give more flexibility to people using Language Customisation. The avaiable information is the same as the template context for the two templates in the next paragraph, but without the messagetext/html.
+- When the assignment activity sends notifications, it now sets more information in the $a object passed to the languages strings for the message subject and body. This is to give more flexibility to people using Language Customisation. The available information is the same as the template context for the two templates in the next paragraph, but without the messagetext/html.
Also, the overall structure of these messages is now rendered using templates mod_assign/messages/notification_html and mod_assign/messages/notification_html, so they can be overridden by themes. As a result of this, the methods format_notification_message_text and format_notification_message_html (which should have been private to mod_assign and not used anywhere else) have been removed.
For more information see [MDL-84733](https://tracker.moodle.org/browse/MDL-84733)
@@ -1030,7 +1030,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Deprecated
-- The 'mode' parameter has been deprecated from 'edit_template_action_bar' and 'templates_table' contructors.
+- The 'mode' parameter has been deprecated from 'edit_template_action_bar' and 'templates_table' constructors.
For more information see [MDL-81744](https://tracker.moodle.org/browse/MDL-81744)
@@ -1171,12 +1171,12 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
- qbank_bulkmove/helper::get_displaydata
- Superceded by a modal and webservice, see qbank_bulkmove/modal_question_bank_bulkmove and core_question_external\move_questions
+ Superseded by a modal and webservice, see qbank_bulkmove/modal_question_bank_bulkmove and core_question_external\move_questions
For more information see [MDL-71378](https://tracker.moodle.org/browse/MDL-71378)
- qbank_bulkmove\output\renderer::render_bulk_move_form
- Superceded by qbank_bulkmove\output\bulk_move
+ Superseded by qbank_bulkmove\output\bulk_move
For more information see [MDL-71378](https://tracker.moodle.org/browse/MDL-71378)
@@ -2118,7 +2118,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Added
- All session management has been moved to the `\core\session\manager` class.
- This removes the dependancy to use the `sessions` table.
+ This removes the dependency to use the `sessions` table.
Session management plugins (like Redis) should now inherit
the base `\core\session\handler` class, which implements
@@ -2146,7 +2146,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Added
-- A new `$reponsive` property (defaulting to `true`) has been added to the `\core_table\flexible_table` class.
+- A new `$responsive` property (defaulting to `true`) has been added to the `\core_table\flexible_table` class.
This property allows you to control whether the table is rendered as a responsive table.
For more information see [MDL-80748](https://tracker.moodle.org/browse/MDL-80748)
@@ -2266,7 +2266,7 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Added
-- Added new `FEATURE_QUICKCREATE` for modules that can be quickly created in the course wihout filling a previous form.
+- Added new `FEATURE_QUICKCREATE` for modules that can be quickly created in the course without filling a previous form.
For more information see [MDL-81767](https://tracker.moodle.org/browse/MDL-81767)
@@ -2464,12 +2464,12 @@ The format of this change log follows the advice given at [Keep a CHANGELOG](htt
#### Added
-- Bridged `theme-color-level` using a new `shift-color` function to prepare for its deprecation in Boostrap 5.
+- Bridged `theme-color-level` using a new `shift-color` function to prepare for its deprecation in Bootstrap 5.
For more information see [MDL-81816](https://tracker.moodle.org/browse/MDL-81816)
- Upon upgrading Font Awesome from version 4 to 6, the solid family was selected by default.
- Support for the `regular`, and `brands` families of icons has now been added, allowing icons defined with `\core\outut\icon_system::FONTAWESOME` to use them.
+ Support for the `regular`, and `brands` families of icons has now been added, allowing icons defined with `\core\output\icon_system::FONTAWESOME` to use them.
Icons can select the FontAwesome family (`fa-regular`, `fa-brands`, `fa-solid`) by using the relevant class name when display the icon.
diff --git a/admin/roles/UPGRADING.md b/admin/roles/UPGRADING.md
index fc857502871..baf31976b31 100644
--- a/admin/roles/UPGRADING.md
+++ b/admin/roles/UPGRADING.md
@@ -5,7 +5,7 @@
### Added
- All session management has been moved to the `\core\session\manager` class.
- This removes the dependancy to use the `sessions` table.
+ This removes the dependency to use the `sessions` table.
Session management plugins (like Redis) should now inherit
the base `\core\session\handler` class, which implements
diff --git a/admin/tool/componentlibrary/content/library/syntax-highlighting.md b/admin/tool/componentlibrary/content/library/syntax-highlighting.md
index b7fd12170fa..565abf3da8a 100644
--- a/admin/tool/componentlibrary/content/library/syntax-highlighting.md
+++ b/admin/tool/componentlibrary/content/library/syntax-highlighting.md
@@ -9,7 +9,7 @@ weight: 3
## Using Shortcodes for syntax
-Using this (shortcode) syntax you can higlight programming syntax in the component library
+Using this (shortcode) syntax you can highlight programming syntax in the component library
## HTML highlighting
diff --git a/admin/tool/componentlibrary/content/moodle/accessibility/contrast.md b/admin/tool/componentlibrary/content/moodle/accessibility/contrast.md
index 0e87c5bfe26..3b7f1cd8628 100644
--- a/admin/tool/componentlibrary/content/moodle/accessibility/contrast.md
+++ b/admin/tool/componentlibrary/content/moodle/accessibility/contrast.md
@@ -8,7 +8,7 @@ tags:
- 3.9
---
-## Accessibile colours
+## Accessible colours
In WCAG 2, contrast is a measure of the difference in perceived "luminance" or brightness between two colors (the phrase "color contrast" is never used). This brightness difference is expressed as a ratio ranging from 1:1 (e.g. white on white) to 21:1 (e.g., black on a white).
diff --git a/admin/tool/componentlibrary/content/moodle/accessibility/keyboard-access.md b/admin/tool/componentlibrary/content/moodle/accessibility/keyboard-access.md
index 37e49b6f5fc..77fa2ae72e4 100644
--- a/admin/tool/componentlibrary/content/moodle/accessibility/keyboard-access.md
+++ b/admin/tool/componentlibrary/content/moodle/accessibility/keyboard-access.md
@@ -68,4 +68,4 @@ exampleContainer.querySelectorAll('.aalink').forEach(function (link) {
The focus order when navigating a Moodle page needs to be logical.
An example of logical focus order would be starting at the main menu before then following through to the main content and finally the footer. To achieve this the navdrawer menu has been relocate in the DOM to be positioned right after the navdrawer in [MDL-67863](https://tracker.moodle.org/browse/MDL-67863).
-Testing with a keyboard is essential when evaluating the accessibility of your compoment, You should never be able to tab to hidden items and there should always be a visual que to your current location in the page.
+Testing with a keyboard is essential when evaluating the accessibility of your component, You should never be able to tab to hidden items and there should always be a visual que to your current location in the page.
diff --git a/admin/tool/componentlibrary/content/moodle/components/actionmenu.md b/admin/tool/componentlibrary/content/moodle/components/actionmenu.md
index b9102221131..f4511f0295e 100644
--- a/admin/tool/componentlibrary/content/moodle/components/actionmenu.md
+++ b/admin/tool/componentlibrary/content/moodle/components/actionmenu.md
@@ -19,7 +19,7 @@ Moodle action menus are a reusable component that can display a list of actions
- `lib/classes/output/local/action_menu/subpanel.php`: contains the `subpanel` menu item class.
- `lib/templates/action_menu.mustache`: contains the main template for the action menu.
- `lib/templates/action_menu_*`: location for the legacy auxliar mustache files.
-- `lib/templates/local/action_menu/*`: location for any new auxiliar mustache files.
+- `lib/templates/local/action_menu/*`: location for any new auxiliary mustache files.
## Examples
@@ -182,7 +182,7 @@ The following example creates a subpanel using a renderable choicelist instance:
/** @var core_renderer $output*/
$output = $PAGE->get_renderer('core');
-// A choice list is a renderable class to outpout a user choice.
+// A choice list is a renderable class to output a user choice.
$choice = new core\output\choicelist('Choice example');
$choice->add_option("statusa", "Status A", [
'url' => $PAGE->url,
diff --git a/admin/tool/componentlibrary/content/moodle/components/buttons.md b/admin/tool/componentlibrary/content/moodle/components/buttons.md
index 4df972eacf9..81d2ca31158 100644
--- a/admin/tool/componentlibrary/content/moodle/components/buttons.md
+++ b/admin/tool/componentlibrary/content/moodle/components/buttons.md
@@ -56,14 +56,14 @@ Use a danger button when the primary action is a potentially dangerous action, l
{{< /example >}}
-Outline buttons are used for buttons that controll part of the user interface, like filters on a table or the display type on the user dashboard. Outline buttons look more subtle than secondary buttons and do not distract the user from the main user interface too much.
+Outline buttons are used for buttons that control part of the user interface, like filters on a table or the display type on the user dashboard. Outline buttons look more subtle than secondary buttons and do not distract the user from the main user interface too much.
### Subtle buttons
{{< example >}}
-
-
+
+
{{< /example >}}
The subtle class is designed to create buttons that offer a balance between the visual prominence of standard buttons and the minimalism of outline buttons. This class aims to provide a softer, more understated appearance compared to regular buttons while still maintaining more visual presence than outline buttons.
diff --git a/admin/tool/componentlibrary/content/moodle/components/collapsable-sections.md b/admin/tool/componentlibrary/content/moodle/components/collapsable-sections.md
index 655d034177a..ce680dd4bfd 100644
--- a/admin/tool/componentlibrary/content/moodle/components/collapsable-sections.md
+++ b/admin/tool/componentlibrary/content/moodle/components/collapsable-sections.md
@@ -1,7 +1,7 @@
---
layout: docs
-title: "Collapsable sections"
-description: "A reusable collapsable section component"
+title: "Collapsible sections"
+description: "A reusable collapsible section component"
date: 2024-12-20T10:10:00+08:00
draft: false
tags:
@@ -11,25 +11,25 @@ tags:
## How it works
-The collapsable section component in Moodle allows you to create sections of content that can be expanded or collapsed by the user. This is useful for organizing content in a way that doesn't overwhelm the user with too much information at once. The component is built using a combination of PHP, Mustache templates, and JavaScript.
+The collapsible section component in Moodle allows you to create sections of content that can be expanded or collapsed by the user. This is useful for organizing content in a way that doesn't overwhelm the user with too much information at once. The component is built using a combination of PHP, Mustache templates, and JavaScript.
## Source files
-- `lib/templates/local/collapsable_section.mustache`: The Mustache template for rendering the collapsable section.
-- `lib/classes/output/local/collapsable_section.php`: The output class for the collapsable section component.
-- `lib/amd/src/local/collapsable_section/events.js`: JavaScript module for handling events related to the collapsable section.
-- `lib/amd/src/local/collapsable_section/controls.js`: JavaScript module for controlling the collapsable section.
+- `lib/templates/local/collapsable_section.mustache`: The Mustache template for rendering the collapsible section.
+- `lib/classes/output/local/collapsable_section.php`: The output class for the collapsible section component.
+- `lib/amd/src/local/collapsable_section/events.js`: JavaScript module for handling events related to the collapsible section.
+- `lib/amd/src/local/collapsable_section/controls.js`: JavaScript module for controlling the collapsible section.
## Usage
-To use the collapsable section component, you need to create an instance of the `collapsable_section` class and render it using Moodle's output renderer. You can customize the title content, section content, CSS classes, and additional HTML attributes.
+To use the collapsible section component, you need to create an instance of the `collapsable_section` class and render it using Moodle's output renderer. You can customize the title content, section content, CSS classes, and additional HTML attributes.
Example:
{{< php >}}
use core\output\local\collapsable_section;
-// Create an instance of the collapsable section.
+// Create an instance of the collapsible section.
$section = new collapsable_section(
titlecontent: 'Section Title',
sectioncontent: 'This is the content of the section.',
@@ -45,7 +45,7 @@ echo $OUTPUT->render($section);
}
{{< /mustache >}}
-You can also add CSS classes, extra HTML attributes, and customize the expand and collapse labels of the collapsable section:
+You can also add CSS classes, extra HTML attributes, and customize the expand and collapse labels of the collapsible section:
{{< php >}}
$section = new collapsable_section(
@@ -83,9 +83,9 @@ echo $OUTPUT->render($section);
}
{{< /mustache >}}
-## Include a collapsable section from a mustache template
+## Include a collapsible section from a mustache template
-Collapsable sections can also be included from a Mustache template using the `core/local/collapsable_section` template. This template allows you to define the title content and section content within the template.
+Collapsible sections can also be included from a Mustache template using the `core/local/collapsable_section` template. This template allows you to define the title content and section content within the template.
{{< mustache template="tool_componentlibrary/examples/collapsablesections/includesection" >}}
{
@@ -96,7 +96,7 @@ Collapsable sections can also be included from a Mustache template using the `co
### Control a section
-The collapsable sections component includes a JavaScript module for controlling the sections. This module provides methods to hide, show, and toggle the visibility of the sections.
+The collapsible sections component includes a JavaScript module for controlling the sections. This module provides methods to hide, show, and toggle the visibility of the sections.
To use the JavaScript controls, you need to import the `CollapsableSection` module and create an instance from a selector:
@@ -129,7 +129,7 @@ if (section.isVisible()) {
### Events
-The collapsable sections component also includes a JavaScript module for handling events. This module wraps the standard Bootstrap collapsable events and provides custom event types for collapsable sections.
+The collapsible sections component also includes a JavaScript module for handling events. This module wraps the standard Bootstrap collapsible events and provides custom event types for collapsible sections.
The component triggers two main events:
@@ -143,7 +143,7 @@ For convenience, the `core/local/collapsable_section/events` also list the origi
- `hide.bs.collapse`: when the collapse is starting to hide.
- `hidden.bs.collapse`: when the collapse has been hidden.
-To listen for events related to the collapsable sections, you need to import the `eventTypes` from the `events` module and add event listeners:
+To listen for events related to the collapsible sections, you need to import the `eventTypes` from the `events` module and add event listeners:
```javascript
import {eventTypes as collapsableSectionEventTypes} from 'core/local/collapsable_section/events';
diff --git a/admin/tool/componentlibrary/content/moodle/components/coursecards.md b/admin/tool/componentlibrary/content/moodle/components/coursecards.md
index ca449302845..983922779ac 100644
--- a/admin/tool/componentlibrary/content/moodle/components/coursecards.md
+++ b/admin/tool/componentlibrary/content/moodle/components/coursecards.md
@@ -12,7 +12,7 @@ tags:
## How to use course cards
-Course cards are rendered using a shared template found in `course/templates/coursecard.mustache`. They are loaded throught JavaScript or PHP on pages like the user dashboard.
+Course cards are rendered using a shared template found in `course/templates/coursecard.mustache`. They are loaded through JavaScript or PHP on pages like the user dashboard.
Course cards should always contain an image, if no image is provided by the backend a placeholder image is used. The card image and title should be clickable and should always link you to a course page.
diff --git a/admin/tool/componentlibrary/content/moodle/components/example.md b/admin/tool/componentlibrary/content/moodle/components/example.md
index c1d5f39f7c4..88b184021d7 100644
--- a/admin/tool/componentlibrary/content/moodle/components/example.md
+++ b/admin/tool/componentlibrary/content/moodle/components/example.md
@@ -53,5 +53,5 @@ Is there a webservice backend required?
Descripbe the `aria-something` parts of the element. Are there any possible accessibility issues using this example?
What are the considerations for keyboard navigation?
-What accessibile colors can be used?
+What accessible colors can be used?
How to test its accessibility?
diff --git a/admin/tool/componentlibrary/content/moodle/components/footer.md b/admin/tool/componentlibrary/content/moodle/components/footer.md
index e0e83753b95..5b072ce6649 100644
--- a/admin/tool/componentlibrary/content/moodle/components/footer.md
+++ b/admin/tool/componentlibrary/content/moodle/components/footer.md
@@ -29,7 +29,7 @@ The page footer should always stick to the bottom of the page and never overlap
### Minimal footer requirements
-The page footer is required to inject the page JavaScript, show the reset user tours link and show user info and (if avaliable) the contents of the user configure theme custom menu.
+The page footer is required to inject the page JavaScript, show the reset user tours link and show user info and (if available) the contents of the user configure theme custom menu.
{{< example >}}