Added some extra clarification to a comment above the assertion in LookAndFeel's destructor

modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp

@@ -60,8 +60,10 @@ LookAndFeel::~LookAndFeel()
 
        Generally the fix for this will be to make sure you call
        Component::setLookandFeel (nullptr) on any components that were still using
-       it before you delete it. Or call LookAndFeel::setDefaultLookAndFeel (nullptr)
-       if you had set it up to be the default one.
+       it before you delete it, or call LookAndFeel::setDefaultLookAndFeel (nullptr)
+       if you had set it up to be the default one. This assertion can also be avoided by
+       declaring your LookAndFeel object before any of the Components that use it as
+       the LookAndFeel will be destroyed before the Components.
 
        Deleting a LookAndFeel is unlikely to cause a crash since most things will use a
        safe WeakReference to it, but it could cause some unexpected graphical behaviour,