docs: update rendering comparison and license wording#1041
Open
kiyeonjeon21 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This updates a few documentation references after the recent AWS Lambda rendering work:
Why
Recent releases added the AWS Lambda rendering flow, including
lambda deploy,lambda render,lambda render-batch, progress/cost polling, and SDK usage. Some comparison docs still reflected the earlier single-machine-only state, which could confuse adopters evaluating HyperFrames for production rendering.The contributing docs also had license wording that did not match the repository license.
Notes
Docs-only change. No runtime or API behavior changes.
Validation
bunx oxfmt --check README.md docs/guides/hyperframes-vs-remotion.mdx docs/contributing.mdxgit diff --check