docs: improve observability intro#934
Open
firecrawl-spring[bot] wants to merge 1 commit into
Open
Conversation
Co-Authored-By: micahstairs <micah@sideguide.dev>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Page: https://docs.firecrawl.dev/use-cases/observability
Summary
Rewrites the intro on
use-cases/observability.mdxto lead with what the reader can accomplish instead of who uses the product. The new opener names the concrete signals you can monitor (downtime, content changes, performance regressions) and explains why JavaScript rendering matters for monitoring, mirroring the prose style used on stronger Firecrawl docs pages.No content was added or removed elsewhere on the page.