Remove AI-generated content warnings and update internal links#77
Remove AI-generated content warnings and update internal links#77
Conversation
…and accurate links Refine `faq.mdx` and `glossary.mdx` to keep legacy structure/content while removing migration artifacts and fixing outdated references. - removed AI-generated warning banners from both pages - preserved legacy FAQ/Glossary layout and core definitions - updated FAQ answers that were no longer accurate (notably crypto-to-fiat support) - replaced generic or confusing references with feature-specific links where appropriate - cleaned old `docs.request.network` dependencies and moved to current internal/docs links where possible - fixed inconsistent link behavior in FAQ responses to improve readability and navigation
aimensahnoun
changed the title
faq.mdx and glossary.mdx to keep legacy structure/content while removing migration artifacts and fixing outdated references. - removed AI-generated warning 
Greptile SummaryThis PR removes AI-generated content warnings from Key changes:
Issues requiring attention:
Confidence Score: 2/5
Last reviewed commit: 0ef3c12 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| <Accordion title="Does Request Network support crypto-to-fiat (off-ramp) or fiat-to-crypto (on-ramp) payments?"> | ||
| Not currently, but we're working on it. | ||
| Crypto-to-fiat payments are supported via the Request Network API. See [Crypto-to-fiat Payments](/api-features/crypto-to-fiat-payments). | ||
| </Accordion> |
There was a problem hiding this comment.
On-ramp (fiat-to-crypto) part of question left unanswered
The accordion title explicitly asks about both "crypto-to-fiat (off-ramp) or fiat-to-crypto (on-ramp) payments", but the answer only addresses the crypto-to-fiat direction. A reader looking for on-ramp information will find no answer here.
Recommendation: Add a brief sentence clarifying the status of on-ramp support. For example: "Fiat-to-crypto on-ramp payments are not currently supported via the API." This ensures the answer fully addresses the question asked.
| ### Payment Reference | ||
|
|
||
| In the Reference-based Payment Networks, Payments are linked to Requests via a `paymentReference` which is derived from the `requestId` and payment recipient address. For details see [Payment Reference](https://docs.request.network/advanced/request-network-sdk/sdk-guides/request-client/payment-reference) | ||
| In the Reference-based Payment Networks, Payments are linked to Requests via a `paymentReference` which is derived from the `requestId` and payment recipient address. For details see [SDK (Legacy)](/sdk-legacy/overview). | ||
|
|
||
| ### Conversion Payment | ||
|
|
||
| A "conversion" request is denominated in one currency but paid in another currency. This is facilitated by on-chain price feeds provided by oracles. The typical use case is to denominate a request in fiat like USD and pay the request in stablecoins like USDC or DAI. For details see [Conversion Payment](https://docs.request.network/advanced/request-network-sdk/sdk-guides/payment/conversion-request) | ||
| A "conversion" request is denominated in one currency but paid in another currency. This is facilitated by on-chain price feeds provided by oracles. The typical use case is to denominate a request in fiat like USD and pay the request in stablecoins like USDC or DAI. For details see [Conversion Payments](/api-features/conversion-payments). | ||
|
|
||
| ### Swap-to-pay Payment | ||
|
|
||
| A "swap-to-pay" payment is where the payment sender sends one currency but the payment recipient receives a different currency. For details see [Swap-to-Pay Payment](https://docs.request.network/advanced/request-network-sdk/sdk-guides/payment/swap-to-pay-request) | ||
| A "swap-to-pay" payment is where the payment sender sends one currency but the payment recipient receives a different currency. For details see [SDK (Legacy)](/sdk-legacy/overview). | ||
|
|
||
| ### Swap-to-Conversion Payment | ||
|
|
||
| A "swap-to-conversion" payment is where the request is denominated in currency A, the payer sends currency B and the payee receives currency C. For details see [Swap-to-Conversion Payment](https://docs.request.network/advanced/request-network-sdk/sdk-guides/payment/swap-to-conversion-request) | ||
| A "swap-to-conversion" payment is where the request is denominated in currency A, the payer sends currency B and the payee receives currency C. For details see [SDK (Legacy)](/sdk-legacy/overview). |
There was a problem hiding this comment.
Three glossary "For details" links changed from specific guides to generic overview
Three glossary entries were updated to link to the generic /sdk-legacy/overview instead of their original specific guide pages:
- Payment Reference (line 103): was
payment-referenceguide - Swap-to-pay Payment (line 111): was
swap-to-pay-requestguide - Swap-to-Conversion Payment (line 115): was
swap-to-conversion-requestguide
The "For details see" text now points readers to a generic overview rather than documentation specific to each concept, reducing the usefulness of these reference links.
Recommendation: If the specific SDK guide pages still exist (even under sdk-legacy/), consider linking to them directly for more targeted documentation. If those pages have been removed, update the prose to reflect that detailed documentation is unavailable rather than implying the overview provides concept-specific details.
Additional Comments (1)
The security warning block that previously explained risks of exposing private keys in client-side code was deleted in this PR, but the Recommendation: Either restore a condensed security note alongside the code snippet, or replace the example pattern with a safer alternative (e.g., Web3 wallet providers like MetaMask, or server-side signing). This is especially important since the snippet shows a frontend context ( |
1 participant
TL;DR
Removed AI-generated content warnings and updated internal documentation links to use relative paths instead of absolute URLs.
What changed?
/resources/supported-chains-and-currenciesinstead ofhttps://docs.request.network/get-started/supported-chains)How to test?
Why make this change?
The AI-generated content warnings were no longer needed as the content has been reviewed and validated. Using relative paths for internal links improves maintainability and ensures links work correctly across different deployment environments. The changes also reflect current product capabilities, such as crypto-to-fiat payment support via the API.