chore: fix links

Author: ilbertt

.github/CONTRIBUTING.md

@@ -15,7 +15,7 @@ The contributor guidelines are intended to make the contribution process easy an
 
 Before contributing, consider the following:
 
-- If you want to report an issue, click [issues](https://github.com/dfinity/cbor-js/issues).
+- If you want to report an issue, click [issues](https://github.com/dfinity/typedoc-plugin-icp-docs/issues).
 - If you have more general questions related to this package and its use, post a message to the [community forum](https://forum.dfinity.org/).
 - If you are reporting a bug, provide as much information about the problem as possible.
 - If you want to contribute directly to this repository, typical fixes might include any of the following:
@@ -40,7 +40,7 @@ This section describes the most common workflow scenarios:
 
 To open a new issue:
 
-1. Click [create a new issue](https://github.com/dfinity/cbor-js/issues/new).
+1. Click [create a new issue](https://github.com/dfinity/typedoc-plugin-icp-docs/issues/new).
 2. Type a title and description, then click **Submit new issue**.
    - Be as clear and descriptive as possible.
    - For any problem, describe it in detail, including details about the crate, the version of the code you are using, the results you expected, and how the actual results differed from your expectations.
@@ -50,7 +50,7 @@ To open a new issue:
 If you want to submit a pull request to fix an issue or add a feature, here's a summary of what you need to do:
 
 1. Make sure you have a GitHub account, an internet connection, and access to a terminal shell or GitHub Desktop application for running commands.
-2. Navigate to the [repository's homepage](https://github.com/dfinity/cbor-js) in a web browser.
+2. Navigate to the [repository's homepage](https://github.com/dfinity/typedoc-plugin-icp-docs) in a web browser.
 3. Click **Fork** to create a copy of the repository under your GitHub account or organization name.
 4. Clone the forked repository to your local machine.
 5. Create a new branch for your fix by running a command similar to the following:

README.md

@@ -41,7 +41,7 @@ See [HACKING.md](./HACKING.md) for more information.
 
 ## Contributing
 
-Contributions are welcome! Please see [CONTRIBUTING.md](./CONTRIBUTING.md) for more information.
+Contributions are welcome! Please see [CONTRIBUTING.md](./.github/CONTRIBUTING.md) for more information.
 
 ## License