Fix doc site

[philasmar]

Description

Merge dev into main

Motivation and Context

Testing

Breaking Changes Assessment

1. Identify all breaking changes including the following details:
   • What functionality was changed?
   • How will this impact customers?
   • Why does this need to be a breaking change and what are the most notable non-breaking alternatives?
   • Are best practices being followed?
   • How have you tested this breaking change?
2. Has a senior/+ engineer been assigned to review this PR?

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

License

• I confirm that this pull request can be released under the Apache 2 license