fix repo link

Author: JonasBa

packages/profiling-node/CONTRIBUTING.md

@@ -6,27 +6,33 @@
 
 # Contributing
 
-We welcome suggested improvements and bug fixes to the `@sentry/*` family of packages, in the form of pull requests on [`GitHub`](https://github.com/getsentry/profiling-node). The guide below will help you get started, but if you have further questions, please feel free to reach out on [Discord](https://discord.gg/Ww9hbqr).
+We welcome suggested improvements and bug fixes to the `@sentry/*` family of packages, in the form of pull requests on
+[`GitHub`](https://github.com/getsentry/sentry-javascript). The guide below will help you get started, but if you have
+further questions, please feel free to reach out on [Discord](https://discord.gg/Ww9hbqr).
 
 ## Setting up an Environment
 
 To run the test suite and our code linter, node.js and npm are required.
 
 [`npm and node` download](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm)
 
-Because the repository requires you to compile the c++ bindings via node-gyp, we may require you to install dependencies like Python and GCC. See [node-gyp](https://github.com/nodejs/node-gyp#on-unix) for a full list of those requirements depending on the OS that you are running.
+Because the repository requires you to compile the c++ bindings via node-gyp, we may require you to install dependencies
+like Python and GCC. See [node-gyp](https://github.com/nodejs/node-gyp#on-unix) for a full list of those requirements
+depending on the OS that you are running.
 
 ## Building the package
 
-Since we are using [`TypeScript`](https://www.typescriptlang.org/) and native node addons, you need to transpile the code to JavaScript and compile the c++ bindings in order to be able to run the addon.
+Since we are using [`TypeScript`](https://www.typescriptlang.org/) and native node addons, you need to transpile the
+code to JavaScript and compile the c++ bindings in order to be able to run the addon.
 
 - `yarn build` will compile the c++ bindings and ts files.
 - `yarn build:lib` will compile ts files
 - `yarn build:bindings` will compile c++ bindings
 
 ## Tests
 
-Tests are colocated with source files and should have a .test.ts suffix. The entire test suite can be ran using the `yarn test` command.
+Tests are colocated with source files and should have a .test.ts suffix. The entire test suite can be ran using the
+`yarn test` command.
 
 ## Linting
 
@@ -37,12 +43,17 @@ Similar to building and testing, linting can be done via `yarn lint` command.
 When contributing to the codebase, please note:
 
 - Non-trivial PRs will not be accepted without tests (see above).
-- We encourage you to open issues and discuss the change you want to make before opening PR's. This is especially true if you are considering adding new functionality. Remember that your requirements may differ from the direction that we want this SDK to take.
+- We encourage you to open issues and discuss the change you want to make before opening PR's. This is especially true
+  if you are considering adding new functionality. Remember that your requirements may differ from the direction that we
+  want this SDK to take.
 - Please do not bump version numbers yourself.
 
 ## Benchmarks
 
-The repository contains micro benchmarks. You can find all benchmarks at the benchmarks folder in project root directory. The benchmarks can either be ran directly through node via `node benchmarks/cpu/benchmark.profiler.js` or via `yarn benchmark` command. There are also individual yarn benchmark commands like `yarn benchmark:server` or `yarn benchmark:methods` which will only run individual benchmarks.
+The repository contains micro benchmarks. You can find all benchmarks at the benchmarks folder in project root
+directory. The benchmarks can either be ran directly through node via `node benchmarks/cpu/benchmark.profiler.js` or via
+`yarn benchmark` command. There are also individual yarn benchmark commands like `yarn benchmark:server` or
+`yarn benchmark:methods` which will only run individual benchmarks.
 
 Remember that these are micro benchmarks and that results will vary across different OS and architectures.
 
@@ -51,7 +62,9 @@ Remember that these are micro benchmarks and that results will vary across diffe
 _These steps are only relevant to Sentry employees when preparing and publishing a new SDK release._
 
 1. Determine what version will be released (we use [semver](https://semver.org)).
-2. Update [`CHANGELOG.md`](https://github.com/getsentry/profiling-node/edit/master/CHANGELOG.md) to add an entry for the next release number and a list of changes since the last release. (See details below.)
-3. Run the [Prepare Release](https://github.com/getsentry/profiling-node/actions/workflows/release.yml) workflow.
+2. Update [`CHANGELOG.md`](https://github.com/getsentry/sentry-javascript/edit/master/CHANGELOG.md) to add an entry for
+   the next release number and a list of changes since the last release. (See details below.)
+3. Run the [Prepare Release](https://github.com/getsentry/sentry-javascript/actions/workflows/release.yml) workflow.
 4. A new issue should appear in https://github.com/getsentry/publish/issues.
-5. Ask a member of the [@getsentry/releases team](https://github.com/orgs/getsentry/teams/releases/members) to approve the release.
+5. Ask a member of the [@getsentry/releases team](https://github.com/orgs/getsentry/teams/releases/members) to approve
+   the release.