Apply suggestions from code review

Co-authored-by: Simon H <[email protected]>

sites/svelte-5-preview/src/routes/docs/content/01-api/03-snippets.md

@@ -159,6 +159,7 @@ Within the template, snippets are values just like any other. As such, they can
 As an authoring convenience, snippets declare directly _inside_ a component implicitly become props _on_ the component ([demo](/#H4sIAAAAAAAAE41Sy27bMBD8lYVcwHYrW4kBXxRFaP-htzgHSqQsojLJkuu2BqF_74qUrfhxCHQRh7MzO9z1SSM74ZL8zSeKHUSSJz-MSdIET2Y4uD-iQ0Fnp4-2HpDC1VYaLHdqh_JgtEX4yapOQGP1AebrLJzWsXD-QjQi1lo5JMZRooNXeBuwHXoYLHOYM2OoiXkKv_GUwzYFY2VNFxvo0xtqxRR9F-7z04X8fE-uW2GtnJQ3E_tpvYV-oL9Ti0U2hVJFjMMZslcfW-5DWj9zShojEFrBuLCLZR_9CmzLQCwy-psw8rxBgvkNhhpZd8F8NppE7Stbq_8u-GTKS8_XQ9Keqnl5BZP1AzTYP2bDV7i7_9hLEeda0iocNJeNFDzJ0R5Fn142JzA-uzsdBfLhldPxPdMhIPS0H1-M1cYtlnejwdBDfBXZjHXTFOg4BhuOtvTfrVDEmAZG2ew5ezYV-Ew2fVzVAivNTyPHzwSr29AlMAe8f6g-zuWDts-GusAmdBSkv3P7qnB4GpMEEHwsRPEPV6yTe5VDJxp8iXClLRmtnGG1VHva3oCPHQd9QJsrbFd1Kzu-2Khvz8uzZsXqX3urj4rnMBNCXNUG83zf6Yp1C2yXKdxA_KJjGOfRfb0Vh7MKDShEuV-M9_4_nq6svF4EAAA=)):
 
 ```svelte
+<!-- this is semantically the same as the above -->
 <Table data={fruits}>
 	{#snippet header()}
 		<th>fruit</th>

sites/svelte-5-preview/src/routes/docs/content/01-api/04-event-handlers.md

@@ -176,5 +176,5 @@ By deprecating `createEventDispatcher` and the `on:` directive in favour of call
 - remove the overhead of creating `CustomEvent` objects for events that may not even have listeners
 - add the ability to spread event handlers
 - add the ability to know which event handlers were provided to a component
-- add the ability to express whether a given event handler is required or optional (props with default values are considered optional, those without are considered required)
+- add the ability to express whether a given event handler is required or optional
 - increase type safety (previously, it was effectively impossible for Svelte to guarantee that a component didn't emit a particular event)