Skip to content

chore: fix some comments #7975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 31, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cms/static/cms/js/libs/pep.js
Original file line number Diff line number Diff line change
Expand Up @@ -428,7 +428,7 @@
// is element a shadow host?
sr = this.targetingShadow(t);
while (sr) {
// find the the element inside the shadow root
// find the element inside the shadow root
st = sr.elementFromPoint(x, y);
if (!st) {
// check for older shadows
Expand Down
4 changes: 2 additions & 2 deletions cms/tests/frontend/integration/changeSettings.js
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ casper.test.begin('Change Settings', function(test) {
});
})
.waitForResource(/admin/)
// have to wait for the sideframe again, cause the page reloads itself after saving the the language
// have to wait for the sideframe again, cause the page reloads itself after saving the language
.waitUntilVisible('.cms-sideframe-frame')
.withFrame(0, function() {
casper
Expand All @@ -69,7 +69,7 @@ casper.test.begin('Change Settings', function(test) {
});
})
.waitForResource(/admin/)
// have to wait for the sideframe again, cause the page reloads itself after saving the the language
// have to wait for the sideframe again, cause the page reloads itself after saving the language
.waitUntilVisible('.cms-sideframe-frame')
.withFrame(0, function() {
casper
Expand Down
2 changes: 1 addition & 1 deletion docs/contributing/documentation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -317,7 +317,7 @@ context. Please follow these rules:
capitalisation or highlighting: "Your placeholder can now be used."
- at the start of sentences or titles, capitalise in the usual way: "Placeholder
management guide"
- when introducing the term for the the first time, or for the first time in a document,
- when introducing the term for the first time, or for the first time in a document,
you may highlight it to draw attention to it: "**Placeholders** are special model
fields".
- when the word refers specifically to an object in the code, highlight it as a literal:
Expand Down
Loading