edits

Author: diberry

articles/typespec/includes/quickstart/file-structure-typescript.md

@@ -3,7 +3,7 @@ ms.custom: devx-track-ts, devx-track-typespec
 ms.topic: include
 ms.date: 04/23/2025
 ---
-The project structure for the generated server includes the Express.js server, the package.json, and the middleware for your Azure integration. 
+The Express.js project structure found at `tsp-output/server/` includes the generated server, the package.json, and the middleware for your Azure integration. 
 
 ```console
 ├── docs
@@ -13,4 +13,15 @@ The project structure for the generated server includes the Express.js server, t
 ├── README.md
 ├── package.json
 ├── openapi3.json
+```
+
+The file structure for the parent TypeSpec project includes this Express.js project in `tsp-output`:
+
+```console
+├── tsp-output
+├── .gitignore
+├── main.tsp
+├── package-lock.json
+├── package.json
+├── tspconfig.yaml
 ```

articles/typespec/quickstart-scaffold-dotnet.md

@@ -1012,6 +1012,27 @@ Create the files needed to have a repeatable deployment with [Azure Developer CL
     ...bicep..
     ```
 
+## Project structure
+
+The final project structure includes the TypeSpec API files, the Express.js server, and the Azure deployment files: 
+
+```console
+├── infra
+├── tsp-output
+├── .gitignore
+├── .azure.yaml
+├── Dockerfile
+├── main.tsp
+├── package-lock.json
+├── package.json
+├── tspconfig.yaml
+```
+
+| Area                     | Files/Directories                                                                 |
+|--------------------------|-----------------------------------------------------------------------------------|
+| **TypeSpec**             | `main.tsp`, `tspconfig.yaml`                                        |
+| **Express.js server**    | `./tsp-output/server/` (includes generated files like `controllers/`, `models/`, `ServiceProject.csproj`) |
+| **Azure Developer CLI deployment** | `./azure.yaml`,`./infra/`                             |
 
 ## Deploy application to Azure
 

articles/typespec/quickstart-scaffold-typescript.md

@@ -1,6 +1,6 @@
 ---
 title: "Quickstart: Create a new TypeScript API project with TypeSpec"
-description: Learn how to generate and set up a new RESTful TypeScrip API project using TypeSpec to scaffold consistent client and server code for cloud services.
+description: Learn how to generate and set up a new RESTful TypeScript API project using TypeSpec to scaffold consistent client and server code for cloud services.
 ms.topic: quickstart
 ms.date: 04/30/2025
 ms.custom: devx-track-typespec, devx-track-js, devx-track-ts
@@ -110,7 +110,7 @@ TypeSpec defines your API in a language-agnostic way and generates the API serve
 1. TypeSpec generates the default project in `./tsp-output`, creating two separate folders:
 
     * **schema** is the OpenApi 3 specification. Notice that the few lines in `./main.tsp` generated over 200 lines of OpenApi specification for you.
-    * **server** is the generated middleware. This can be incorporated into a Node.js server project.
+    * **server** is the generated middleware. This middleware can be incorporated into a Node.js server project.
         * `./tsp-output/js/src/generated/models/all/demo-service.ts` defines the interfaces for the Widgets API.
         * `./tsp-output/js/src/generated/http/openapi3.ts` defines the Open API spec as a TypeScript file and is regenerated every time you compile your TypeSpec project.
     
@@ -147,7 +147,7 @@ Use the TypeSpec files to configure the API server generation to scaffold the en
     npx hsjs-scaffold
     ```
 
-1. Change into the new `/./tsp-output/server` directory:
+1. Change into the new `./tsp-output/server` directory:
 
     ```console
     cd ./tsp-output/server
@@ -179,7 +179,7 @@ Use the TypeSpec files to configure the API server generation to scaffold the en
 
 ## Change persistence to Azure Cosmos DB no-sql
 
-Now that the basic Express.js API server is working, update the Express.js server to work with [Azure Cosmos DB](/azure/cosmos-db/) for a persistent data store. This includes changes to the `index.ts` to use Cosmos DB integration in the middleware. All changes should happen outside the `./src/generated` directory.
+Now that the basic Express.js API server is working, update the Express.js server to work with [Azure Cosmos DB](/azure/cosmos-db/) for a persistent data store. This includes changes to the `index.ts` to use Cosmos DB integration in the middleware. All changes should happen outside the `./tsp-output/server/src/generated` directory.
 
 1. In the `./tsp-output/server` directory, add [Azure Cosmos DB](/azure/cosmos-db/) to the project:
 
@@ -287,9 +287,9 @@ Now that the basic Express.js API server is working, update the Express.js serve
     };
     ```
 
-    Notice the file uses the endpoint, database, and container. It doesn't need a connection string or key because it is using the Azure Identity credential `DefaultAzureCredential`. Learn more about this method of [secure authentication for both local and production](/azure/developer/javascript/sdk/authentication/overview) environments.
+    Notice the file uses the endpoint, database, and container. It doesn't need a connection string or key because it's using the Azure Identity credential `DefaultAzureCredential`. Learn more about this method of [secure authentication for both local and production](/azure/developer/javascript/sdk/authentication/overview) environments.
 
-1. Create a new Widget controller, `./src/controllers/widgets-cosmos.ts`, with the following code to integrate Azure Cosmos DB.
+1. Create a new Widget controller, `./tsp-output/server/src/controllers/widgets-cosmos.ts`, and paste in the following integration code for Azure Cosmos DB.
 
     ```typescript
     import { Widgets, Widget, WidgetList,   AnalyzeResult,Error } from "../generated/models/all/demo-service.js";
@@ -504,7 +504,7 @@ Now that the basic Express.js API server is working, update the Express.js serve
     }
     ```
 
-1. Update the `./src/index.ts` to use the new controller. 
+1. Update the `./tsp-output/server/src/index.ts` to use the new controller. 
 
     ```typescript
     // Generated by Microsoft TypeSpec
@@ -930,7 +930,7 @@ Once deployed, you can:
 Now that you have the entire end to end process working, continue to build your API: 
 
 * Learn more about the [TypeSpec language](https://typespec.io/docs/language-basics/overview/) to add more APIs and API layer features in the `./main.tsp`.
-* Add additional [emitters](https://typespec.io/docs/extending-typespec/emitters-basics/) and configure their parameters in the `./tspconfig.yaml`.
+* Add more [emitters](https://typespec.io/docs/extending-typespec/emitters-basics/) and configure their parameters in the `./tspconfig.yaml`.
 * As you add more features in your TypeSpec files, support those changes with source code in the server project. 
 * Continue to use [passwordless authentication](/azure/developer/javascript/sdk/authentication/overview) with Azure Identity.