Repository navigation
docs: add descriptive link text to documentation (#1005) - #1046
Merged
ayshadogo merged 1 commit intoOct 19, 2026
Merged
Conversation
|
@odehsamuel Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
Resolves #1005.
This PR improves documentation accessibility across the repository by replacing non-descriptive link labels (such as "docs", "View Guide", raw paths, and vague phrases) and bare URLs with descriptive link text that clearly identifies destinations and includes target filenames where linking to local files.
Key Changes
Descriptive Link Text for Local Files & Runbooks:
[docs/error_codes.md](./error_codes.md)->[the error codes reference (error_codes.md)](./error_codes.md)) acrossdocs/API_REFERENCE.mdanddocs/COMPREHENSIVE_API_DOCS.md.[maintenance window](./MAINTENANCE_WINDOWS.md)->[maintenance window (MAINTENANCE_WINDOWS.md)](./MAINTENANCE_WINDOWS.md)) indocs/UPGRADE_AND_ROLLBACK.mdanddocs/COMMUNICATION_TEMPLATES.md.docs/videos/README.mdto specific companion guide filenames ([escrow-contract-walkthrough.md](escrow-contract-walkthrough.md), etc.).examples/README.mdto include.rsextensions ([deploy_contract.rs](src/bin/deploy_contract.rs), etc.) matching the pattern used insdk/examples/README.md.docs/ADRs/README.md,docs/QUERY_OPTIMIZATION.md,docs/RETENTION_AND_PRUNING.md,docs/STORAGE.md, anddocs/CONTRACTS.md.docs/error_codes.md([balance.rs],[sanitize.rs]).Replaced Bare URLs:
docs/DEVELOPER_ENVIRONMENT.mdwith descriptive labels ([Rust installation guide](...),[Soroban CLI setup guide](...), etc.).docs/TOKEN_SETUP.mdinto descriptive link text.CONTRIBUTING.mdwith[rustup, the Rust toolchain installer](https://rustup.rs)and descriptive Soroban documentation links.Cross-Repository & Sibling Repository Verification:
README.mdfor references to sibling repositories (lumora-web,lumora-services,lumora-contracts,lumora-mobile,lumora-design-system). Verified that these entries under "Organization Repositories" are structural section headings rather than links, preserving existing destinations without introducing arbitrary external URLs.Reference-Style Links & Destination Integrity:
CHANGELOG.md) are well-formed and valid.Noted Pre-Existing Issues (Reported Separately):
docs/ADMIN_MULTISIG.md(line 222) contains an author-local file path URLfile:///c:/Users/hp/OneDrive/Desktop/GrantFox/stellarAid-contract/contracts/campaign/src/lib.rs. Preserved destination per the constraint not to alter destinations in this pass, reported here for follow-up.Acceptance Criteria Checklist