Update triage-procedure.md

src/en/wizden-staff/maintainer/triage-procedure.md

@@ -51,7 +51,7 @@ Each label has a description that explains what is to be used for in its categor
 | Area | A | Describes which area of the project an item is related to. An item may be related to multiple areas, however it should always have at least one. An example would be a guidebook entry on an undocumented Science feature, which would fit within both the Guidebook and Science area. If an item doesn't seem to fit in any area, report it to a maintainer to see if a new label needs to be made. |
 | Branch | Branch | If an item is intended for a non-master branch. Most commonly used for hotfixes. |
 | Changes | Changes | Indicates an item should be handled by someone with knowledge in a certain area. Automatically generated by Github. |
-| Difficulty | D# | 0-3, with 0 the hardest. An estimate of how complex the item would be to review or create a PR for. <br>`DB: Beginner Friendly` can be applied for items that are particularly beginner friendly. |
+| Difficulty | D# | 0-3, with 0 the hardest. An estimate of how complex the item would be to review or create a PR for. <br>`DB: Beginner Friendly` should include clear steps towards a solution for the issue. |
 | Fun | Fun | For the silly little labels. Should be used sparingly. |
 | Intent | Intent | If the item is intended to be processed using an alternate review/merge policy. Used for hotfixes or test merges.
 | Issue | Issue | Reserved for Issues, where a complex bug should be replicated to ensure it's accurately reported. Not necessary for all bug reports. |