docs: fix broken link

[benmccann]

closes #283

[changeset-bot]

⚠️ No Changeset found

Latest commit: 122702e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Rich-Harris]

preview: https://svelte-dev-git-preview-cli-284-svelte.vercel.app/

this is an automated message

[Conduitry]

Suggested change

	`sv migrate` migrates Svelte(Kit) codebases. It delegates to the [`svelte-migrate`](npmjs.com/package/svelte-migrate) package.
	`sv migrate` migrates Svelte(Kit) codebases. It delegates to the [`svelte-migrate`](https://www.npmjs.com/package/svelte-migrate) package.

But also: Would it be more helpful to link to the location of the package in this repo, rather than to npm?

[benmccann]

Thanks for catching this!

But also: Would it be more helpful to link to the location of the package in this repo, rather than to npm?

I don't think so, which is why I changed it. Is there a reason you think that might be more helpful?

[manuel3108]

Is it even worth to mention that in the docs? It's more of an internal thing for me at least. Also does not look like we have a similar sentence for check in the docs.

[benmccann]

There are lots of articles, blog posts, tweets, etc. mentioning the two, so I think it's helpful for users to know what the difference is between them and how they relate

[benmccann]

Hmm. But I guess all the docs have been updated to refer to sv, so maybe the more important place to put this is the svelte-migrate readme