Fix: Correct module path and clarify config structure in Medusa v2 Docs

[aqeebpathan]

What

This PR addresses an issue in the Medusa v2 documentation regarding the module creation example. The import paths were corrected to reflect the proper directory structure, ensuring clarity for users.

Closes #9220

Why

The previous documentation contained incorrect import paths that could lead to confusion for users attempting to create and configure modules. Clarifying the structure aims to prevent similar issues for future users.

How

• Updated the import statements in the documentation to go two levels up instead of three.
• Added clarification in the medusa-config.js example to indicate that the modules node should be a part of projectConfig.

Testing

While documentation changes do not require formal testing, I reviewed the updated paths and descriptions against the current code structure to ensure accuracy and clarity.

Note

This is my first contribution to an open source project, and I'm excited to contribute to the Medusa community!

[changeset-bot]

⚠️ No Changeset found

Latest commit: 38ad846

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

[vercel]

@aqeebpathan is attempting to deploy a commit to the medusajs Team on Vercel.

A member of the Team first needs to authorize it.

[damien-thiesson]

LGTM

[olivermrbl]

Thanks for the contribution. Will let @shahednasser take a look at it!