Broken link in documentation
See original GitHub issueProblem description
I found that the bottom link in this page is broken: http://pravega.io/docs/latest/streamcuts/
The broken link contains this variable.pravega_samples_verion
, which may be a typo (should the variable be called variable.pravega_samples_veri(s)on
?). It would be necessary to check that the rest of links that use this variable are working.
Problem location Documentation.
Suggestions for an improvement Fix broken links.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to find and fix broken links on your knowledge base
You can easily identify your broken links using the Links status checker. Once you've identified your broken links, you can navigate to your ......
Read more >Ways to Handle Broken Links - ClickHelp
Broken links are unacceptable in documentation because they influence the quality of documentation and SEO. With ClickHelp you can handle broken links easily....
Read more >docs/checking-broken-links.md at master - GitHub
Checking for broken links is a science on its own. External webpages, internal sites and references to anchors can cause broken links in...
Read more >Fixing a broken link - Caseware
Links can be broken for a variety of reasons and it can take considerable time to diagnose the problem. Some examples of actions...
Read more >HowTo - fix broken links in documents with ReplaceMagic
Fix broken links, link fixer tool for Office, PDF and text documents.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Your are right Raul : i assure that will redo according to the procedure
This has been temporarily fixed via #2867, but we still need to make use of variables in documentation to avoid hard coded release numbers.