Update collaborative-blog-with-jekyll-github.md

en/lessons/collaborative-blog-with-jekyll-github.md

@@ -668,7 +668,7 @@ The bulk of this [lesson’s text](https://github.com/scholarslab/scholarslab.or
 ## Footnotes
 [^1]: Technically, once you commit something (regardless of what branch you are working on), what you have written is publicly visible to anyone who thinks to visit our repo, switch to your particular branch, and look at your commits, or to web crawlers (for example, powering search engines or preserving popular websites). Your work will not appear on your website until you have merged it back into the default branch, though. If you would like to prevent others from seeing your in-progress and finished code in your repo, you can visit your repoʼs settings to change it from “public” to “private”. When this lesson was written, repos with 3 or fewer collaborators can be made private for free, but you must pay to make repos private if you work with more collaborators.  
 [^2]: See "[Ten Hot Topics Around Scholarly Publishing](https://www.mdpi.com/2304-6775/7/2/34/htm#sec2dot7-publications-07-00034)" by Johnathan  P. Tennant, et al.
-[^3]: See _[Planned Obsolescence: Publishing, Technology, and the Future of the Academy](https://nyupress.org/9780814727881/)_ and  _[Generous Thinking: A Generous Approach to Saving the University](https://jhupbooks.press.jhu.edu/title/generous-thinking)_, both by Kathleen Fitzpatrick; and _[Open: The Philosophies and Practices that are Revolutionizing Education and Science](https://www.ubiquitypress.com/site/books/10.5334/bbc/)_, edited by Rajiv S. Jhangiani and Robert Biswas-Diener. [The Debates in Digital Humanities](https://dhdebates.gc.cuny.edu/) series has several contributions that began life as blog posts.
+[^3]: See _[Planned Obsolescence: Publishing, Technology, and the Future of the Academy](https://nyupress.org/9780814727881/)_ and  _[Generous Thinking: A Generous Approach to Saving the University](https://jhupbooks.press.jhu.edu/title/generous-thinking)_, both by Kathleen Fitzpatrick; and _[Open: The Philosophies and Practices that are Revolutionizing Education and Science](https://www.ubiquitypress.com/chapters/e/10.5334/bbc.a)_, edited by Rajiv S. Jhangiani and Robert Biswas-Diener. [The Debates in Digital Humanities](https://dhdebates.gc.cuny.edu/) series has several contributions that began life as blog posts.
 [^4]: Technically, we started off serving ScholarsLab.org from GitHub Pages, but we now use a script that updates the site on our own university servers, whenever we make changes to the default branch on GitHub. Hosting your site on a different server than GitHub Pages is an option that gives you more control over your site, including the ability to run some types of code that GitHub Pages does not allow. As *The Programming Historian* emphasizes use of free resources such as GitHub Pages, in this lesson we do not cover hosting your site on servers you run yourself or pay a company to run.   
 [^5]: See Natasha Roth Rowland's [post on ethical reasons](https://scholarslab.lib.virginia.edu/blog/github-ice-praxis/) you may decide to not use GitHub (or GitLab, or other technology).  
 [^6]: Usually, if you want to build something on the code of an existing repository you [fork that repo](https://help.github.com/en/articles/fork-a-repo). For this lesson, we decided working from a fork would be too confusing because 1) opening a pull request defaults to comparing changes between two repos rather than two branches, and 2) when actually building your own site (rather than the demonstration copy created in this lesson) you will not be dealing with forks.