chore: apply suggestions from code review

Co-authored-by: Neil Campbell <[email protected]>

docs/capabilities/debugging.md

@@ -21,6 +21,6 @@ Refer to the [algokit-utils-ts-debug](https://github.com/algorandfoundation/algo
 
 > Note: Config also contains a set flags that affect behaviour of [algokit-utils-ts-debug](https://github.com/algorandfoundation/algokit-utils-ts-debug). Those include `projectRoot`, `traceAll`, `traceBufferSizeMb`, and `maxSearchDepth`. Refer to addon package documentation for details.
 
-### Why debug utilities are in a separate package?
+### Why are the debug utilities in a separate package?
 
 To keep the `algokit-utils-ts` package lean and isomporphic, the debugging utilities are located in a separate package. This eliminates various error cases with bundlers (e.g. `webpack`, `esbuild`) when building for the browser.

docs/capabilities/event-emitter.md

@@ -1,6 +1,6 @@
 # Event Emitter
 
-The Event Emitter is a capability provided by AlgoKit Utils that allows for asynchronous event handling. It provides a flexible mechanism for emitting and listening to custom events, which can be particularly useful for debugging and extending functionality not available in the `algokit-utils-ts` package.
+The Event Emitter is a capability provided by AlgoKit Utils that allows for asynchronous event handling of lifecycle events. It provides a flexible mechanism for emitting and listening to custom events, which can be particularly useful for debugging and extending functionality not available in the `algokit-utils-ts` package.
 
 ## `AsyncEventEmitter`
 

src/types/async-event-emitter.spec.ts

@@ -8,8 +8,6 @@ describe('async-event-emitter', () => {
   afterEach(logging.afterEach)
 
   const mockRegisterNodeDebugHandlers = () => {
-    // TODO: Define types for the events
-    // TODO: Question - Would this be the package we'd use to surface the UI widget for downloading a simulate trace?
     Config.events.on('event_a', (data: unknown) => {
       logging.testLogger.info('event_a', data)
     })