Add consistent GitHub naming

Author: utkinis

Diff for: slide-notebooks/deploy_notebooks.jl

@@ -1,6 +1,6 @@
 using Literate
 ## include Literate scripts starting with following 3 letters in the deploy
-incl = "l1_"
+incl = "l9_"
 ## Set `sol=true` to produce output with solutions contained and hints stripts. Otherwise the other way around.
 sol = false
 ##

Diff for: slide-notebooks/l2_2-git.jl

@@ -133,8 +133,8 @@ When you contribute new code to a repo (in particular a repo which other people
 In a repo with write permission, the use following work-flow:
 - make a branch and switch to it: `git switch -c some-branch-name`
 - make changes, add files, etc. and commit to the branch.  You can have several commits on the branch.
-- push the branch to Github
-- on the Github web-page a bar with a "open pull request" should show: click it
+- push the branch to GitHub
+- on the GitHub web-page a bar with a "open pull request" should show: click it
 - if you got more changes, just commit and push them to that branch
 - when happy merge the PR
 

Diff for: slide-notebooks/l7_2-tests-ci.jl

@@ -67,8 +67,8 @@ Let's now add CI to this:
 For step 2 we follow the documentation on [https://github.com/julia-actions/julia-runtest](https://github.com/julia-actions/julia-runtest).
 """
 
-#nb # > 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable Github Actions file..
-#md # \note{[PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable Github Actions file.}
+#nb # > 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable GitHub Actions file..
+#md # \note{[PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable GitHub Actions file.}
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
 md"""

Diff for: slide-notebooks/l9_2-doc.jl

@@ -103,7 +103,7 @@ transform(r, θ) = (r*cos(θ), r*sin(θ))
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
 md"""
-### Documentation tools: Github markdown rendering
+### Documentation tools: GitHub markdown rendering
 
 The easiest way to write long-form documentation is to just use GitHub's markdown rendering.
 
@@ -123,7 +123,7 @@ md"""
 ### Documentation tools: Literate.jl
 
 There are several tools which render .jl files (with special formatting) into
-markdown files.  These files can then be added to Github and will be rendered there.
+markdown files.  These files can then be added to GitHub and will be rendered there.
 
 - we're using [Literate.jl](https://github.com/fredrikekre/Literate.jl)
 - format is described [here](https://fredrikekre.github.io/Literate.jl/v2/fileformat/)
@@ -142,7 +142,7 @@ Literate.markdown("car_travels.jl", directory_of_this_file, execute=true, docume
 md"""
 But this is not automatic!  Manual steps: run Literate, add files, commit and push...
 
-or use Github Actions...
+or use GitHub Actions...
 """
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}

Diff for: slide-notebooks/notebooks/l2_2-git.ipynb

@@ -197,8 +197,8 @@
     "In a repo with write permission, the use following work-flow:\n",
     "- make a branch and switch to it: `git switch -c some-branch-name`\n",
     "- make changes, add files, etc. and commit to the branch.  You can have several commits on the branch.\n",
-    "- push the branch to Github\n",
-    "- on the Github web-page a bar with a \"open pull request\" should show: click it\n",
+    "- push the branch to GitHub\n",
+    "- on the GitHub web-page a bar with a \"open pull request\" should show: click it\n",
     "- if you got more changes, just commit and push them to that branch\n",
     "- when happy merge the PR\n",
     "\n",

Diff for: slide-notebooks/notebooks/l7_2-tests-ci.ipynb

@@ -114,7 +114,7 @@
   {
    "cell_type": "markdown",
    "source": [
-    "> 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable Github Actions file.."
+    "> 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable GitHub Actions file.."
    ],
    "metadata": {}
   },

Diff for: slide-notebooks/notebooks/l9_2-doc.ipynb

@@ -177,7 +177,7 @@
   {
    "cell_type": "markdown",
    "source": [
-    "### Documentation tools: Github markdown rendering\n",
+    "### Documentation tools: GitHub markdown rendering\n",
     "\n",
     "The easiest way to write long-form documentation is to just use GitHub's markdown rendering.\n",
     "\n",
@@ -204,7 +204,7 @@
     "### Documentation tools: Literate.jl\n",
     "\n",
     "There are several tools which render .jl files (with special formatting) into\n",
-    "markdown files.  These files can then be added to Github and will be rendered there.\n",
+    "markdown files.  These files can then be added to GitHub and will be rendered there.\n",
     "\n",
     "- we're using [Literate.jl](https://github.com/fredrikekre/Literate.jl)\n",
     "- format is described [here](https://fredrikekre.github.io/Literate.jl/v2/fileformat/)\n",
@@ -230,7 +230,7 @@
    "source": [
     "But this is not automatic!  Manual steps: run Literate, add files, commit and push...\n",
     "\n",
-    "or use Github Actions..."
+    "or use GitHub Actions..."
    ],
    "metadata": {
     "name": "A slide ",

Diff for: website/_literate/l2_2-git_web.jl

@@ -133,8 +133,8 @@ When you contribute new code to a repo (in particular a repo which other people
 In a repo with write permission, the use following work-flow:
 - make a branch and switch to it: `git switch -c some-branch-name`
 - make changes, add files, etc. and commit to the branch.  You can have several commits on the branch.
-- push the branch to Github
-- on the Github web-page a bar with a "open pull request" should show: click it
+- push the branch to GitHub
+- on the GitHub web-page a bar with a "open pull request" should show: click it
 - if you got more changes, just commit and push them to that branch
 - when happy merge the PR
 

Diff for: website/_literate/l7_2-tests-ci_web.jl

@@ -67,8 +67,8 @@ Let's now add CI to this:
 For step 2 we follow the documentation on [https://github.com/julia-actions/julia-runtest](https://github.com/julia-actions/julia-runtest).
 """
 
-#nb # > 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable Github Actions file..
-#md # \note{[PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable Github Actions file.}
+#nb # > 💡 note: [PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable GitHub Actions file..
+#md # \note{[PkgTemplates.jl](https://github.com/invenia/PkgTemplates.jl) is a handy package, which can generate a suitable GitHub Actions file.}
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
 md"""

Diff for: website/_literate/l9_2-doc_web.jl

@@ -103,7 +103,7 @@ transform(r, θ) = (r*cos(θ), r*sin(θ))
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}
 md"""
-### Documentation tools: Github markdown rendering
+### Documentation tools: GitHub markdown rendering
 
 The easiest way to write long-form documentation is to just use GitHub's markdown rendering.
 
@@ -123,7 +123,7 @@ md"""
 ### Documentation tools: Literate.jl
 
 There are several tools which render .jl files (with special formatting) into
-markdown files.  These files can then be added to Github and will be rendered there.
+markdown files.  These files can then be added to GitHub and will be rendered there.
 
 - we're using [Literate.jl](https://github.com/fredrikekre/Literate.jl)
 - format is described [here](https://fredrikekre.github.io/Literate.jl/v2/fileformat/)
@@ -142,7 +142,7 @@ Literate.markdown("car_travels.jl", directory_of_this_file, execute=true, docume
 md"""
 But this is not automatic!  Manual steps: run Literate, add files, commit and push...
 
-or use Github Actions...
+or use GitHub Actions...
 """
 
 #nb # %% A slide [markdown] {"slideshow": {"slide_type": "slide"}}

Diff for: website/index.md

@@ -9,7 +9,7 @@ title = "Solving PDEs in parallel on GPUs with Julia"
 \note{2024 edition starts Tuesday Sept. 17, 12h45. Welcome!}
 
 ## Course information
-This course aims to cover state-of-the-art methods in modern parallel GPU computing, supercomputing and scientific software development with applications to natural sciences and engineering. The course is open source and is available on [Github](https://github.com/eth-vaw-glaciology/course-101-0250-00)
+This course aims to cover state-of-the-art methods in modern parallel GPU computing, supercomputing and scientific software development with applications to natural sciences and engineering. The course is open source and is available on [GitHub](https://github.com/eth-vaw-glaciology/course-101-0250-00).
 
 ~~~
 <center>
@@ -18,7 +18,7 @@ This course aims to cover state-of-the-art methods in modern parallel GPU comput
 ~~~
 
 ### Objective
-The goal of this course is to offer a practical approach to solve systems of partial differential equations in parallel on GPUs using the [Julia programming language](http://www.julialang.org/). Julia combines high-level language expressiveness and low-level language performance which enables efficient code development. The Julia GPU applications will be hosted on Github and implement modern software development practices.
+The goal of this course is to offer a practical approach to solve systems of partial differential equations in parallel on GPUs using the [Julia programming language](http://www.julialang.org/). Julia combines high-level language expressiveness and low-level language performance which enables efficient code development. The Julia GPU applications will be hosted on GitHub and implement modern software development practices.
 
 ### Outline
 - **Part 1**  _Introducing Julia & PDEs_