Improve EmbeddedResource documentation with step-by-step guide (#1631)

- Expand JsonProvider.fsx EmbeddedResource section with step-by-step
  setup instructions, fsproj snippet, naming convention explanation,
  and common pitfall warning
- Expand CsvProvider.fsx to include a brief EmbeddedResource section
  pointing readers to the full guide in JsonProvider.fsx

Addresses #1315.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: github-actions[bot]

docs/library/CsvProvider.fsx

@@ -475,9 +475,21 @@ transformed the dataset to be smaller.
 *)
 
 (**
+## Using CSV provider in a library
+
+When using `CsvProvider` in a library that others will reference, the sample file must be
+embedded in the compiled assembly. See the step-by-step guide in
+[Using JSON provider in a library](JsonProvider.html#jsonlib) — the same `EmbeddedResource`
+parameter and naming convention applies to `CsvProvider`.
+
+In brief, for a file `data/sample.csv` in a library `MyLib`:
+1. Mark the file as `<EmbeddedResource>` in the `.fsproj`
+2. Use `EmbeddedResource="MyLib, MyLib.data.sample.csv"` in the type provider declaration
+
 ## Related articles
 
- * [Using JSON provider in a library](JsonProvider.html#jsonlib) also applies to CSV type provider
+ * [Using JSON provider in a library](JsonProvider.html#jsonlib) — includes step-by-step
+   `EmbeddedResource` guide that applies to all type providers
  * [CSV Parser](CsvFile.html) - provides more information about
    working with CSV documents dynamically.
  * [API Reference: CsvProvider type provider](../reference/fsharp-data-csvprovider.html)

docs/library/JsonProvider.fsx

@@ -462,8 +462,26 @@ access the sample JSON. This works fine when the sample is specified inline, but
 the sample is specified as a local file (unless you distribute the samples with your library).
 
 For this reason, the JSON provider lets you specify samples as embedded resources using the
-static parameter `EmbeddedResource` (don't forget then to [include the file](https://docs.microsoft.com/en-us/visualstudio/ide/build-actions) as EmbeddedResource in the
-project file). If you are building a library `MyLib.dll`, you can write:
+static parameter `EmbeddedResource`. When this parameter is set, the type provider at design time
+reads the sample from the local path, but at runtime (when the library is loaded by a consumer)
+it reads the sample from the embedded resource in the compiled assembly.
+
+### Step-by-step guide
+
+**Step 1**: Mark your sample file as an embedded resource in the `.fsproj` file:
+
+```xml
+<ItemGroup>
+  <EmbeddedResource Include="data/worldbank.json" />
+</ItemGroup>
+```
+
+**Step 2**: Use the `EmbeddedResource` static parameter. The value must be
+`"AssemblyName, AssemblyName.dotted.path.to.file.json"` where:
+- `AssemblyName` is the name of your library assembly (without `.dll`)
+- The file path uses **dots** (not slashes) as separators, prefixed with `AssemblyName`
+
+So for a file `data/worldbank.json` in a library `MyLib`, the value is:
 
 *)
 type WB =
@@ -480,6 +498,14 @@ to load `MyLib.dll` and locate the sample `worldbank.json` as a resource of the
 this succeeds, it does not attempt to find the local file and so your library can be used
 without providing a local copy of the sample JSON files.
 
+> **Common pitfall**: If you get a cryptic error where the type provider interprets the file path
+> as the CSV/JSON content itself (resulting in a single-column type named after the path), you
+> have likely forgotten to add the `EmbeddedResource` parameter, or the assembly name or resource
+> path in the parameter value is incorrect.
+>
+> To verify the embedded resource name, you can inspect the compiled `.dll` using a tool such as
+> `ildasm`, `dotnet-ildasm`, or ILSpy and look at the `.mresource` entries.
+
 ## Related articles
 
  * [JSON Parser](JsonValue.html) - provides more information about