Updated documentation clarifying legacy widget handling and future updates (#309)

* Update widget-inner-wrapper.md

* Apply suggestions from code review

Co-authored-by: Copilot <[email protected]>

---------

Co-authored-by: Copilot <[email protected]>

Author: rami-elementor

src/widgets/widget-inner-wrapper.md

@@ -34,8 +34,7 @@ Elementor had previously utilized unoptimized markup. Nowadays, the only website
 
 The number of wrapping elements that each widget needs is up to the widget developer.
 
-If it's a legacy widget that requires both `<div>` wrappers, add the following method to the widget:
-
+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:
 ```php
 public function has_widget_inner_wrapper(): bool {
 	return true;
@@ -58,8 +57,9 @@ public function has_widget_inner_wrapper(): bool {
 }
 ```
 
-Whether the experiment is running or not, widgets that do not employ the `has_widget_inner_wrapper()` function will behave like unoptimized widgets with two wrapping `<div>` elements for backward compatibility.
+Finnaly, widgets that do not employ the `has_widget_inner_wrapper()` function will behave like unoptimized widgets with two wrapping `<div>` elements.
 
+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.
 ## Examples
 
 ### Optimized Widget DOM