Skip to content

fix: update 301 links with trailing slash in secops pages#902

Merged
tamtamchik merged 1 commit into
lidofinance:mainfrom
cakeinpanic:fix-301-secops
May 21, 2026
Merged

fix: update 301 links with trailing slash in secops pages#902
tamtamchik merged 1 commit into
lidofinance:mainfrom
cakeinpanic:fix-301-secops

Conversation

@cakeinpanic
Copy link
Copy Markdown
Contributor

Please, go through these steps before you request a review:

📝 Describe your changes

  1. Fix 301 trailing slash redirects in secops pages

🔎 Attach a source of truth or evidence that allows reviewers to confirm the changes independently

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates a couple of external/internal documentation links in security-related pages to include a trailing slash before anchors/paths, avoiding 301 redirects and improving link stability.

Changes:

  • Update SEAL Safe Harbor “scope-terms” link to include a trailing slash.
  • Update wstETH bridging guide link to include a trailing slash before the anchor.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
docs/security/safeharbor.md Adds trailing slash to Safe Harbor terms link to avoid redirect.
docs/security/audits.md Adds trailing slash before anchor in wstETH bridging guide link to avoid redirect.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@tamtamchik tamtamchik merged commit d40f7cd into lidofinance:main May 21, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants