chore: fixed up some comments

Author: joker23

packages/sdk/react/contract-tests/app/ClientEntity.ts

@@ -11,11 +11,8 @@ import { useLDClient } from '@launchdarkly/react-sdk';
 
 export type CommandHandler = (params: CommandParams) => Promise<unknown>;
 
-/**
- * Creates an IClientEntity wrapper for a React-managed client.
- * The entity's doCommand delegates to the command handler registered
- * by ClientInstance once the React component mounts.
- */
+// We are creating this wrapper because we have a custom commandHandler implementation to work well
+// with React rendering.
 export function createReactClientEntity(
   clientId: string,
   commandHandlers: Map<string, CommandHandler>,

packages/tooling/contract-test-utils/src/client-side/ClientEntity.ts

@@ -7,10 +7,7 @@ import { IClientEntity } from './TestHarnessWebSocket.js';
 
 /**
  * Base client entity that wraps an SDK client and dispatches test harness
- * commands. Suitable for browser, react-native, and electron entities.
- *
- * Subclass and override `doCommand` to customize command handling for
- * platform-specific behavior.
+ * commands.
  */
 export class ClientEntity implements IClientEntity {
   protected readonly logger: LDLogger;

packages/tooling/contract-test-utils/src/client-side/capabilities.ts

@@ -1,9 +1,6 @@
 /**
  * Known capability strings from the SDK test harness service spec.
  * See: https://github.com/launchdarkly/sdk-test-harness/blob/v2/docs/service_spec.md
- *
- * Each entity should define its own capabilities array typed against this union,
- * since different SDKs advertise different capabilities.
  */
 export type Capability =
   | 'server-side'