Skip to content

Commit e3595c1

Browse files
Apply suggestions from code review
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent dd0a0ec commit e3595c1

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

src/widgets/widget-inner-wrapper.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,7 @@ Elementor had previously utilized unoptimized markup. Nowadays, the only website
3434

3535
The number of wrapping elements that each widget needs is up to the widget developer.
3636

37-
If it's a legacy widget that requires both `<div>` wrappers, as it reqieres the inner `.elementor-widget-container` wrapper, add the following method to the widget:
38-
37+
If it's a legacy widget that requires both `<div>` wrappers, as it requires the inner `.elementor-widget-container` wrapper, add the following method to the widget:
3938
```php
4039
public function has_widget_inner_wrapper(): bool {
4140
return true;
@@ -60,8 +59,7 @@ public function has_widget_inner_wrapper(): bool {
6059

6160
Finnaly, widgets that do not employ the `has_widget_inner_wrapper()` function will behave like unoptimized widgets with two wrapping `<div>` elements.
6261

63-
In any case, whether the experiment is active or not, developer need to think about the future when Elementor merges this feature. To prevent styling issues, make the nesseary updates. Add the `has_widget_inner_wrapper()` to all the widgets.
64-
62+
In any case, whether the experiment is active or not, developer need to think about the future when Elementor merges this feature. To prevent styling issues, make the necessary updates. Add the `has_widget_inner_wrapper()` to all the widgets.
6563
## Examples
6664

6765
### Optimized Widget DOM

0 commit comments

Comments
 (0)