fix: remove trailing white space

Author: lwasser

contribute-open-source/clone-repo.md

@@ -17,82 +17,80 @@ myst_html_meta:
 ---
 
 (clone-repository)=
-# Clone a GitHub Repository to Work Locally 
-How to clone a repo. 
+
+# Clone a GitHub Repository to Work Locally
+
+How to clone a repo.
 
 ## Clone a repo: copy files From GitHub.com to your computer
 
 To work locally with a **GitHub** repository (including forked repos), you must create a local copy of that repository on your computer (a task referred to as `cloning` a repo). You can clone **GitHub** repositories that you own or that are owned by others (e.g., repositories that you have forked to your **GitHub** account).
 
-In either case, cloning allows you to create a local copy of a **GitHub** repository to work with the files locally on your computer. Cloning a repository to your computer is a great way to work on your files locally while still having a copy of your files on the cloud on **GitHub.com**. Following the steps below, you will use the `git clone` command in the **terminal** to clone **GitHub** repositories. 
-
+In either case, cloning allows you to create a local copy of a **GitHub** repository to work with the files locally on your computer. Cloning a repository to your computer is a great way to work on your files locally while still having a copy of your files on the cloud on **GitHub.com**. Following the steps below, you will use the `git clone` command in the **terminal** to clone **GitHub** repositories.
 
 ### Use `Bash` to Change to Your Desired Working Directory
 
 The first step to using any **git** command is changing the current working directory to your desired one.
-In the case of `git clone`, the current working directory needs to be where you want to download a local copy of a **GitHub** repository. 
-
-For this lesson, you will clone a repo locally on your computer (or wherever you work).   
+In the case of `git clone`, the current working directory needs to be where you want to download a local copy of a **GitHub** repository.
 
+For this lesson, you will clone a repo locally on your computer (or wherever you work).
 
 ### Copy a Github.com Repository URL From GitHub.com
 
-To run the `git clone` command, you need the URL for the repository you want to clone (i.e., either a repository owned by you or a fork you created from another user's repository). 
+To run the `git clone` command, you need the URL for the repository you want to clone (i.e., either a repository owned by you or a fork you created from another user's repository).
 
-On the main **GitHub.com** page of the repository, you can click on the green button for `Clone or download`, and copy the URL provided in the box, which will look like this: 
+On the main **GitHub.com** page of the repository, you can click on the green button for `Clone or download`, and copy the URL provided in the box, which will look like this:
 
 `https://github.com/your-username/repo-name`
 
 ::::{todo}
 :::{figure} /images/github/image-coming-soon.png
 :alt: alt text here
 
- You can make a local copy of your forked repository on your computer with the git clone command. 
+ You can make a local copy of your forked repository on your computer with the git clone command.
 :::
 ::::
 
-:::{tip} 
-You can copy the URL directly from your web browser, or in some cases, you might already know the URL. However, in many cases, you will come across a new **GitHub.com** repository on your own and will need to follow these instructions to copy the URL for future use. 
+:::{tip}
+You can copy the URL directly from your web browser, or in some cases, you might already know the URL. However, in many cases, you will come across a new **GitHub.com** repository on your own and will need to follow these instructions to copy the URL for future use.
 :::
 
 ### Run the `git clone` in the shell
 
-Now that you have the URL for a repository that you want to copy locally, you can use the **terminal** to run the `git clone` command followed by the URL that you copied: 
+Now that you have the URL for a repository that you want to copy locally, you can use the **terminal** to run the `git clone` command followed by the URL that you copied:
 
 ```bash
 git clone https://github.com/your-username/repo-name
 ```
 
-You have now made a local copy of a repository. You can double-check that the directory exists using the `ls` command in the **terminal**. 
+You have now made a local copy of a repository. You can double-check that the directory exists using the `ls` command in the **terminal**.
 
 ```bash
-$ ls     
+$ ls
     repo-name
 ```
 
-
 :::{admonition} <i class="fa fa-pencil-square-o" aria-hidden="true"></i> Challenge  - Fork and Clone a Repository
 
 Go to GitHub.com and login. Then use the link below to open the **repo-name** repo.
 
 `https://github.com/pyopensci/repo-name`
 
 * On the main **GitHub.com** page of this repository, you will see a button on the top right that says `Fork`. The number next to `Fork` tells the number of times that the repository has been copied or forked.
-* Click on the `Fork` button and select your **GitHub.com** account as the home of the forked repository. 
+* Click on the `Fork` button and select your **GitHub.com** account as the home of the forked repository.
 * Once you have forked a repository, you will have a copy (or a fork) of that repository in your **GitHub** account. The URL to your fork will contain your username:
 
 `https://github.com/your-username/repo-name`
 
-* Finally, clone the fork that you created above so you have a copy of all the files on github.com on your local computer. 
+* Finally, clone the fork that you created above so you have a copy of all the files on github.com on your local computer.
 
-To make sure you did things right, in bash, cd to the repo-name directory on your computer. 
+To make sure you did things right, in bash, cd to the repo-name directory on your computer.
 Type:
 
-`$ git remote -v` 
+`$ git remote -v`
 
 The paths returned should look something like this:
 
 `https://github.com/your-username/repo-name`
 
-
 :::

contribute-open-source/edit-commit-files.md

@@ -19,46 +19,47 @@ og:image:alt: An image that shows the steps for contributing to open source on G
 ---
 
 (pyos-edit-commit-files)=
+
 # Your First Edits to a File in Your Fork: Edit & Commit
 
-> In this lesson, you’ll learn how to:  
+> In this lesson, you’ll learn how to:
 > <i class="fa-solid fa-circle-check" style="color: #81c0aa;"></i>edit a file directly in your **fork** using GitHub’s interface and commit the changes using only the native GitHub interface
 >
 > If you want to work on the files locally on your laptop, you will need to [clone or make a copy of your repo locally](clone-repo).
 
-Now that you've [identified and commented on an issue](identify-github-issue), [forked the repository](fork-repo), and received approval to work on an issue, it's time to make your changes.  
+Now that you've [identified and commented on an issue](identify-github-issue), [forked the repository](fork-repo), and received approval to work on an issue, it's time to make your changes.
 
 :::{tip}
-💡 Your fix should be **small and text-based**, like updating documentation or fixing a typo.  
+💡 Your fix should be **small and text-based**, like updating documentation or fixing a typo.
 :::
 
-## How to edit a file in your fork  
+## How to edit a file in your fork
 
-GitHub lets you edit files right in your browser. Here’s how:  
+GitHub lets you edit files right in your browser. Here’s how:
 
-1. Navigate to **your fork** of the repository.  
-2. Find the file you want to edit.  
-3. Click the <kbd><i class="fa-solid fa-pencil" style="color: #81c0aa;"></i> Edit</kbd> button.  
+1. Navigate to **your fork** of the repository.
+2. Find the file you want to edit.
+3. Click the <kbd><i class="fa-solid fa-pencil" style="color: #81c0aa;"></i> Edit</kbd> button.
 4. Make your changes and **commit** them.
 
 :::{figure} /images/github/edit-commit-file.gif
-:alt: "GIF showing how to edit and commit a file on GitHub."  
+:alt: "GIF showing how to edit and commit a file on GitHub."
 
 Editing a file directly in the GitHub interface is a straight forward process.
 :::
 
-> **⚡ Quick tip:** You can edit as many files as you want, but GitHub only lets you commit them **one at a time** in the browser.  
+> **⚡ Quick tip:** You can edit as many files as you want, but GitHub only lets you commit them **one at a time** in the browser.
 
-## Ways to edit a file: GitHub vs. GitHub Codespaces  
+## Ways to edit a file: GitHub vs. GitHub Codespaces
 
 GitHub now offers **two ways** to edit files directly in the interface or using the [cloud-based GitHub Codespaces](about-codespace). If you’re making a small change, use GitHub’s interface. If you need to edit multiple files, try Codespaces.
 
-| | Option  | When to Use | Pros | Limitations |  
-|-|---------|------------|------|-------------|  
-| | **GitHub Interface** <i class="fa-solid fa-pencil" style="color: #81c0aa;"></i> | Quick edits (typos, small fixes) | No setup needed, edit in browser | Can only commit one file at a time |  
-| | **GitHub Codespaces** <i class="fa-solid fa-laptop-code" style="color: #81c0aa;"></i> | Editing multiple files | Full VS Code environment in browser | Requires configuration but once configured, you can reuse it |  
+| | Option  | When to Use | Pros | Limitations |
+|-|---------|------------|------|-------------|
+| | **GitHub Interface** <i class="fa-solid fa-pencil" style="color: #81c0aa;"></i> | Quick edits (typos, small fixes) | No setup needed, edit in browser | Can only commit one file at a time |
+| | **GitHub Codespaces** <i class="fa-solid fa-laptop-code" style="color: #81c0aa;"></i> | Editing multiple files | Full VS Code environment in browser | Requires configuration but once configured, you can reuse it |
 
-> **💡 Need to edit multiple files using a coding editor like VsCode or Jupyter?** Learn more about using [GitHub Codespaces](github-codespaces).  
+> **💡 Need to edit multiple files using a coding editor like VsCode or Jupyter?** Learn more about using [GitHub Codespaces](github-codespaces).
 
 ## What is a commit?
 
@@ -85,11 +86,10 @@ Each commit represents **a set of changes** at a specific time.
 You can always **undo or revert** changes using Git.
 :::
 
-:::{admonition} What's next?  
-:class: seealso  
+:::{admonition} What's next?
+:class: seealso
 
-Once you've committed your changes, you can open a **<i class="fa-brands fa-github-alt"></i> pull request (PR)** to suggest your edits to the main project.  
+Once you've committed your changes, you can open a **<i class="fa-brands fa-github-alt"></i> pull request (PR)** to suggest your edits to the main project.
 
-[<i class="fa-solid fa-circle-check" style="color: #81c0aa;"></i> Learn how to create a pull request →](pyos-pull-request)  
+[<i class="fa-solid fa-circle-check" style="color: #81c0aa;"></i> Learn how to create a pull request →](pyos-pull-request)
 :::
-