docs: address PR #318 review comments (#325)

## Summary
- Add NuGet explanation (external libraries) for non-.NET developers
- Clarify publish output location and benefits of single-file deployment
- Remove misleading info metadata example that implied required fields

Addresses review comments 2, 3, 4, and 5 from PR #318.

Author: abdullah-cognite

docfx_project/docs/building-and-running.md

@@ -17,7 +17,7 @@ Your connector is a console application with a simple entry point in [Program.cs
 
 ### What Gets Built
 
-When you run `dotnet build`, the compiler compiles all `.cs` files, resolves NuGet dependencies, and produces an executable with a `.dll` (your code) and `.exe` (launcher) in `bin/Debug/<target-framework>/` or `bin/Release/<target-framework>/`.
+When you run `dotnet build`, the compiler compiles all `.cs` files, resolves NuGet dependencies (external libraries), and produces an executable with a `.dll` (your code) and `.exe` (launcher) in `bin/Debug/<target-framework>/` or `bin/Release/<target-framework>/`.
 
 ## Building & Running Your Connector
 
@@ -55,7 +55,7 @@ dotnet publish -r win-x64 -c Release \
   /p:EnableCompressionInSingleFile=true
 ```
 
-This produces a single file binary with everything needed to run in the `bin/Release/<target-framework>/win-x64/publish/`
+This produces a single file binary with everything needed to run in the `bin/Release/<target-framework>/win-x64/publish/`. This makes it easier to share your connector with others, as a single file packages everything needed to run the connector on another environment.
 
 ## Running as a Windows Service
 

docfx_project/docs/create-connector.md

@@ -260,8 +260,6 @@ public class NewSimClient : AutomationClient, ISimulatorClient<DefaultModelFiles
             Initialize();
             workbook = OpenBook(modelState.FilePath);
 
-            // var routine = new NewSimRoutine(workbook, routineRev, inputData, logger);
-            // return routine.PerformSimulation(token);
             return null;
         }
         finally

docfx_project/docs/implement-routine.md

@@ -480,4 +480,4 @@ public override void SetInput(
 
 ---
 
-**Next:** Continue to [Testing](testing.md) to learn how to test your connector.
+**Next:** Continue to [Testing](testing-and-extras.md) to learn how to test your connector.

docfx_project/docs/model-parsing.md

@@ -108,19 +108,6 @@ The DWSIM implementation shows how to:
 
 You can also optionally extract arbitrary metadata about the model using the `info` field. This is a key-value structure that can hold any JSON-serializable data.
 
-### Info Structure
-
-```csharp
-var info = new Dictionary<string, string>
-{
-    ["ModelVersion"] = "2.1",
-    ["CreatedDate"] = "2024-01-15",
-    ["Author"] = "John Doe",
-    ["Description"] = "Distillation column model",
-    ["CustomField"] = "Custom value"
-};
-```
-
 ### When to Use Info
 
 Use `info` for: