From 8cb033a0e0ff8cca41d0fd92d90b5589d88c206f Mon Sep 17 00:00:00 2001
From: Matt Herbst <mherbst@anduril.com>
Date: Tue, 12 Mar 2024 09:59:01 -0700
Subject: [PATCH] Update repo link

---
 CHANGELOG.md                        | 146 ++++++++++++++--------------
 LICENSE                             |   2 +-
 README.md                           |  28 +++---
 examples/ComponentToPrint/index.tsx |   2 +-
 package.json                        |   6 +-
 src/components/ReactToPrint.tsx     |  10 +-
 6 files changed, 97 insertions(+), 97 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index bfa1b58..b6a9c15 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,11 +2,11 @@
 
 ## 2.15.1 (February 13th, 2024)
 
-- FIX [686](https://github.com/gregnb/react-to-print/pull/686) A breaking type error was mistakenly introduced as part of [652](https://github.com/gregnb/react-to-print/issues/652). This has been fixed.
+- FIX [686](https://github.com/MatthewHerbst/react-to-print/pull/686) A breaking type error was mistakenly introduced as part of [652](https://github.com/MatthewHerbst/react-to-print/issues/652). This has been fixed.
 
 ## 2.15.0 (February 11th, 2024)
 
-- FEATURE [652](https://github.com/gregnb/react-to-print/issues/652): When using the `useReactToPrint` hook it is now possible to pass the returned callback the `content` ref at call time, rather than needing to pass it to the hook directly. This allows for generating the content to be printed closer to when the print occurs. Thanks [isocroft](https://github.com/isocroft)
+- FEATURE [652](https://github.com/MatthewHerbst/react-to-print/issues/652): When using the `useReactToPrint` hook it is now possible to pass the returned callback the `content` ref at call time, rather than needing to pass it to the hook directly. This allows for generating the content to be printed closer to when the print occurs. Thanks [isocroft](https://github.com/isocroft)
 - DEPENDENCIES: Upgraded all `devDependencies` to their latest versions
 - CHORE: broke up the single file in the repo, started organizing things a bit
 
@@ -16,21 +16,21 @@ This is a republish of 2.14.14 since that version got screwed up by some [downti
 
 ## 2.14.14 (September 22nd, 2023)
 
-- FIX [635](https://github.com/gregnb/react-to-print/issues/635): Ensure proper handling of `<link>` nodes that have multiple value `rel` attributes set such as `rel="prefetch stylesheet"`, and, ensure proper handling of `<link>` nodes using `rel="preload" + as="style"`
-- DOCS [637](https://github.com/gregnb/react-to-print/issues/637): Added README section regarding having proper a `media` attribute set on `<link>` nodes
-- DOCS [633](https://github.com/gregnb/react-to-print/pull/633) Added README section regarding proper printing of scrolled containers. Thanks [siaikin](https://github.com/siaikin)!
+- FIX [635](https://github.com/MatthewHerbst/react-to-print/issues/635): Ensure proper handling of `<link>` nodes that have multiple value `rel` attributes set such as `rel="prefetch stylesheet"`, and, ensure proper handling of `<link>` nodes using `rel="preload" + as="style"`
+- DOCS [637](https://github.com/MatthewHerbst/react-to-print/issues/637): Added README section regarding having proper a `media` attribute set on `<link>` nodes
+- DOCS [633](https://github.com/MatthewHerbst/react-to-print/pull/633) Added README section regarding proper printing of scrolled containers. Thanks [siaikin](https://github.com/siaikin)!
 - DEPENDENCIES: Upgrade all `devDependencies` to their latest versions
 
 ## 2.14.13 (June 7th, 2023)
 
-- FIX [616](https://github.com/gregnb/react-to-print/issues/616): When passing a custom `print` function we were not waiting for that function to resolve its promise before removing the printing iframe if `removeAfterPrint={true}` was set. Further, we were not calling `onAfterPrint` at all when a custom printing function was passed. While not strictly needed since the caller knows when the printing has completed by resolving the promise, we now call `onAfterPrint` when that promise has resolved and before removing the print iframe
+- FIX [616](https://github.com/MatthewHerbst/react-to-print/issues/616): When passing a custom `print` function we were not waiting for that function to resolve its promise before removing the printing iframe if `removeAfterPrint={true}` was set. Further, we were not calling `onAfterPrint` at all when a custom printing function was passed. While not strictly needed since the caller knows when the printing has completed by resolving the promise, we now call `onAfterPrint` when that promise has resolved and before removing the print iframe
 - DEPENDENCIES: Removed our long unused single prod dependency, `prop-types`. The package now has zero `dependencies` 🪓
 - CHORE: Updated all `devDependencies` to their latest versions
 - CHORE: Removed a bunch of old unused files including `require.d.ts`, `.babelrc`, and an unused example
 
 ## 2.14.12 (February 18th, 2023)
 
-- FIX [565](https://github.com/gregnb/react-to-print/pull/565): Support font-weight and font-style for custom fonts (and add more font examples). Thanks [gauthierrodaro](https://github.com/gauthierrodaro)
+- FIX [565](https://github.com/MatthewHerbst/react-to-print/pull/565): Support font-weight and font-style for custom fonts (and add more font examples). Thanks [gauthierrodaro](https://github.com/gauthierrodaro)
 - CHORE: Updated all `devDependencies`
 
 ## 2.14.11 (January 3rd, 2023)
@@ -49,41 +49,41 @@ Happy new year! We can't wait to see what 2023 brings
 
 ## 2.14.10 (November 17th, 2022)
 
-- FIX [556](https://github.com/gregnb/react-to-print/pull/556) In 2.14.9 we changed the print `iframe` size to be dynamic but didn't take into account the fixed offset we were giving to hide it on the page. This resulted in the print `iframe` being partially visible when printing on wide screens. This has been corrected
+- FIX [556](https://github.com/MatthewHerbst/react-to-print/pull/556) In 2.14.9 we changed the print `iframe` size to be dynamic but didn't take into account the fixed offset we were giving to hide it on the page. This resulted in the print `iframe` being partially visible when printing on wide screens. This has been corrected
 
 ## 2.14.9 (November 14th, 2022)
 
-- FIX [553](https://github.com/gregnb/react-to-print/pull/553) Ensures that the `iframe` used for printing has the same viewport size as the parent window of the node being printed. Prior to this the browser set the default 300px/150px size on the `iframe`, causing code that changes styles based on viewport sizes (such as many grid systems) to sometimes change the display of the elements being printed, requiring CSS hacks to avoid. Thanks [dantecarlo](https://github.com/dantecarlo) for reviving this issue
+- FIX [553](https://github.com/MatthewHerbst/react-to-print/pull/553) Ensures that the `iframe` used for printing has the same viewport size as the parent window of the node being printed. Prior to this the browser set the default 300px/150px size on the `iframe`, causing code that changes styles based on viewport sizes (such as many grid systems) to sometimes change the display of the elements being printed, requiring CSS hacks to avoid. Thanks [dantecarlo](https://github.com/dantecarlo) for reviving this issue
 
 ## 2.14.8 (November 3rd, 2022)
 
-- FIX [537](https://github.com/gregnb/react-to-print/pull/537)/[545](https://github.com/gregnb/react-to-print/pull/543) `<link>` nodes marked with the `disabled` attribute were causing printing to hang. Thanks [luckrnx09](https://github.com/luckrnx09)
-- FIX/CHORE [545](https://github.com/gregnb/react-to-print/pull/545) Updated examples to use React 18. This also exposed a minor typing bug (`ReactToPrint` needed to specify a `children` prop to fully support React 18) which was corrected. Other dependencies were also updated, mostly dropping Node 12 support
-- CHORE [538](https://github.com/gregnb/react-to-print/pull/538) The examples had some minor Webpack related refactors
+- FIX [537](https://github.com/MatthewHerbst/react-to-print/pull/537)/[545](https://github.com/MatthewHerbst/react-to-print/pull/543) `<link>` nodes marked with the `disabled` attribute were causing printing to hang. Thanks [luckrnx09](https://github.com/luckrnx09)
+- FIX/CHORE [545](https://github.com/MatthewHerbst/react-to-print/pull/545) Updated examples to use React 18. This also exposed a minor typing bug (`ReactToPrint` needed to specify a `children` prop to fully support React 18) which was corrected. Other dependencies were also updated, mostly dropping Node 12 support
+- CHORE [538](https://github.com/MatthewHerbst/react-to-print/pull/538) The examples had some minor Webpack related refactors
 
 ## 2.14.7 (April 28th, 2022)
 
-- FIX [484](https://github.com/gregnb/react-to-print/issues/484): Previously `onAfterPrint` was not being called if a custom `print` function was passed. Now it will always be called
+- FIX [484](https://github.com/MatthewHerbst/react-to-print/issues/484): Previously `onAfterPrint` was not being called if a custom `print` function was passed. Now it will always be called
 - CHORE: a couple `devDependency` updates to make `npm audit` happy
 
 ## 2.14.6 (April 9th, 2022)
 
-- FIX [485](https://github.com/gregnb/react-to-print/issues/485): `react-to-print` assumed that the `tagName` of `<style>` nodes was always `'STYLE'`, however, sometimes it can be `'style'` or possibly other case combinations. Added resiliency to the check so now any casing of `'style'` will pass the check
+- FIX [485](https://github.com/MatthewHerbst/react-to-print/issues/485): `react-to-print` assumed that the `tagName` of `<style>` nodes was always `'STYLE'`, however, sometimes it can be `'style'` or possibly other case combinations. Added resiliency to the check so now any casing of `'style'` will pass the check
 
 ## 2.14.5 (March 31st, 2022)
 
-- FIX [479](https://github.com/gregnb/react-to-print/pull/479): React 18 is now a supported `peerDependency`. Thanks [fabb](https://github.com/fabb)
+- FIX [479](https://github.com/MatthewHerbst/react-to-print/pull/479): React 18 is now a supported `peerDependency`. Thanks [fabb](https://github.com/fabb)
 
 ## 2.14.4 (January 24th, 2022)
 
-- FIX [459](https://github.com/gregnb/react-to-print/issues/459): `react-to-print` now ensures that a `DOCTYPE` is set on the print iframe. Without this some browsers could render the print iframe in quirks mode, possibly changing the output
+- FIX [459](https://github.com/MatthewHerbst/react-to-print/issues/459): `react-to-print` now ensures that a `DOCTYPE` is set on the print iframe. Without this some browsers could render the print iframe in quirks mode, possibly changing the output
 - CHORE: Removed some debugging statements that made it into a previous production build
 - CHORE: Updated all dependencies
 - DOCS: Added a section with a link to a fully-working Electron example
 
 ## 2.14.3 (December 25th, 2021)
 
-- FIX [439](https://github.com/gregnb/react-to-print/issues/439): `react-to-print` now waits for `video` elements to load before printing. While this should work in most cases, we highly recommend setting the [`poster`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/video#attr-poster) attribute of the `video`, which allows specifying an image to be a placeholder for the video until the video loads.
+- FIX [439](https://github.com/MatthewHerbst/react-to-print/issues/439): `react-to-print` now waits for `video` elements to load before printing. While this should work in most cases, we highly recommend setting the [`poster`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/video#attr-poster) attribute of the `video`, which allows specifying an image to be a placeholder for the video until the video loads.
 - CHORE: cleaned up the examples code a bit, including adding tests for `video` elements
 - CHORE: all `devDependencies` have been upgraded to their latest and greatest
 
@@ -91,32 +91,32 @@ Happy new years!
 
 ## 2.14.2 (December 14th, 2021)
 
-- FIX: As seen in [441](https://github.com/gregnb/react-to-print/issues/441) when using the `useReactToPrint` hook along with TypeScript and strict checking the user is currently required to ensure that the return of `useReactToPrint` isn't `undefined`, since that is what is returned if the user is using a version of React that does not support hooks. To remove the need for this check `useReactToPrint` will now return a function that throws an error if the version of React does not support hooks.
+- FIX: As seen in [441](https://github.com/MatthewHerbst/react-to-print/issues/441) when using the `useReactToPrint` hook along with TypeScript and strict checking the user is currently required to ensure that the return of `useReactToPrint` isn't `undefined`, since that is what is returned if the user is using a version of React that does not support hooks. To remove the need for this check `useReactToPrint` will now return a function that throws an error if the version of React does not support hooks.
 
 ## 2.14.1 (November 21st, 2021)
 
-- FIX [429](https://github.com/gregnb/react-to-print/issues/429): Attempting to access the contents of a cross-origin stylesheet is forbidden by scripts, and attempting to do so would cause `react-to-print` to crash. Upstream work in the browsers is required to find a proper solution to this, read more in the issue. A `try/catch` has been added around the offending code, along with a warning message with tips on how to resolve. Thanks [@JoshuaKGoldberg](https://github.com/JoshuaKGoldberg) for lots of debugging help
-- FIX [432](https://github.com/gregnb/react-to-print/issues/432): TypeScript 4.4 shipped with `FontFace` support in its [lib definitions](https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/1029#issuecomment-869224737) which caused `react-to-print` to fail to build locally on versions of TypeScript >= 4.4 since our `FontFace` definitions clashed with those now in TypeScript. This has been resolved, thanks [@oxygen-xx](https://github.com/oxygen-xx)
-- DOCS [422](https://github.com/gregnb/react-to-print/pull/422): The README was updated to properly reflect that functional components can be used so long as they are wrapped with `React.forwardRef`
-- DOCS [430](https://github.com/gregnb/react-to-print/pull/430): A typo was fixed, thanks [@hsusanoo](https://github.com/hsusanoo)
+- FIX [429](https://github.com/MatthewHerbst/react-to-print/issues/429): Attempting to access the contents of a cross-origin stylesheet is forbidden by scripts, and attempting to do so would cause `react-to-print` to crash. Upstream work in the browsers is required to find a proper solution to this, read more in the issue. A `try/catch` has been added around the offending code, along with a warning message with tips on how to resolve. Thanks [@JoshuaKGoldberg](https://github.com/JoshuaKGoldberg) for lots of debugging help
+- FIX [432](https://github.com/MatthewHerbst/react-to-print/issues/432): TypeScript 4.4 shipped with `FontFace` support in its [lib definitions](https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/1029#issuecomment-869224737) which caused `react-to-print` to fail to build locally on versions of TypeScript >= 4.4 since our `FontFace` definitions clashed with those now in TypeScript. This has been resolved, thanks [@oxygen-xx](https://github.com/oxygen-xx)
+- DOCS [422](https://github.com/MatthewHerbst/react-to-print/pull/422): The README was updated to properly reflect that functional components can be used so long as they are wrapped with `React.forwardRef`
+- DOCS [430](https://github.com/MatthewHerbst/react-to-print/pull/430): A typo was fixed, thanks [@hsusanoo](https://github.com/hsusanoo)
 
 ## 2.14.0 (October 20th, 2021)
 
-- FIX [391](https://github.com/gregnb/react-to-print/issues/391): Setting `documentTitle` will now properly set the filename when printing as a PDF in Chrome, Firefox, and Safari
-- FIX: a rare (no reported events) edge case could cause printing to hang if an image failed to load and error logging was not enabled. [This has been fixed](https://github.com/gregnb/react-to-print/pull/418/commits/36baecc00fd68a1efa976c5a982463c78a0dca93#diff-0b5adbfe7b36e4ae2f479291e20152e33e940f7f265162d77f40f6bdb5da7405L333)
+- FIX [391](https://github.com/MatthewHerbst/react-to-print/issues/391): Setting `documentTitle` will now properly set the filename when printing as a PDF in Chrome, Firefox, and Safari
+- FIX: a rare (no reported events) edge case could cause printing to hang if an image failed to load and error logging was not enabled. [This has been fixed](https://github.com/MatthewHerbst/react-to-print/pull/418/commits/36baecc00fd68a1efa976c5a982463c78a0dca93#diff-0b5adbfe7b36e4ae2f479291e20152e33e940f7f265162d77f40f6bdb5da7405L333)
 - FEATURE: the UI for running the examples has been massively improved. Try them out! We will be porting this to our official CodeSandbox example soon.
 - CHORE: changed an error message saying only class based components are allowed to be printed to clarify that functional components wrapped in `React.forwardRef` can be printed as well
 - CHORE: refactored logging code to be DRYer and simpler to use
 - CHORE: all `devDependencies` have been upgraded to their latest and greatest
-- DOCS: major improvements to the README, including making some examples more concise, adding information about using functional components to print, adding some new pitfalls, and adding information about known issues when printing in mobile WebViews (see [#384](https://github.com/gregnb/react-to-print/issues/384) for more)
+- DOCS: major improvements to the README, including making some examples more concise, adding information about using functional components to print, adding some new pitfalls, and adding information about known issues when printing in mobile WebViews (see [#384](https://github.com/MatthewHerbst/react-to-print/issues/384) for more)
 
 ## 2.13.0 (August 4th, 2021)
 
-- FEATURE [402](https://github.com/gregnb/react-to-print/pull/402): support passing a `nonce` property to be used with CSP. Thanks [@Arcturus5404]((https://github.com/Arcturus5404)) and [@nenonja](https://github.com/nenonja)
+- FEATURE [402](https://github.com/MatthewHerbst/react-to-print/pull/402): support passing a `nonce` property to be used with CSP. Thanks [@Arcturus5404]((https://github.com/Arcturus5404)) and [@nenonja](https://github.com/nenonja)
 
 ## 2.12.6 (May 31st, 2021)
 
-- FIX [379](https://github.com/gregnb/react-to-print/pull/379): `img` tags missing a `src` attribute should not prevent printing
+- FIX [379](https://github.com/MatthewHerbst/react-to-print/pull/379): `img` tags missing a `src` attribute should not prevent printing
 
 ## 2.12.5 (May 29th, 2021)
 
@@ -129,23 +129,23 @@ Happy new years!
 
 ## 2.12.3 (February 5th, 2021)
 
-- FIX [344](https://github.com/gregnb/react-to-print/pull/344): Remove the single use of [`ParentNode.append`](https://developer.mozilla.org/en-US/docs/Web/API/ParentNode/append) in favor of [`Node.appendChild`](https://developer.mozilla.org/en-US/docs/Web/API/Node/appendChild). `append` is not supported by IE11, and polyfilling it within the context of an iframe can be difficult
-- FIX [344](https://github.com/gregnb/react-to-print/pull/344): While testing the above I realized that trying to print out a bare string didn't work. This has been fixed
+- FIX [344](https://github.com/MatthewHerbst/react-to-print/pull/344): Remove the single use of [`ParentNode.append`](https://developer.mozilla.org/en-US/docs/Web/API/ParentNode/append) in favor of [`Node.appendChild`](https://developer.mozilla.org/en-US/docs/Web/API/Node/appendChild). `append` is not supported by IE11, and polyfilling it within the context of an iframe can be difficult
+- FIX [344](https://github.com/MatthewHerbst/react-to-print/pull/344): While testing the above I realized that trying to print out a bare string didn't work. This has been fixed
 - CHORE: Upgraded all `devDependencies`
 
 ## 2.12.2 (January 1st, 2021)
 
 Happy new years!
 
-- FIX [196](https://github.com/gregnb/react-to-print/issues/196): For a long time various inputs/select did not properly copy their value over into the print window. This has been corrected!
-- FIX [292](https://github.com/gregnb/react-to-print/issues/292): Removed usage of `document.write`
+- FIX [196](https://github.com/MatthewHerbst/react-to-print/issues/196): For a long time various inputs/select did not properly copy their value over into the print window. This has been corrected!
+- FIX [292](https://github.com/MatthewHerbst/react-to-print/issues/292): Removed usage of `document.write`
 - FIX: Edge case where passing a function to the `pageStyle` prop that did not return a string could cause problems
 - CHORE: Upgraded all `devDependencies`
 - CHORE: Minor README updates
 
 ## 2.12.1 (December 14th, 2020)
 
-- FIX [329](https://github.com/gregnb/react-to-print/pull/329): v2.12.0 upgraded Webpack from 4 -> 5 which broke the package for environments that didn't support ES6 as Webpack now requires finer grained controls to output pure ES5 code. These changes have been made.
+- FIX [329](https://github.com/MatthewHerbst/react-to-print/pull/329): v2.12.0 upgraded Webpack from 4 -> 5 which broke the package for environments that didn't support ES6 as Webpack now requires finer grained controls to output pure ES5 code. These changes have been made.
 - CHORE: upgraded all devDependencies
 
 ## 2.12.0 (November 27th, 2020)
@@ -154,46 +154,46 @@ Happy new years!
 - CHORE: upgraded all devDependencies. Big changes here include updating Typescript from 3 -> 4 and Webpack from 4 -> 5. While upgrading Webpack the minifier was changed from UglifyJS to Terser, resulting in a 5.7% reduced file size (14.1kb -> 13.3kb)
 - CHORE: Use Node ^14 for CLI tests
 - DOCUMENTATION: small improvements to the examples, including renaming them from `example` -> `examples`
-- DOCUMENTATION: added a note about finding the [`examples`](https://github.com/gregnb/react-to-print/tree/master/examples) folder
-- DOCUMENTATION [311](https://github.com/gregnb/react-to-print/issues/311): small type fix, thanks [nealeu](https://github.com/nealeu)
+- DOCUMENTATION: added a note about finding the [`examples`](https://github.com/MatthewHerbst/react-to-print/tree/master/examples) folder
+- DOCUMENTATION [311](https://github.com/MatthewHerbst/react-to-print/issues/311): small type fix, thanks [nealeu](https://github.com/nealeu)
 - DOCUMENTATION: added a "Common Pitfalls" section to the README, starting with a note on using the library with a component wrapped in `connect` from `react-redux`
 
 ## 2.11.0 (October 30th, 2020)
 
-- FIX/FEATURE [285](https://github.com/gregnb/react-to-print/pull/285): Adds a new `fonts` prop which allows the passing of custom fonts. Previously custom fonts were not loaded into the print window
+- FIX/FEATURE [285](https://github.com/MatthewHerbst/react-to-print/pull/285): Adds a new `fonts` prop which allows the passing of custom fonts. Previously custom fonts were not loaded into the print window
 - CHORE: update patch and minor `devDependencies`, `dedupe`, and `audit fix`
 
 ## 2.10.3 (October 16th, 2020)
 
-- FIX [301](https://github.com/gregnb/react-to-print/pull/301): Ensures the library works with modules that have a `null` prototype such as ES modules and SystemJS modules. Thanks [joeldenning](https://github.com/joeldenning)
+- FIX [301](https://github.com/MatthewHerbst/react-to-print/pull/301): Ensures the library works with modules that have a `null` prototype such as ES modules and SystemJS modules. Thanks [joeldenning](https://github.com/joeldenning)
 
 ## 2.10.2 (October 16th, 2020)
 
-- FIX [298](https://github.com/gregnb/react-to-print/pull/298): Fixes a long-standing issue of checkbox state not always copying properly into the print window. Thanks [aviklai](https://github.com/aviklai)
+- FIX [298](https://github.com/MatthewHerbst/react-to-print/pull/298): Fixes a long-standing issue of checkbox state not always copying properly into the print window. Thanks [aviklai](https://github.com/aviklai)
 - CHORE: update patch and minor `devDependencies`, `dedupe`, and `audit fix`
 
 ## 2.10.1 (October 15th, 2020)
 
-- FIX [296](https://github.com/gregnb/react-to-print/pull/296): Ensure `bodyClass` can handle multiple class names instead of just a single class name. Thanks [seanblonien](https://github.com/seanblonien)
+- FIX [296](https://github.com/MatthewHerbst/react-to-print/pull/296): Ensure `bodyClass` can handle multiple class names instead of just a single class name. Thanks [seanblonien](https://github.com/seanblonien)
 - CHORE: update patch and minor `devDependencies`, `dedupe`, and `audit fix`
 
 ## 2.10.0 (August 23rd, 2020)
 
-- FEATURE [272](https://github.com/gregnb/react-to-print/pull/272): a new prop `print` has been added. This can be used to override the default browser [`Window.print`](https://developer.mozilla.org/en-US/docs/Web/API/Window/print). This can be useful if you want to print in an alternative environment such as Electron. As part of this change, `onPrintError` will now report if an error occurs in a passed in `print` method. Thanks to [Ririshi](https://github.com/Ririshi) for this idea
-- DOCS [269](https://github.com/gregnb/react-to-print/pull/269): added guidelines for how to achieve nice page breaks. Thanks [hbrannan](https://github.com/hbrannan)
-- CHORE [273](https://github.com/gregnb/react-to-print/pull/273): updated `devDependencies`, `npm dedupe`, `npm audit fix`
+- FEATURE [272](https://github.com/MatthewHerbst/react-to-print/pull/272): a new prop `print` has been added. This can be used to override the default browser [`Window.print`](https://developer.mozilla.org/en-US/docs/Web/API/Window/print). This can be useful if you want to print in an alternative environment such as Electron. As part of this change, `onPrintError` will now report if an error occurs in a passed in `print` method. Thanks to [Ririshi](https://github.com/Ririshi) for this idea
+- DOCS [269](https://github.com/MatthewHerbst/react-to-print/pull/269): added guidelines for how to achieve nice page breaks. Thanks [hbrannan](https://github.com/hbrannan)
+- CHORE [273](https://github.com/MatthewHerbst/react-to-print/pull/273): updated `devDependencies`, `npm dedupe`, `npm audit fix`
 
 ## 2.9.0 (June 2nd, 2020)
 
-- FEATURE [255](https://github.com/gregnb/react-to-print/pull/255): updated local development examples so that every use case is covered
-- FIX [255](https://github.com/gregnb/react-to-print/pull/255): `onload` event listener is now cleared after being called
-- FIX [255](https://github.com/gregnb/react-to-print/pull/255): `useReactToPrint` now properly sets `defaultProps`
-- CHORE [256](https://github.com/gregnb/react-to-print/pull/256): updated `devDependencies` to latest. This clears a high severity `npm audit` issue
+- FEATURE [255](https://github.com/MatthewHerbst/react-to-print/pull/255): updated local development examples so that every use case is covered
+- FIX [255](https://github.com/MatthewHerbst/react-to-print/pull/255): `onload` event listener is now cleared after being called
+- FIX [255](https://github.com/MatthewHerbst/react-to-print/pull/255): `useReactToPrint` now properly sets `defaultProps`
+- CHORE [256](https://github.com/MatthewHerbst/react-to-print/pull/256): updated `devDependencies` to latest. This clears a high severity `npm audit` issue
 
 ## 2.8.0 (May 19th, 2020)
 
-- FEATURE [245](https://github.com/gregnb/react-to-print/pull/245): `documentTitle` prop can now be passed to set a default filename when the user is saving as a PDF. Thanks [zb2oby](https://github.com/zb2oby)
-- FEATURE [244](https://github.com/gregnb/react-to-print/pull/244): `trigger` is now an optional prop. To print without it we now offer two new options.
+- FEATURE [245](https://github.com/MatthewHerbst/react-to-print/pull/245): `documentTitle` prop can now be passed to set a default filename when the user is saving as a PDF. Thanks [zb2oby](https://github.com/zb2oby)
+- FEATURE [244](https://github.com/MatthewHerbst/react-to-print/pull/244): `trigger` is now an optional prop. To print without it we now offer two new options.
 
   `PrintContextConsumer` with a render-props pattern:
 
@@ -231,10 +231,10 @@ Happy new years!
 
 ## 2.7.0 (May 1st, 2020)
 
-- FEATURE [198](https://github.com/gregnb/react-to-print/pull/198): `pageStyle` prop can now be passed as a function. Thanks [sergeyshmakov](https://github.com/sergeyshmakov)
-- FIX [218](https://github.com/gregnb/react-to-print/issues/218): Image duplication in Edge and IE. This should also fix [211](https://github.com/gregnb/react-to-print/issues/211) (slow performance with many images on the page). Thank you [dioscarey](https://github.com/dioscarey) for helping to get this pushed through
-- Fix [93](https://github.com/gregnb/react-to-print/issues/93): Check for existence of `target.contentWindow.print`
-- CHORE: updated an error message (see [96](https://github.com/gregnb/react-to-print/issues/96))
+- FEATURE [198](https://github.com/MatthewHerbst/react-to-print/pull/198): `pageStyle` prop can now be passed as a function. Thanks [sergeyshmakov](https://github.com/sergeyshmakov)
+- FIX [218](https://github.com/MatthewHerbst/react-to-print/issues/218): Image duplication in Edge and IE. This should also fix [211](https://github.com/MatthewHerbst/react-to-print/issues/211) (slow performance with many images on the page). Thank you [dioscarey](https://github.com/dioscarey) for helping to get this pushed through
+- Fix [93](https://github.com/MatthewHerbst/react-to-print/issues/93): Check for existence of `target.contentWindow.print`
+- CHORE: updated an error message (see [96](https://github.com/MatthewHerbst/react-to-print/issues/96))
 - CHORE: updated all `devDependencies` to latest
 - CHORE: slightly decreased size of the build by better using UglifyJS
 - CHORE: enabled TypeScript strict mode
@@ -243,80 +243,80 @@ Happy new years!
 
 ## 2.6.3 (March 9th, 2020)
 
-- FIX [227](https://github.com/gregnb/react-to-print/pull/227) Add a `title` to the print iframe to improve accessibility. Thanks [invious](https://github.com/invious)
+- FIX [227](https://github.com/MatthewHerbst/react-to-print/pull/227) Add a `title` to the print iframe to improve accessibility. Thanks [invious](https://github.com/invious)
 
 ## 2.6.2 (March 8th, 2020)
 
-- FIX [224](https://github.com/gregnb/react-to-print/pull/224) Handle the `content` prop returning `null`. This is required for proper usage in TypeScript strict mode. Thanks [a-sync](https://github.com/a-sync)
+- FIX [224](https://github.com/MatthewHerbst/react-to-print/pull/224) Handle the `content` prop returning `null`. This is required for proper usage in TypeScript strict mode. Thanks [a-sync](https://github.com/a-sync)
 
 ## 2.6.1 (March 3rd, 2020)
 
-- CHORE [220](https://github.com/gregnb/react-to-print/pull/222) Added `suppressErrors` documentation to the README
+- CHORE [220](https://github.com/MatthewHerbst/react-to-print/pull/222) Added `suppressErrors` documentation to the README
 
 ## 2.6.0 (March 3rd, 2020)
 
-- FEATURE [220](https://github.com/gregnb/react-to-print/pull/220) Adds a `suppressErrors` prop. When passed, console logging of errors is disabled. Thanks [invious](https://github.com/invious)
+- FEATURE [220](https://github.com/MatthewHerbst/react-to-print/pull/220) Adds a `suppressErrors` prop. When passed, console logging of errors is disabled. Thanks [invious](https://github.com/invious)
 
 ## 2.5.1 (January 9th, 2020)
 
-- CHORE [208](https://github.com/gregnb/react-to-print/pull/208) Minor improvements to code comments, linting, and README
+- CHORE [208](https://github.com/MatthewHerbst/react-to-print/pull/208) Minor improvements to code comments, linting, and README
 
-- CHORE [207](https://github.com/gregnb/react-to-print/pull/207) Updated `devDependencies`
+- CHORE [207](https://github.com/MatthewHerbst/react-to-print/pull/207) Updated `devDependencies`
 
-- FIX [204](https://github.com/gregnb/react-to-print/pull/204): Ensure images are fully loaded before printing. Previously long-loading images might not be included in the print. This ensures that we wait for them to load, similar to how we wait for style sheets to load. Thanks [nhanhuynh-agilityio](https://github.com/nhanhuynh-agilityio)
+- FIX [204](https://github.com/MatthewHerbst/react-to-print/pull/204): Ensure images are fully loaded before printing. Previously long-loading images might not be included in the print. This ensures that we wait for them to load, similar to how we wait for style sheets to load. Thanks [nhanhuynh-agilityio](https://github.com/nhanhuynh-agilityio)
 
 ## 2.5.0 (October 16th, 2019)
 
-- FEATURE [172](https://github.com/gregnb/react-to-print/pull/172): Allow the `trigger` component to be a functional component. Previously, only class based components were allowed here. Thanks [idanhaviv](https://github.com/idanhaviv)
+- FEATURE [172](https://github.com/MatthewHerbst/react-to-print/pull/172): Allow the `trigger` component to be a functional component. Previously, only class based components were allowed here. Thanks [idanhaviv](https://github.com/idanhaviv)
 
-- FEATURE [172](https://github.com/gregnb/react-to-print/pull/172): Enable CSS HMR when running the local example build. Thanks [idanhaviv](https://github.com/idanhaviv)
+- FEATURE [172](https://github.com/MatthewHerbst/react-to-print/pull/172): Enable CSS HMR when running the local example build. Thanks [idanhaviv](https://github.com/idanhaviv)
 
 ## 2.4.0 (August 27th, 2019)
 
-- FEATURE [161](https://github.com/gregnb/react-to-print/pull/161): add a new callback method `onPrintError`. This method is called when `react-to-print` catches a Promise rejection in either `onBeforeGetContent` or `onBeforePrint`. The API docs were also cleaned up to better explain which method to use when.
+- FEATURE [161](https://github.com/MatthewHerbst/react-to-print/pull/161): add a new callback method `onPrintError`. This method is called when `react-to-print` catches a Promise rejection in either `onBeforeGetContent` or `onBeforePrint`. The API docs were also cleaned up to better explain which method to use when.
 
-- FEATURE [158](https://github.com/gregnb/react-to-print/pull/158)/[160](https://github.com/gregnb/react-to-print/pull/160): add new callback method `onBeforeGetContent`. Currently, `onBeforePrint` is called before the print window is opened but after `react-to-print` has gathered the content of the page. This new method is fired before `react-to-print` gathers the content of the page, meaning it can be used to change the content of the page before printing. It can optionally return a `Promise`. Thanks [@andfs](https://github.com/andfs)
+- FEATURE [158](https://github.com/MatthewHerbst/react-to-print/pull/158)/[160](https://github.com/MatthewHerbst/react-to-print/pull/160): add new callback method `onBeforeGetContent`. Currently, `onBeforePrint` is called before the print window is opened but after `react-to-print` has gathered the content of the page. This new method is fired before `react-to-print` gathers the content of the page, meaning it can be used to change the content of the page before printing. It can optionally return a `Promise`. Thanks [@andfs](https://github.com/andfs)
 
 ## 2.3.2 (August 6th, 2019)
 
-- CHORE [156](https://github.com/gregnb/react-to-print/pull/156): dependency upgrades. All listed dependencies were manually upgraded to their latest versions. `npm audit fix` was then run to give us a clean audit. Finally, `npm dedupe` was run to reduce package bloat.
+- CHORE [156](https://github.com/MatthewHerbst/react-to-print/pull/156): dependency upgrades. All listed dependencies were manually upgraded to their latest versions. `npm audit fix` was then run to give us a clean audit. Finally, `npm dedupe` was run to reduce package bloat.
 
-- FIX [156](https://github.com/gregnb/react-to-print/pull/156): a stylesheet that no longer exists but that was being required by the local example has been removed
+- FIX [156](https://github.com/MatthewHerbst/react-to-print/pull/156): a stylesheet that no longer exists but that was being required by the local example has been removed
 
 *NOTE*: To build the library locally, Node ^8.6 is now required
 
 ## 2.3.1 (August 6th, 2019)
 
-- FIX [154](https://github.com/gregnb/react-to-print/pull/154): TSLint was not working properly for the project. A configuration was added, and linting errors were fixed. While fixing linting errors, a bug was discovered whereby if a stylesheet was found that did not have tag type `STYLE` it was possible that `react-to-print` would not include all stylesheets from the page into the print window
+- FIX [154](https://github.com/MatthewHerbst/react-to-print/pull/154): TSLint was not working properly for the project. A configuration was added, and linting errors were fixed. While fixing linting errors, a bug was discovered whereby if a stylesheet was found that did not have tag type `STYLE` it was possible that `react-to-print` would not include all stylesheets from the page into the print window
 
-- FIX: [154](https://github.com/gregnb/react-to-print/pull/154) (meant to be a different PR, was included by mistake in 154): When passing `removeAfterPrint` some users were getting the error `TypeError: Object doesn't support property or method 'remove'`. This was due to using an incorrect way to remove the iframe
+- FIX: [154](https://github.com/MatthewHerbst/react-to-print/pull/154) (meant to be a different PR, was included by mistake in 154): When passing `removeAfterPrint` some users were getting the error `TypeError: Object doesn't support property or method 'remove'`. This was due to using an incorrect way to remove the iframe
 
 ## 2.3.0 (July 30th, 2019)
 
-- FEATURE [152](https://github.com/gregnb/react-to-print/pull/152): Previously, this library used a window rather than an `iframe` to handle printing. That was changed some time ago, however, the `closeAfterPrint` prop was never removed from the documentation (though it was removed from the code). This release restores similar functionality, in a new `removeAfterPrint` prop. Passing this prop will ensure that `react-to-print` removes the `iframe` it uses to print from the DOM after printing (something that it currently does not do). NOTE: the `iframe` is removed after the call to `onAfterPrint` (if provided) has completed. We will likely make this the default functionality in version 3, but are keeping it like this for now to ensure anyone relying on the `iframe` does not face issues. Thanks [aviklai](https://github.com/aviklai)
+- FEATURE [152](https://github.com/MatthewHerbst/react-to-print/pull/152): Previously, this library used a window rather than an `iframe` to handle printing. That was changed some time ago, however, the `closeAfterPrint` prop was never removed from the documentation (though it was removed from the code). This release restores similar functionality, in a new `removeAfterPrint` prop. Passing this prop will ensure that `react-to-print` removes the `iframe` it uses to print from the DOM after printing (something that it currently does not do). NOTE: the `iframe` is removed after the call to `onAfterPrint` (if provided) has completed. We will likely make this the default functionality in version 3, but are keeping it like this for now to ensure anyone relying on the `iframe` does not face issues. Thanks [aviklai](https://github.com/aviklai)
 
 ## 2.2.1 (July 22nd, 2019)
 
-- FIX [149](https://github.com/gregnb/react-to-print/pull/149): Print window would not open if `onBeforePrint` was not given. Thanks [aviklai](https://github.com/aviklai)
+- FIX [149](https://github.com/MatthewHerbst/react-to-print/pull/149): Print window would not open if `onBeforePrint` was not given. Thanks [aviklai](https://github.com/aviklai)
 
 ## 2.2.0 (July 19th, 2019)
 
-- FEATURE [140](https://github.com/gregnb/react-to-print/issues/140): `onBeforePrint` can now optionally return a Promise. If a Promise is returned, `react-to-print` will wait for it to resolve before continuing with the print. NOTE: `react-to-print` does not handle if the Promise rejects, so this must be accounted for when using this option. Thanks [aviklai](https://github.com/aviklai)
+- FEATURE [140](https://github.com/MatthewHerbst/react-to-print/issues/140): `onBeforePrint` can now optionally return a Promise. If a Promise is returned, `react-to-print` will wait for it to resolve before continuing with the print. NOTE: `react-to-print` does not handle if the Promise rejects, so this must be accounted for when using this option. Thanks [aviklai](https://github.com/aviklai)
 
 ## 2.1.3 (June 22nd, 2019)
 
-- FIX [134](https://github.com/gregnb/react-to-print/pull/134): Solve print window issues in Safari (especially Mobile Safari), thanks [Ellenergic](https://github.com/Ellenergic)
+- FIX [134](https://github.com/MatthewHerbst/react-to-print/pull/134): Solve print window issues in Safari (especially Mobile Safari), thanks [Ellenergic](https://github.com/Ellenergic)
 - CHORE: Updated the README to contain a link to a fully updated demo
 
 ## 2.1.2 (May 3rd, 2019)
 
-- FIX [118](https://github.com/gregnb/react-to-print/issues/118): Ensure fonts have time to load before printing, thanks [aviklai](https://github.com/aviklai)
+- FIX [118](https://github.com/MatthewHerbst/react-to-print/issues/118): Ensure fonts have time to load before printing, thanks [aviklai](https://github.com/aviklai)
 
 ## 2.1.1 (April 13th, 2019)
 
-- FIX: Ensure we build the package as UMD instead of CommonJS ([#116](https://github.com/gregnb/react-to-print/pull/116), thanks [@aviklai](https://github.com/aviklai))
+- FIX: Ensure we build the package as UMD instead of CommonJS ([#116](https://github.com/MatthewHerbst/react-to-print/pull/116), thanks [@aviklai](https://github.com/aviklai))
 - CHORE: Added a CHANGELOG
 
 ## 2.1.0 (April 2nd, 2019)
 
-- CHORE: Convert the package to TypeScript ([#111](https://github.com/gregnb/react-to-print/pull/111), thanks [@sergeyshmakov](https://github.com/sergeyshmakov))
+- CHORE: Convert the package to TypeScript ([#111](https://github.com/MatthewHerbst/react-to-print/pull/111), thanks [@sergeyshmakov](https://github.com/sergeyshmakov))
diff --git a/LICENSE b/LICENSE
index de9ab97..ccac07d 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023 gregnb, Matthew Herbst
+Copyright (c) 2024 Matthew Herbst, Gregory Nowakowski
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
diff --git a/README.md b/README.md
index 82b897e..24c4890 100644
--- a/README.md
+++ b/README.md
@@ -57,7 +57,7 @@ For functional components, use the `useReactToPrint` hook, which accepts an obje
 
 While printing on mobile browsers should work, printing within a WebView (when your page is opened by another app such as Facebook or Slack, but not by the full browser itself) is known to not work on many if not all WebViews. Some don't make the correct API available. Others make it available but cause printing to no-op when in WebView.
 
-We are actively researching resolutions to this issue, but it likely requires changes by Google/Chromium and Apple/WebKit. See [#384](https://github.com/gregnb/react-to-print/issues/384) for more information. If you know of a way we can solve this, your help would be greatly appreciated.
+We are actively researching resolutions to this issue, but it likely requires changes by Google/Chromium and Apple/WebKit. See [#384](https://github.com/MatthewHerbst/react-to-print/issues/384) for more information. If you know of a way we can solve this, your help would be greatly appreciated.
 
 ### Known Incompatible Browsers
 
@@ -191,7 +191,7 @@ export const AnotherExample = () => {
 }
 ```
 
-**Note ([401](https://github.com/gregnb/react-to-print/issues/401)):** In TypeScript, if you encounter `componentRef.current` error such as: `Type 'undefined' is not assignable to type 'ReactInstance | null'.`, add `null` inside the `useRef()`:
+**Note ([401](https://github.com/MatthewHerbst/react-to-print/issues/401)):** In TypeScript, if you encounter `componentRef.current` error such as: `Type 'undefined' is not assignable to type 'ReactInstance | null'.`, add `null` inside the `useRef()`:
 
 ```ts
 const componentRef = useRef(null);
@@ -217,11 +217,11 @@ const componentRef = useRef(null);
   div.parent p { color:red; }
   ```
 
-- The `connect` method from `react-redux` returns a functional component that cannot be assigned a reference to be used within the `content` props' callback in `react-to-print`. To use a component wrapped in `connect` within `content` create an intermediate class component that simply renders your component wrapped in `connect`. See [280](https://github.com/gregnb/react-to-print/issues/280) for more.
+- The `connect` method from `react-redux` returns a functional component that cannot be assigned a reference to be used within the `content` props' callback in `react-to-print`. To use a component wrapped in `connect` within `content` create an intermediate class component that simply renders your component wrapped in `connect`. See [280](https://github.com/MatthewHerbst/react-to-print/issues/280) for more.
 
-- Using a custom component as the return for the `trigger` props is possible, just ensure you pass along the `onClick` prop. See [248](https://github.com/gregnb/react-to-print/issues/248) for an example.
+- Using a custom component as the return for the `trigger` props is possible, just ensure you pass along the `onClick` prop. See [248](https://github.com/MatthewHerbst/react-to-print/issues/248) for an example.
 
-- When rendering multiple components to print, for example, if you have a list of charts and want each chart to have its own print icon, ideally you will wrap each component to print + print button in its own component, and just render a list of those components. However, if you cannot do that for some reason, in your `.map` ensure that each component gets a unique `ref` value passed to it, otherwise printing any of the components will always print the last component. See [323](https://github.com/gregnb/react-to-print/issues/323) for more.
+- When rendering multiple components to print, for example, if you have a list of charts and want each chart to have its own print icon, ideally you will wrap each component to print + print button in its own component, and just render a list of those components. However, if you cannot do that for some reason, in your `.map` ensure that each component gets a unique `ref` value passed to it, otherwise printing any of the components will always print the last component. See [323](https://github.com/MatthewHerbst/react-to-print/issues/323) for more.
 
 ## FAQ
 
@@ -239,7 +239,7 @@ const handlePrint = useReactToPrint({
 });
 ```
 
-For examples of how others have done this, see [#484](https://github.com/gregnb/react-to-print/issues/484)
+For examples of how others have done this, see [#484](https://github.com/MatthewHerbst/react-to-print/issues/484)
 
 ### Can the `ComponentToPrint` be a functional component?
 
@@ -344,7 +344,7 @@ The default page size is usually A4. Most browsers do not allow JavaScript or CS
 }
 ```
 
-### Set custom margin to the page ([29](https://github.com/gregnb/react-to-print/issues/29))
+### Set custom margin to the page ([29](https://github.com/MatthewHerbst/react-to-print/issues/29))
 
 To set custom margin to the page,
 
@@ -364,7 +364,7 @@ Now, within the JSX call this function within the style tags,
 
 PS: This style tag should be inside the component that is being passed in as the content ref.
 
-### Set landscape printing ([240](https://github.com/gregnb/react-to-print/issues/240))
+### Set landscape printing ([240](https://github.com/MatthewHerbst/react-to-print/issues/240))
 
 In the component that is passed in as the content ref, add the following:
 
@@ -374,7 +374,7 @@ In the component that is passed in as the content ref, add the following:
 }
 ```
 
-### Printing elements that are not displayed ([159](https://github.com/gregnb/react-to-print/issues/159))
+### Printing elements that are not displayed ([159](https://github.com/MatthewHerbst/react-to-print/issues/159))
 
 Instead of using `{ display: 'none'; }`, try using `{ overflow: hidden; height: 0; }`
 
@@ -384,7 +384,7 @@ The `pageStyle` prop should be a CSS string. For example: `".divider { break-aft
 
 ### Getting a blank page when printing
 
-Many have found setting the following CSS helpful. See [#26](https://github.com/gregnb/react-to-print/issues/26) for more.
+Many have found setting the following CSS helpful. See [#26](https://github.com/MatthewHerbst/react-to-print/issues/26) for more.
 
 ```css
 @media print {
@@ -403,7 +403,7 @@ If you are getting a blank page while setting `removeAfterPrint` to `true`, try
 
 ### Styles incorrect in print dialog when using grid system
 
-We often ([#327](https://github.com/gregnb/react-to-print/issues/327), [#343](https://github.com/gregnb/react-to-print/issues/343), [#382](https://github.com/gregnb/react-to-print/issues/382)) see issues reported where the developer is using Bootstrap or a similar grid system, and everything works great until the user goes to print and suddenly it seems the styles are off. We've found that often the issue is the grid library uses the smallest sized columns during printing, such as the `xs` size on Bootstrap's grid, a size developers often don't plan for. The simplest solution is to ensure your grid will adapt to this size appropriately, though this may not be acceptable since you may want the large view to print rather than the smaller view. Another solution is to [override the grid column definition](https://stackoverflow.com/questions/22199429/bootstrap-grid-for-printing/28152320). Some newer versions of libraries have specific tools for dealing with printing, for example, [Bootstrap 4's Display property](https://getbootstrap.com/docs/4.3/utilities/display/).
+We often ([#327](https://github.com/MatthewHerbst/react-to-print/issues/327), [#343](https://github.com/MatthewHerbst/react-to-print/issues/343), [#382](https://github.com/MatthewHerbst/react-to-print/issues/382)) see issues reported where the developer is using Bootstrap or a similar grid system, and everything works great until the user goes to print and suddenly it seems the styles are off. We've found that often the issue is the grid library uses the smallest sized columns during printing, such as the `xs` size on Bootstrap's grid, a size developers often don't plan for. The simplest solution is to ensure your grid will adapt to this size appropriately, though this may not be acceptable since you may want the large view to print rather than the smaller view. Another solution is to [override the grid column definition](https://stackoverflow.com/questions/22199429/bootstrap-grid-for-printing/28152320). Some newer versions of libraries have specific tools for dealing with printing, for example, [Bootstrap 4's Display property](https://getbootstrap.com/docs/4.3/utilities/display/).
 
 ### Page Breaks
 
@@ -472,14 +472,14 @@ If your content rendered as print media does not automatically break multi-page
 - A style of `position: absolute`, when rendered to print, may result in reformatted, rotated, or re-scaled content, causing unintended affects to print page layout and page breaks
 - Using `flex` may interfere with page breaks, try using `display: block`
 
-### Handling Scrolling ([603](https://github.com/gregnb/react-to-print/issues/603))
+### Handling Scrolling ([603](https://github.com/MatthewHerbst/react-to-print/issues/603))
 
 [![Edit react-to-print (Handling Scrolling)](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/react-to-print-handling-scrolling-n4mxyj?fontsize=14&hidenavigation=1&theme=dark)
 
 If you need to print the content of a scrolling container, you may encounter the following issues:
 
-- [Unable to control the scroll position](https://github.com/gregnb/react-to-print/issues/603#issue-1647664811), so the printed content may not be what you want.
-- [Overflow content is truncated](https://github.com/gregnb/react-to-print/issues/603#issuecomment-1649604330), resulting in missing printed content.
+- [Unable to control the scroll position](https://github.com/MatthewHerbst/react-to-print/issues/603#issue-1647664811), so the printed content may not be what you want.
+- [Overflow content is truncated](https://github.com/MatthewHerbst/react-to-print/issues/603#issuecomment-1649604330), resulting in missing printed content.
 
 To solve these problems, you need to modify the properties of the scrolling container when printing. You can pass a function to the `print` property, which will be called when printing. In this function, you can use the DOM API to query the scrolling container that needs to be modified, and then modify its properties to **control the scroll position**.
 
diff --git a/examples/ComponentToPrint/index.tsx b/examples/ComponentToPrint/index.tsx
index b27b8b1..a3e91af 100644
--- a/examples/ComponentToPrint/index.tsx
+++ b/examples/ComponentToPrint/index.tsx
@@ -49,7 +49,7 @@ export class ComponentToPrint extends React.PureComponent<Props, State> {
       <div className="relativeCSS">
         <link
           // This tests that we properly ignore disabled nodes
-          // Learn more: https://github.com/gregnb/react-to-print/pull/537
+          // Learn more: https://github.com/MatthewHerbst/react-to-print/pull/537
           // eslint-disable-next-line @typescript-eslint/ban-ts-comment
           // @ts-ignore
           disabled
diff --git a/package.json b/package.json
index de5494c..03c98c8 100644
--- a/package.json
+++ b/package.json
@@ -15,7 +15,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/gregnb/react-to-print.git"
+    "url": "git+https://github.com/MatthewHerbst/react-to-print.git"
   },
   "keywords": [
     "react",
@@ -29,9 +29,9 @@
   ],
   "license": "MIT",
   "bugs": {
-    "url": "https://github.com/gregnb/react-to-print/issues"
+    "url": "https://github.com/MatthewHerbst/react-to-print/issues"
   },
-  "homepage": "https://github.com/gregnb/react-to-print#readme",
+  "homepage": "https://github.com/MatthewHerbst/react-to-print#readme",
   "peerDependencies": {
     "react": "^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0",
     "react-dom": "^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0"
diff --git a/src/components/ReactToPrint.tsx b/src/components/ReactToPrint.tsx
index 9509ce6..107306b 100644
--- a/src/components/ReactToPrint.tsx
+++ b/src/components/ReactToPrint.tsx
@@ -77,7 +77,7 @@ export class ReactToPrint extends React.Component<IReactToPrintProps> {
                     this.handleRemoveIframe();
                 }
             } else {
-                this.logMessages(["Printing failed because the `contentWindow` of the print iframe did not load. This is possibly an error with `react-to-print`. Please file an issue: https://github.com/gregnb/react-to-print/issues/"]);
+                this.logMessages(["Printing failed because the `contentWindow` of the print iframe did not load. This is possibly an error with `react-to-print`. Please file an issue: https://github.com/MatthewHerbst/react-to-print/issues/"]);
             }
         }, 500);
     }
@@ -156,7 +156,7 @@ export class ReactToPrint extends React.Component<IReactToPrintProps> {
         }
 
         if (contentEl === undefined) {
-            this.logMessages(['To print a functional component ensure it is wrapped with `React.forwardRef`, and ensure the forwarded ref is used. See the README for an example: https://github.com/gregnb/react-to-print#examples']);
+            this.logMessages(['To print a functional component ensure it is wrapped with `React.forwardRef`, and ensure the forwarded ref is used. See the README for an example: https://github.com/MatthewHerbst/react-to-print#examples']);
             return;
         }
 
@@ -173,7 +173,7 @@ export class ReactToPrint extends React.Component<IReactToPrintProps> {
         printWindow.style.left = `-${document.documentElement.clientWidth + 100}px`;
         printWindow.id = "printWindow";
         // Ensure we set a DOCTYPE on the iframe's document
-        // https://github.com/gregnb/react-to-print/issues/459
+        // https://github.com/MatthewHerbst/react-to-print/issues/459
         printWindow.srcdoc = "<!DOCTYPE html>";
 
         const contentNodes = findDOMNode(contentEl);
@@ -381,7 +381,7 @@ export class ReactToPrint extends React.Component<IReactToPrintProps> {
                                 try {
                                     // Accessing `sheet.cssRules` on cross-origin sheets can throw
                                     // security exceptions in some browsers, notably Firefox
-                                    // https://github.com/gregnb/react-to-print/issues/429
+                                    // https://github.com/MatthewHerbst/react-to-print/issues/429
                                     const cssLength = sheet.cssRules.length;
                                     for (let j = 0; j < cssLength; ++j) {
                                         if (typeof sheet.cssRules[j].cssText === "string") {
@@ -389,7 +389,7 @@ export class ReactToPrint extends React.Component<IReactToPrintProps> {
                                         }
                                     }
                                 } catch (error) {
-                                    this.logMessages([`A stylesheet could not be accessed. This is likely due to the stylesheet having cross-origin imports, and many browsers block script access to cross-origin stylesheets. See https://github.com/gregnb/react-to-print/issues/429 for details. You may be able to load the sheet by both marking the stylesheet with the cross \`crossorigin\` attribute, and setting the \`Access-Control-Allow-Origin\` header on the server serving the stylesheet. Alternatively, host the stylesheet on your domain to avoid this issue entirely.`, node], 'warning');
+                                    this.logMessages([`A stylesheet could not be accessed. This is likely due to the stylesheet having cross-origin imports, and many browsers block script access to cross-origin stylesheets. See https://github.com/MatthewHerbst/react-to-print/issues/429 for details. You may be able to load the sheet by both marking the stylesheet with the cross \`crossorigin\` attribute, and setting the \`Access-Control-Allow-Origin\` header on the server serving the stylesheet. Alternatively, host the stylesheet on your domain to avoid this issue entirely.`, node], 'warning');
                                 }
 
                                 newHeadEl.setAttribute("id", `react-to-print-${i}`);