docs: add note about packaging patterns

docs/repo-docs/crafting-your-repository/creating-an-internal-package.mdx

@@ -12,7 +12,7 @@ import { Files, File, Folder } from '#/components/files';
 
 ![Visual representation of a Package Graph in a Turborepo.](/images/docs/package-graph.png)
 
-Let's create your first Internal Package to share math utilities in your repo using the guidance in the [Anatomy of a package](/repo/docs/crafting-your-repository/structuring-a-repository#anatomy-of-a-package) section. In the steps below, we assume you've [created a new repository using `create-turbo`](/repo/docs/getting-started/installation) or are using a similarly structured repository.
+Let's create your first Internal Package to share math utilities in your repo using the guidance in the [Anatomy of a package](/repo/docs/crafting-your-repository/structuring-a-repository#anatomy-of-a-package) section and the [Compiled Packages](/repo/docs/core-concepts/internal-packages#compiled-packages) pattern. In the steps below, we assume you've [created a new repository using `create-turbo`](/repo/docs/getting-started/installation) or are using a similarly structured repository.
 
 <Steps>
 <Step>

docs/repo-docs/crafting-your-repository/structuring-a-repository.mdx

@@ -280,13 +280,15 @@ For example, if you had a `@repo/math` package, you might have the following `ex
 ```json title="./packages/math/package.json"
 {
   "exports": {
-    ".": "./dist/constants.ts",
-    "./add": "./dist/add.ts",
-    "./subtract": "./dist/subtract.ts"
+    ".": "./src/constants.ts",
+    "./add": "./src/add.ts",
+    "./subtract": "./src/subtract.ts"
   }
 }
 ```
 
+Note that this example uses the [Just-in-Time Package](/repo/docs/core-concepts/internal-packages#just-in-time-packages) pattern for simplicity. It exports TypeScript directly, but you might choose to use the [Compiled Package](/repo/docs/core-concepts/internal-packages#compiled-packages) pattern instead.
+
 <Callout type="info">
   The `exports` field in this example requires modern versions of Node.js and
   TypeScript.
@@ -307,9 +309,9 @@ Using exports this way provides three major benefits:
 - **IDE autocompletion**: By specifying the entrypoints for your package using `exports`, you can ensure that your code editor can provide auto-completion for the package's exports.
 
 <Callout type="good-to-know">
-  You may also specify `exports` using a wildcard. However, you will lose IDE
-  autocompletion due to performance tradeoffs with the TypeScript compiler. For
-  more information, visit [the TypeScript
+  You may also specify `exports` using a wildcard. However, you will lose some 
+  IDE autocompletion due to performance tradeoffs with the TypeScript compiler.
+  For more information, visit [the TypeScript
   guide](/repo/docs/guides/tools/typescript#package-entrypoint-wildcards).
 </Callout>