From 9860f8f18640b06907785c1e930b17f39c8f4d6e Mon Sep 17 00:00:00 2001
From: Gleb Ebert <5892266+gl-eb@users.noreply.github.com>
Date: Fri, 6 Oct 2023 12:49:39 +0200
Subject: [PATCH] Fix link to tidyverse design principles

---
 vignettes/articles/column-names.Rmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vignettes/articles/column-names.Rmd b/vignettes/articles/column-names.Rmd
index e8ca2e37..08536eb1 100644
--- a/vignettes/articles/column-names.Rmd
+++ b/vignettes/articles/column-names.Rmd
@@ -33,7 +33,7 @@ But users have long wanted a way to specify a name repair *strategy*, as opposed
 As of v1.2.0, readxl provides the `.name_repair` argument, which affords control over how column names are checked or repaired.
 
 The `.name_repair` argument in `read_excel()`, `read_xls()`, and `read_xlsx()` works exactly the same way as it does in [`tibble::tibble()`](https://tibble.tidyverse.org/reference/tibble.html) and [`tibble::as_tibble()`](https://tibble.tidyverse.org/reference/as_tibble.html).
-The reasoning behind the name repair strategy is laid out in [principles.tidyverse.org](https://principles.tidyverse.org/names-attribute.html).
+The reasoning behind the name repair strategy is laid out in [design.tidyverse.org](https://design.tidyverse.org/names.html).
 
 readxl's default is `.name_repair = "unique"`, which ensures each column has a unique name.
 If that is already true of the column names, readxl won't touch them.