From bf35f0c768c3625483e1cba7146dc24dd4e35f76 Mon Sep 17 00:00:00 2001
From: Dewey Dunnington <dewey@fishandwhistle.net>
Date: Mon, 20 Dec 2021 21:12:14 -0400
Subject: [PATCH] fix urls

---
 README.Rmd |  4 ++--
 README.md  | 28 ++++++++++++++--------------
 2 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/README.Rmd b/README.Rmd
index 89a828ce..db6f9bc6 100644
--- a/README.Rmd
+++ b/README.Rmd
@@ -17,7 +17,7 @@ knitr::opts_chunk$set(
 
 <!-- badges: start -->
 [![R build status](https://github.com/paleolimbot/wk/workflows/R-CMD-check/badge.svg)](https://github.com/paleolimbot/wk/actions)
-[![Codecov test coverage](https://codecov.io/gh/paleolimbot/wk/branch/master/graph/badge.svg)](https://codecov.io/gh/paleolimbot/wk?branch=master)
+[![Codecov test coverage](https://codecov.io/gh/paleolimbot/wk/branch/master/graph/badge.svg)](https://app.codecov.io/gh/paleolimbot/wk?branch=master)
 <!-- badges: end -->
 
 The goal of wk is to provide lightweight R, C, and C++ infrastructure for a distributed ecosystem of packages that operate on collections of coordinates. First, wk provides vector classes for points, circles, rectangles, well-known text (WKT), and well-known binary (WKB). Second, wk provides a C API and set of S3 generics for event-based iteration over vectors of geometries.
@@ -61,7 +61,7 @@ The wk package is made up of readers, handlers, and filters. Readers parse the v
 
 ## C API
 
-The distributed nature of the wk framework is powered by a [~100-line header](https://github.com/paleolimbot/wk/blob/master/inst/include/wk-v1.h) describing the types of information that parsers typically encounter when reading geometries and the order in which that information is typically organized. Detailed information is available in the [C and C++ API article](https://paleolimbot.github.io/wk/dev/articles/articles/philosophy.html).
+The distributed nature of the wk framework is powered by a [~100-line header](https://github.com/paleolimbot/wk/blob/master/inst/include/wk-v1.h) describing the types of information that parsers typically encounter when reading geometries and the order in which that information is typically organized. Detailed information is available in the [C and C++ API article](https://paleolimbot.github.io/wk/articles/articles/programming.html).
 
 ```{r}
 wk_debug(
diff --git a/README.md b/README.md
index 4eae4270..de985d05 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@
 [![R build
 status](https://github.com/paleolimbot/wk/workflows/R-CMD-check/badge.svg)](https://github.com/paleolimbot/wk/actions)
 [![Codecov test
-coverage](https://codecov.io/gh/paleolimbot/wk/branch/master/graph/badge.svg)](https://codecov.io/gh/paleolimbot/wk?branch=master)
+coverage](https://codecov.io/gh/paleolimbot/wk/branch/master/graph/badge.svg)](https://app.codecov.io/gh/paleolimbot/wk?branch=master)
 <!-- badges: end -->
 
 The goal of wk is to provide lightweight R, C, and C++ infrastructure
@@ -87,7 +87,7 @@ describing the types of information that parsers typically encounter
 when reading geometries and the order in which that information is
 typically organized. Detailed information is available in the [C and C++
 API
-article](https://paleolimbot.github.io/wk/dev/articles/articles/philosophy.html).
+article](https://paleolimbot.github.io/wk/articles/articles/programming.html).
 
 ``` r
 wk_debug(
@@ -95,12 +95,12 @@ wk_debug(
   wkt_format_handler(max_coords = 2)
 )
 #> initialize (dirty = 0  -> 1)
-#> vector_start: <Unknown type / 0>[1] <0x16d1d1e18> => WK_CONTINUE
-#>   feature_start (1): <0x16d1d1e18>  => WK_CONTINUE
-#>     geometry_start (<none>): LINESTRING[UNKNOWN] <0x16d1d1d20> => WK_CONTINUE
-#>       coord (1): <0x16d1d1d20> (1.000000 1.000000)  => WK_CONTINUE
-#>       coord (2): <0x16d1d1d20> (2.000000 2.000000)  => WK_ABORT_FEATURE
-#> vector_end: <0x16d1d1e18>
+#> vector_start: <Unknown type / 0>[1] <0x16dd25e18> => WK_CONTINUE
+#>   feature_start (1): <0x16dd25e18>  => WK_CONTINUE
+#>     geometry_start (<none>): LINESTRING[UNKNOWN] <0x16dd25d20> => WK_CONTINUE
+#>       coord (1): <0x16dd25d20> (1.000000 1.000000)  => WK_CONTINUE
+#>       coord (2): <0x16dd25d20> (2.000000 2.000000)  => WK_ABORT_FEATURE
+#> vector_end: <0x16dd25e18>
 #> deinitialize
 #> [1] "LINESTRING (1 1, 2 2..."
 ```
@@ -117,12 +117,12 @@ wk_debug(
   wkt_format_handler(max_coords = 2)
 )
 #> initialize (dirty = 0  -> 1)
-#> vector_start: LINESTRING B[1] <0x16d1d4df0> => WK_CONTINUE
-#>   feature_start (1): <0x16d1d4df0>  => WK_CONTINUE
-#>     geometry_start (<none>): LINESTRING[3] <0x16d1d4d50> => WK_CONTINUE
-#>       coord (1): <0x16d1d4d50> (1.000000 1.000000)  => WK_CONTINUE
-#>       coord (2): <0x16d1d4d50> (2.000000 2.000000)  => WK_ABORT_FEATURE
-#> vector_end: <0x16d1d4df0>
+#> vector_start: LINESTRING B[1] <0x16dd28df0> => WK_CONTINUE
+#>   feature_start (1): <0x16dd28df0>  => WK_CONTINUE
+#>     geometry_start (<none>): LINESTRING[3] <0x16dd28d50> => WK_CONTINUE
+#>       coord (1): <0x16dd28d50> (1.000000 1.000000)  => WK_CONTINUE
+#>       coord (2): <0x16dd28d50> (2.000000 2.000000)  => WK_ABORT_FEATURE
+#> vector_end: <0x16dd28df0>
 #> deinitialize
 #> [1] "LINESTRING (1 1, 2 2..."
 ```