Typo

Signed-off-by: Mike Turley <[email protected]>

client/src/app/hooks/table-controls/DOCS.md

@@ -12,7 +12,7 @@ The table-controls hooks and components provide a pattern where state logic can
 
 - Featureful tables should be easy to implement with code that is short and readable without sacrificing composability and refactorability.
 - The consumer should be able to override any and all props manually on any element of the table. If there is a future need for table state to be used for rendering in a way we don't currently anticipate, that should not be blocked by this abstraction.
-- Client-paginated and server-paginated tables should be similar to implement and share reusable. If a table needs to be converted between client logic and server logic, that should be relatively easy.
+- Client-paginated and server-paginated tables should be similar to implement and share reusable code. If a table needs to be converted between client logic and server logic, that should be relatively easy.
 - There should not be a concept of a "row object" because rows are presentational details and defining them as a separate model from the API data causes unnecessary complexity. See [Item Objects, Not Row Objects](#item-objects-not-row-objects).
 - Strict TypeScript types with generics inferred from parameters should be used to provide a safe and convenient development experience without having to repeat type annotations all over the page-level code.
 - All features should be optional and fall back to reasonable defaults if their options are omitted.