Merge pull request #3175 from EliotSeattle/legacy-printer

Legacy printer

Author: prmerger-automator[bot]

windows-driver-docs-pr/print/legacy-printer-driver-submission-process.md

@@ -37,7 +37,7 @@ Partners are required to provide a Driver Exception Justification Document descr
 
 ### Justification document format
 
-The justification document is a JSON file generated by using the new DriverExceptionDocGenerator tool.
+The justification document is a JSON file that can be created using [this schema.](#schema) The DriverExceptionDocGenerator tool will be available in the near future to automatically generate the schema.
 
 Partners may include extra supporting materials if needed, such as security disclosures, Mopria analysis, roadmaps, model comparisons. These supporting materials help the reviewers validate exception claims.
 
@@ -84,18 +84,18 @@ Existing driver updates are only signed and published if they:
 
 ## Generating the Justification Document
 
-### DriverExceptionDocGenerator Tool
+### DriverExceptionDocGenerator Tool (Coming Soon)
 
-Microsoft provides a dedicated tool to help partners prepare the justification JSON:
+The justification document must follow the [schema provided.](#schema) In the future, Microsoft will provide a dedicated tool to help partners prepare the justification JSON. This tool, named **DriverExceptionDocGenerator**, will be available as a command‑line utility and will guide partners through the process of generating a valid justification document.
 
-### Tool Capabilities
+#### Tool Capabilities
 
 - Run interactively (prompt‑driven)
 - Run non‑interactively by providing parameters
 - Produces a JSON document aligned to the Microsoft schema
 - Validates field formatting and required sections
 
-### When to use DriverExceptionDocGenerator
+#### When to use DriverExceptionDocGenerator
 
 Partners should use this tool for every printer driver submission, including:
 
@@ -106,7 +106,7 @@ Partners should use this tool for every printer driver submission, including:
 
 ## Information Required in the Justification JSON
 
-The justification JSON must follow the schema provided (omitted here for brevity but included in your partner enablement package). At a high level, partners must provide:
+The justification JSON must follow the [schema provided.](#schema). At a high level, partners must provide:
 
 ### Submission Metadata