correct imports in README docs

hooks/useCommonContext/README.md

@@ -8,7 +8,7 @@ A React hook that allows connecting to several potential active react contexts.
 
 ```Typescript
 import React from 'react';
-import {useCommonContext} from 'react-hooks';
+import {useCommonContext} from '@optum/react-hooks';
 
 import {useContextA} from 'some-context-provider-a';
 import {useContextB} from 'some-context-provider-b';

hooks/useFocus/README.md

@@ -8,7 +8,7 @@ A React hook that simplifies focus management.
 
 ```Typescript
 import React from 'react';
-import {useFocus} from 'react-hooks';
+import {useFocus} from '@optum/react-hooks';
 
 
 export const MyComponent = ({

hooks/useLoadData/README.md

@@ -7,7 +7,7 @@ A React hook that simplifies complex data loading requirements.
 The most simple usage is to pass a single argument, which should be an asynchronous function. This function will get executed immediately upon component initialization:
 
 ```TypeScript
-import {useLoadData} from 'react-hooks';
+import {useLoadData} from '@optum/react-hooks';
 
 export const DataComponent: React.FC = () => {
   const {isError, isInProgress, result} = useLoadData(async () => fetch(...));

hooks/useOptionalDependency/README.md

@@ -3,11 +3,11 @@
 A React hook that safely optionalizes retry responses.
 
 ## Usage
-`useOptionalDependency` is designed to be used in tandem with [useLoadData](../useLoadData/). This hook will safely optionalize a [retry response objects](../../RetryResponse.ts), meaning an optional dependency that returns type `T` will be typed as `T | null` when passed into `fetchData`, and will always be treated as _null_ by `useLoadData` if the dependency errors. The advantage here being that `useLoadData` will still wait upon the optional dependency to resolve (successfully or unsucessfully), and more significantly, does not hold up a dependency chain while still exposing an error.  
+`useOptionalDependency` is designed to be used in tandem with [useLoadData](../useLoadData/). This hook will safely optionalize a [retry response objects](https://github.com/Optum/react-hooks/blob/main/types/RetryResponse.ts), meaning an optional dependency that returns type `T` will be typed as `T | null` when passed into `fetchData`, and will always be treated as _null_ by `useLoadData` if the dependency errors. The advantage here being that `useLoadData` will still wait upon the optional dependency to resolve (successfully or unsucessfully), and more significantly, does not hold up a dependency chain while still exposing an error.  
 
 ```Typescript
 import React from 'react';
-import {useLoadData} from '@Optum/react-hooks';
+import {useLoadData} from '@optum/react-hooks';
 
 export const MyComponent = (props) => {
  const loadedUserProfile = useLoadData(fetchUserProfile); // loadedUserProfile will be of type RetryResponse<Profile>

hooks/useRetry/README.md

@@ -3,7 +3,7 @@
 A React hook that simplifies retrying failed service calls.
 
 ## Usage
-`useRetry` exposes a wrapped version of [useLoadData](../useLoadData/) that retries any and all errored [retry response objects](../../types/RetryResponse), and only those responses created, from that exposed version of _useLoadData_. 
+`useRetry` exposes a wrapped version of [useLoadData](../useLoadData/) that retries any and all errored [retry response objects](https://github.com/Optum/react-hooks/blob/main/types/RetryResponse.ts), and only those responses created, from that exposed version of _useLoadData_. 
 
 
 

hooks/useServiceEffect/README.md

@@ -22,7 +22,7 @@ and our component looks something like this:
 
 ```Typescript
 import React from 'react';
-import {useServiceEffect} from 'react-hooks';
+import {useServiceEffect} from '@optum/react-hooks';
 
 
 export const MyComponent = ({