Skip to content

Commit c7cd089

Browse files
Fix more typos
1 parent 2160246 commit c7cd089

File tree

9 files changed

+44
-44
lines changed

9 files changed

+44
-44
lines changed

docs/cli/displaying-output.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Standard output can be created using `$this->output->outln`
88

99
### Displaying Error
1010

11-
Similar to the `info()` function, tou can use `$this->error()` for displaying errors that occure. The error call will die upon output, and no further code will be executed.
11+
Similar to the `info()` function, you can use `$this->error()` for displaying errors that occurred. The error call will die upon output, and no further code will be executed.
1212

1313
### Formatting Output
1414

@@ -53,4 +53,4 @@ dim dim in the current text and background colors
5353
ul underline in the current text and background colors
5454
blink blinking in the current text and background colors
5555
reverse reverse the current text and background colors
56-
```
56+
```

docs/control-panel/channels.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ NOTE: **Note:** We recommend using the default base URL variable `{base_url}` de
9090
- **Channel** -- The full URL to the main page for this channel.
9191
- **Comment form** -- The full URL to the "comments" page for this channel. The URL should include the Template Group and Template. For example: <https://example.com/channel/comments/>
9292
- **Search results** -- The full URL where you would like search results from this channel to be pointed. The URL should include the Template Group and Template. For example: `{base_url}/index.php/channel/comments/`.
93-
- **RSS feed** -- Thes URL where you can view the RSS feed for this channel. For example: <https://example.com/channel/rss_2.0>
93+
- **RSS feed** -- The URL where you can view the RSS feed for this channel. For example: <https://example.com/channel/rss_2.0>
9494
- **Preview URL** -- The template path, or route, to use for [Live Preview](control-panel/create.md#preview) in this Channel. You can use the variables `{entry_id}` and `{url_title}` which will be replaced with the entry's ID or URL Title when rendering your template. For example: `blog/entry/{url_title}` **Note:** If an Entry has a Page URI it will be used instead of the Preview URL for the channel.
9595
- **Allow Preview** -- When set to yes, the entry preview will be allowed, don't forget to set the Preview URL too.
9696
- **Generated title** -- When a new entry is created or previewed, this value will be inserted by default in the Title field. This is helpful if you wish every entry in a channel to have the titles follow a certain format. The automatic URL Title creating javascript for the Publish page will ignore this text during processing.

docs/development/fieldtypes/enhanced.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Custom fields can display their data inside the Entry Manager through 3 possible
114114

115115
## Entry cloning support
116116

117-
ExpressionEngine has the ability to [clone existing entries](/channels/entry_cloning.md) using the "Clone to New Entry" option on the entry editing page. Most fieldtypes do not need to do anything special to support this feature.
117+
ExpressionEngine has the ability to [clone existing entries](/channels/entry_cloning.md) using the "Clone to New Entry" option on the entry editing page. Most fieldtypes do not need to do anything special to support this feature.
118118

119119
However, if the fieldtype you are developing saves data to its own database table, you might need to tell it to save the rows as a submission for the new entry and not for the existing one.
120120

@@ -223,7 +223,7 @@ There are 3 available methods, and you are required to implement `evaluate` at t
223223

224224
#### `evaluate($fieldValue, $expectedValue, $fieldSettings)`
225225

226-
Evaluates the rule by comparing the field value (`$fieldValue`) with the `$expectedValue` as entered in the conditional field settings.
226+
Evaluates the rule by comparing the field value (`$fieldValue`) with the `$expectedValue` as entered in the conditional field settings.
227227
`$fieldSettings` is available as array of field settings.
228228

229229
#### `getLanguageKey()`
@@ -248,23 +248,23 @@ To parse both cases correctly, please use the `ee()->file_field->parse_string()`
248248
ee()->load->library('file_field');
249249
$data = ee()->file_field->parse_string($data);
250250

251-
If the fieldtype is using custom JavaScript for manipulating the files, be sure to make the code aware of the [`EE.fileManagerCompatibilityMode`](development/control-panel-js/globals.md#filemanagercompatibilitymode) variable.
251+
If the fieldtype is using custom JavaScript for manipulating the files, be sure to make the code aware of the [`EE.fileManagerCompatibilityMode`](development/control-panel-js/globals.md#filemanagercompatibilitymode) variable.
252252

253253
## Implementing Filepicker for Rich Text Editor
254254

255255
If your add-on is operating as File Manager, you might want to make it available as file picker for RTE fields.
256256

257257
In order to achieve that, create file prefixed with `rtefb.` in add-on's main directory, e.g. `rtefb.my_addon.php`. You can refer to the file in Filepicker add-on as an example.
258258

259-
The file's class needs to implement `ExpressionEngine\Library\Rte\RteFilebrowserInterface`. The easiest way to achive that is to extend `ExpressionEngine\Library\Rte\AbstractRteFilebrowser` abstract class and add code only for the functions that work differently from
259+
The file's class needs to implement `ExpressionEngine\Library\Rte\RteFilebrowserInterface`. The easiest way to achieve that is to extend `ExpressionEngine\Library\Rte\AbstractRteFilebrowser` abstract class and add code only for the functions that work differently from
260260

261261
## Working with Front-End Editing
262262

263263
Most fieldtypes will work with [Front-end content management](/advanced-usage/front-end/frontend.md) out-of-the-box.
264264

265265
However there are some parameters that can be set in `ft.` to improve integration.
266266

267-
### Disabling Front-end Edit Link
267+
### Disabling Front-end Edit Link
268268

269269
public $disable_frontedit = true;
270270

docs/development/legacy/helpers/html-helper.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ The above code will produce this:
207207
<li>suare</li>
208208
<li>circles
209209
<ul>
210-
<li>elipse</li>
210+
<li>ellipse</li>
211211
<li>oval</li>
212212
<li>sphere</li>
213213
</ul>

docs/general/gdpr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Add-ons may also have consent requests, and you can also make any Consent Reques
4343

4444
## Records, Auditing
4545

46-
ExpressionEngine records an audit log of all consents granted or withdrawn by a user. This is maintained indefinitely. If you ever need to prove or report an individual's granting or withdrawl of consent, just visit your [Consent Logs](control-panel/system-logs.md#consent-logs).
46+
ExpressionEngine records an audit log of all consents granted or withdrawn by a user. This is maintained indefinitely. If you ever need to prove or report an individual's granting or withdrawal of consent, just visit your [Consent Logs](control-panel/system-logs.md#consent-logs).
4747

4848
## Data Portability
4949

0 commit comments

Comments
 (0)