Remove dead links

Author: adrianlizarraga

docs/execution-providers/community-maintained/CANN-ExecutionProvider.md

@@ -389,4 +389,3 @@ Following ops are supported by the CANN Execution Provider in single-operator In
 Additional operator support and performance tuning will be added soon.
 
 * [Ascend](https://www.hiascend.com/en/)
-* [CANN](https://www.hiascend.com/en/software/cann)

docs/execution-providers/plugin-ep-libraries.md

@@ -38,25 +38,25 @@ The following table lists the **required** varibles and functions that an implem
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-ort-version-supported">ort_version_supported</a></td>
+<td>ort_version_supported</td>
 <td>The ONNX Runtime version with which the EP was compiled. Implementation should set to <code>ORT_API_VERSION</code>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/16ae99ede405d3d6c59d7cce80c53f5f7055aeed/onnxruntime/test/autoep/library/ep.cc#L160">ExampleEp()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-get-name">GetName</a></td>
+<td>GetName</td>
 <td>Get the execution provider name.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/16ae99ede405d3d6c59d7cce80c53f5f7055aeed/onnxruntime/test/autoep/library/ep.cc#L181">ExampleEp::GetNameImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-get-capability">GetCapability</a></td>
+<td>GetCapability</td>
 <td>Get information about the nodes/subgraphs supported by the <code>OrtEp</code> instance.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/16ae99ede405d3d6c59d7cce80c53f5f7055aeed/onnxruntime/test/autoep/library/ep.cc#L231">ExampleEp::GetCapabilityImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-compile">Compile</a></td>
+<td>Compile</td>
 <td>
 Compile <code>OrtGraph</code> instances assigned to the <code>OrtEp</code>. Implementation must set a <code>OrtNodeComputeInfo</code> instance for each <code>OrtGraph</code> in order to define its computation function.<br/><br/>
 If the session is configured to generate a pre-compiled model, the execution provider must return <code>count</code> number of EPContext nodes.
@@ -65,7 +65,7 @@ If the session is configured to generate a pre-compiled model, the execution pro
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-release-node-compute-infos">ReleaseNodeComputeInfos</a></td>
+<td>ReleaseNodeComputeInfos</td>
 <td>
 Release <code>OrtNodeComputeInfo</code> instances.
 </td>
@@ -84,7 +84,7 @@ The following table lists the **optional** functions that an implementor may def
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-get-preferred-data-layout">GetPreferredDataLayout</a></td>
+<td>GetPreferredDataLayout</td>
 <td>
 Get the EP's preferred data layout.<br/><br/>
 If this function is not implemented, ORT assumes that the EP prefers the data layout <code>OrtEpDataLayout::NCHW</code>.
@@ -93,7 +93,7 @@ If this function is not implemented, ORT assumes that the EP prefers the data la
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-should-convert-data-layout-for-op">ShouldConvertDataLayoutForOp</a></td>
+<td>ShouldConvertDataLayoutForOp</td>
 <td>
 Given an op with domain <code>domain</code> and type <code>op_type</code>, determine whether an associated node's data layout should be converted to a <code>target_data_layout</code>. If the EP prefers a non-default data layout, this function will be called during layout transformation with <code>target_data_layout</code> set to the EP's preferred data layout<br/><br/>
 Implementation of this function is optional. If an EP prefers a non-default data layout, it may implement this to customize the specific op data layout preferences at a finer granularity.
@@ -102,7 +102,7 @@ Implementation of this function is optional. If an EP prefers a non-default data
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-set-dynamic-options">SetDynamicOptions</a></td>
+<td>SetDynamicOptions</td>
 <td>
 Set dynamic options on this EP. Dynamic options can be set by the application at any time after session creation with <a href="https://onnxruntime.ai/docs/api/c/struct_ort_api.html#ab1117a51683e4fbb42687c9db6e8d5fb"><code>OrtApi::SetEpDynamicOptions()</code></a>.<br/><br/>
 Implementation of this function is optional. An EP should only impliment this function if it needs to handle any dynamic options.
@@ -111,7 +111,7 @@ Implementation of this function is optional. An EP should only impliment this fu
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-on-run-start">OnRunStart</a></td>
+<td>OnRunStart</td>
 <td>
 Called by ORT to notify the EP of the start of a run.<br/><br/>
 Implementation of this function is optional. An EP should only impliment this function if it needs to handle application-provided options at the start of a run.
@@ -120,7 +120,7 @@ Implementation of this function is optional. An EP should only impliment this fu
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-on-run-end">OnRunEnd</a></td>
+<td>OnRunEnd</td>
 <td>
 Called by ORT to notify the EP of the end of a run.<br/><br/>
 Implementation of this function is optional. An EP should only impliment this function if it needs to handle application-provided options at the end of a run.
@@ -129,7 +129,7 @@ Implementation of this function is optional. An EP should only impliment this fu
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-create-allocator">CreateAllocator</a></td>
+<td>CreateAllocator</td>
 <td>
 Create an <code>OrtAllocator</code> for the given <code>OrtMemoryInfo</code> for an <code>OrtSession</code>.<br/><br/>The <code>OrtMemoryInfo</code> instance will match one of the values set in the <code>OrtEpDevice</code> using <code>EpDevice_AddAllocatorInfo</code>. Any allocator specific options should be read from the session options.<br/><br/>
 Implementation of this function is optional. If not provided, ORT will use `OrtEpFactory::CreateAllocator()`.
@@ -138,7 +138,7 @@ Implementation of this function is optional. If not provided, ORT will use `OrtE
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-create-sync-stream-for-device">CreateSyncStreamForDevice</a></td>
+<td>CreateSyncStreamForDevice</td>
 <td>
 Create a synchronization stream for the given memory device for an <code>OrtSession</code>.<br/><br/>This is used to create a synchronization stream for the execution provider and is used to synchronize operations on the device during model execution. Any stream specific options should be read from the session options.<br/><br/>
 Implementation of this function is optional. If not provided, ORT will use `OrtEpFactory::CreateSyncStreamForDevice()`.
@@ -147,7 +147,7 @@ Implementation of this function is optional. If not provided, ORT will use `OrtE
 </tr>
 
 <tr>
-<td><a href="c-api-ort-ep-get-compiled-model-compatability-info">GetCompiledModelCompatibilityInfo</a></td>
+<td>GetCompiledModelCompatibilityInfo</td>
 <td>
 Get a string with details about the EP stack used to produce a compiled model.<br/><br/>
 The compatibility information string can be used with <code>OrtEpFactory::ValidateCompiledModelCompatibilityInfo</code> to determine if a compiled model is compatible with the EP.
@@ -170,43 +170,43 @@ The following table lists the **required** variables and functions that an imple
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-ort-version-supported">ort_version_supported</a></td>
+<td>ort_version_supported</td>
 <td>The ONNX Runtime version with which the EP was compiled. Implementation should set this to <code>ORT_API_VERSION</code>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L16">ExampleEpFactory()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-get-name">GetName</a></td>
+<td>GetName</td>
 <td>Get the name of the EP that the factory creates. Must match <code>OrtEp::GetName()</code>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L77">ExampleEpFactory::GetNameImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-get-vendor">GetVendor</a></td>
+<td>GetVendor</td>
 <td>Get the name of the name of the vendor that owns the EP that the factory creates.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L83">ExampleEpFactory::GetVendor()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-get-vendor-id">GetVendorId</a></td>
+<td>GetVendorId</td>
 <td>Get the vendor ID of the vendor that owns the EP that the factory creates. This is typically the <a href="https://pcisig.com/membership/member-companies">PCI vendor ID</a>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L89">ExampleEpFactory::GetVendorId()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-get-version">GetVersion</a></td>
+<td>GetVersion</td>
 <td>Get the version of the EP that the factory creates. The version string should adhere to the <a href="https://github.com/semver/semver/blob/v2.0.0/semver.md">Semantic Versioning 2.0 specification</a>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L95">ExampleEpFactory::GetVersionImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-get-supported-devices">GetSupportedDevices</a></td>
+<td>GetSupportedDevices</td>
 <td>Get information about the <code>OrtHardwareDevice</code> instances supported by an EP created by the factory.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L101">ExampleEpFactory::GetSupportedDevicesImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-create-ep">CreateEp</a></td>
+<td>CreateEp</td>
 <td>Creates an <code>OrtEp</code> instance for use in an ONNX Runtime session. ORT calls <code>OrtEpFactory::ReleaseEp()</code> to release the instance.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L163">ExampleEpFactory::CreateEpImpl()</a></td>
 </tr>
@@ -223,41 +223,41 @@ The following table lists the **optional** functions that an implementer may def
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-validate-compiled-model-compatibility-info">ValidateCompiledModelCompatibilityInfo</a></td>
+<td>ValidateCompiledModelCompatibilityInfo</td>
 <td>Validate the compatibility of a compiled model with the EP.<br/><br/>
 This function validates if a model produced with the supllied compatibility information string is supported by the underlying EP.
 The implementation should check if a compiled model is compatible with the EP and return the appropriate <code>OrtCompiledModelCompatibility</code> value.</td>
 <td></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-create-allocator">CreateAllocator</a></td>
+<td>CreateAllocator</td>
 <td>Create an <code>OrtAllocator</code> that can be shared across sessions for the given <code>OrtMemoryInfo</code>.<br/><br/>
 The factory that creates the EP is responsible for providing the allocators required by the EP. The <code>OrtMemoryInfo</code> instance will match one of the values set in the <code>OrtEpDevice</code> using <code>EpDevice_AddAllocatorInfo</code>.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L212">ExampleEpFactory::CreateAllocatorImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-release-allocator">ReleaseAllocator</a></td>
+<td>ReleaseAllocator</td>
 <td>Releases an <code>OrtAllocator</code> instance created by the factory.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L272">ExampleEpFactory::ReleaseAllocatorImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-create-data-transfer">CreateDataTransfer</a></td>
+<td>CreateDataTransfer</td>
 <td>Creates an <code>OrtDataTransferImpl</code> instance for the factory.<br/><br/>
 An <code>OrtDataTransferImpl</code> can be used to copy data between devices that the EP supports.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L286">ExampleEpFactory::CreateDataTransferImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-is-stream-aware">IsStreamAware</a></td>
+<td>IsStreamAware</td>
 <td>Returns true if the EPs created by the factory are stream-aware.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L295">ExampleEpFactory::IsStreamAwareImpl()</a></td>
 </tr>
 
 <tr>
-<td><a href="#c-api-ort-ep-factory-create-sync-stream-for-device">CreateSyncStreamForDevice</a></td>
+<td>CreateSyncStreamForDevice</td>
 <td>Creates a synchronization stream for the given <code>OrtMemoryDevice</code>.<br/><br/>
 This is use to create a synchronization stream for the <code>OrtMemoryDevice</code> that can be used for operations outside of a session.</td>
 <td><a href="https://github.com/microsoft/onnxruntime/blob/3cadbdb495761a6a54845b178f9bdb811a2c8bde/onnxruntime/test/autoep/library/ep_factory.cc#L300">ExampleEpFactory::CreateSyncStreamForDeviceImpl()</a></td>
@@ -457,7 +457,7 @@ API header files:
 
 <tr>
 <td>
-<a href="#ort-hardware-device-type">OrtHardwareDeviceType</a>
+OrtHardwareDeviceType
 </td>
 <td>
 Enumerates classes of hardware devices:<br>
@@ -552,7 +552,7 @@ Opaque type that represents a combination of a physical device and memory type.
 
 <tr>
 <td>
-<a href="#ort-data-transfer-impl">OrtDataTransferImpl</a>
+OrtDataTransferImpl
 </td>
 <td>
 Struct of functions that an EP implements to copy data between the devices that the EP uses and CPU.
@@ -561,7 +561,7 @@ Struct of functions that an EP implements to copy data between the devices that
 
 <tr>
 <td>
-<a href="#ort-sync-notification-impl">OrtSyncNotificationImpl</a>
+OrtSyncNotificationImpl
 </td>
 <td>
 Struct of functions that an EP implements for Stream notifications.
@@ -570,7 +570,7 @@ Struct of functions that an EP implements for Stream notifications.
 
 <tr>
 <td>
-<a href="#ort-sync-stream-impl">OrtSyncStreamImpl</a>
+OrtSyncStreamImpl
 </td>
 <td>
 Struct of functions that an EP implements if it needs to support Streams.
@@ -579,7 +579,7 @@ Struct of functions that an EP implements if it needs to support Streams.
 
 <tr>
 <td>
-<a href="#ort-ep-factory">OrtEpFactory</a>
+OrtEpFactory
 </td>
 <td>
 A plugin EP library provides ORT with one or more instances of <code>OrtEpFactory</code>. An <code>OrtEpFactory</code> implements functions that are used by ORT to query device support, create allocators, create data transfer objects, and create instances of an EP (i.e., an <code>OrtEp</code> instance).<br/>
@@ -592,7 +592,7 @@ Alternatively, if an EP library author needs ONNX Runtime to partition the graph
 
 <tr>
 <td>
-<a href="#ort-ep">OrtEp</a>
+OrtEp
 </td>
 <td>
 An instance of an Ep that can execute model nodes on one or more hardware devices (<code>OrtHardwareDevice</code>). An <code>OrtEp</code> implements functions that are used by ORT to query graph node support, compile supported nodes, query preferred data layout, set run options, etc. An <code>OrtEpFactory</code> creates an <code>OrtEp</code> instance via the <code>OrtEpFactory::CreateEp()</code> function.
@@ -670,7 +670,7 @@ Opaque type that represents a node in a graph.
 
 <tr>
 <td>
-<a href="#ort-op-attr-type">OrtOpAttrType</a>
+OrtOpAttrType
 </td>
 <td>
 Enumerates attribute types.

docs/genai/tutorials/finetune.md

@@ -161,5 +161,5 @@ python app.py -m <model folder> -a <.onnx_adapter files> -t <prompt template> -s
 
 ## References
 
-* [Python API docs](../api/python.md#adapter-class)
+* [Python API docs](../api/python.md)
 * [Olive CLI docs](https://microsoft.github.io/Olive/how-to/index.html#working-with-the-cli)