From 91b928d52f49dbc9f660f3ab425c4e3fe9aaa1fc Mon Sep 17 00:00:00 2001
From: derdilla <82763757+NobodyForNothing@users.noreply.github.com>
Date: Wed, 3 Jul 2024 19:56:46 +0200
Subject: [PATCH] Fix link in tree hygene doc (#151235)

Link in how section of tree hygiene doc pointed to the wrong url for the style-guide doc introduced in [#148790](https://github.com/flutter/flutter/commit/65abc95542a9866b984f44e8362a9bcfa77a1377).
---
 docs/contributing/Tree-hygiene.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/contributing/Tree-hygiene.md b/docs/contributing/Tree-hygiene.md
index 8684161ff0..6bcca2fa83 100644
--- a/docs/contributing/Tree-hygiene.md
+++ b/docs/contributing/Tree-hygiene.md
@@ -224,7 +224,7 @@ As a reviewer, you are the last line of defense.
 5. Is it testable? Is it tested? **All code must be tested.** Are there asserts? Encourage liberal use of assertions.
 6. Look for mistakes in indenting the code and other trivial formatting problems.
 7. Is new code licensed correctly?
-8. Is the documentation thorough and useful? Look for useless documentation, empty prose, and breadcrumbs. See the [documentation section](hStyle-guide-for-Flutter-repo.md#documentation-dartdocs-javadocs-etc) of our style guide for what that means.
+8. Is the documentation thorough and useful? Look for useless documentation, empty prose, and breadcrumbs. See the [documentation section](Style-guide-for-Flutter-repo.md#documentation-dartdocs-javadocs-etc) of our style guide for what that means.
 9. Check for good grammar in API docs and comments. Check that identifiers are named according to our conventions.
 
 Once you are satisfied with the contribution, and _only_ once you are satisfied,