Fix urls

README.Rmd

@@ -51,7 +51,7 @@ con <- DBI::dbConnect(RSQLite::SQLite(), ":memory:")
 copy_to(con, mtcars)
 ```
 
-Note that you don't actually need to load dbplyr with `library(dbplyr)`; dplyr automatically loads it for you when it sees you working with a database. Database connections are coordinated by the DBI package. Learn more at <http://dbi.r-dbi.org/>
+Note that you don't actually need to load dbplyr with `library(dbplyr)`; dplyr automatically loads it for you when it sees you working with a database. Database connections are coordinated by the DBI package. Learn more at <https://dbi.r-dbi.org/>
 
 Now you can retrieve a table using `tbl()` (see `?tbl_dbi` for more details). Printing it just retrieves the first few rows:
 

README.md

@@ -54,7 +54,7 @@ copy_to(con, mtcars)
 Note that you don’t actually need to load dbplyr with `library(dbplyr)`;
 dplyr automatically loads it for you when it sees you working with a
 database. Database connections are coordinated by the DBI package. Learn
-more at <http://dbi.r-dbi.org/>
+more at <https://dbi.r-dbi.org/>
 
 Now you can retrieve a table using `tbl()` (see `?tbl_dbi` for more
 details). Printing it just retrieves the first few rows:

vignettes/new-backend.Rmd

@@ -19,7 +19,7 @@ This document describes how to add a new SQL backend to dbplyr. To begin:
   `vignette("backend", package = "DBI")`.
 
 * You'll need a working knowledge of S3. Make sure that you're 
-  [familiar with the basics](http://adv-r.had.co.nz/OO-essentials.html#s3) 
+  [familiar with the basics](https://adv-r.hadley.nz/s3.html) 
   before you start.
 
 This document is still a work in progress, but it will hopefully get you started. I'd also strongly recommend reading the bundled source code for [SQLite](https://github.com/tidyverse/dbplyr/blob/master/R/backend-sqlite.R), [MySQL](https://github.com/tidyverse/dbplyr/blob/master/R/backend-mysql.R), and [PostgreSQL](https://github.com/tidyverse/dbplyr/blob/master/R/backend-postgres.R).

vignettes/translation-function.Rmd

@@ -36,7 +36,7 @@ translate_sql(x ^ 2L, con = simulate_access())
 
 Perfect translation is not possible because databases don't have all the functions that R does. The goal of dplyr is to provide a semantic rather than a literal translation: what you mean, rather than precisely what is done. In fact, even for functions that exist both in databases and R, you shouldn't expect results to be identical; database programmers have different priorities than R core programmers. For example, in R in order to get a higher level of numerical accuracy, `mean()` loops through the data twice. R's `mean()` also provides a `trim` option for computing trimmed means; this is something that databases do not provide. 
 
-If you're interested in how `translate_sql()` is implemented, the basic techniques that underlie the implementation of `translate_sql()` are described in ["Advanced R"](http://adv-r.hadley.nz/translation.html). 
+If you're interested in how `translate_sql()` is implemented, the basic techniques that underlie the implementation of `translate_sql()` are described in ["Advanced R"](https://adv-r.hadley.nz/translation.html). 
 
 ## Basic differences