fix(curriculum): Fixed a couple sentences/typos in the Relational Databases Curriculum (#65014)

curriculum/challenges/english/blocks/lecture-introduction-to-git-and-github/68829079ab2abe728a822cc1.md

@@ -18,7 +18,7 @@ jessicawilkins super-awesome-game >> ls
 README.md  index.html script.js  styles.css
 ```
 
-To setup version control for this project using Git, you will need to run the `git init` command in the project directory. This will initialize an empty Git repository so Git can be begin tracking changes for this project. When done correctly you should see a similar output in the terminal:
+To setup version control for this project using Git, you will need to run the `git init` command in the project directory. This will initialize an empty Git repository so Git can begin tracking changes for this project. When done correctly you should see a similar output in the terminal:
 
 ```sh
 jessicawilkins super-awesome-game >> git init
@@ -78,7 +78,7 @@ If you want to stage all unstaged changes, then you can use `git add .` The peri
 git reset name-of-file
 ```
 
-In general though, as long as you are monitoring which files are being added using `git status` before you stage them, then you should be fine.
+In general though, as long as you are monitoring which files are being added using `git status` before you stage them, you should be fine.
 
 Once you stage your files, then you will need to commit them. You can commit your changes by running the `git commit` command. This will open up your preferred editor of choice you set in the Git configuration. Once the editor is open, you can provide a detailed message of your changes. You can also choose to provide a shorter message by using the `git commit -m` command like this:
 

curriculum/challenges/english/blocks/lecture-working-with-code-reviews-branching-deployment-and-ci-cd/68829101d909657350cd80af.md

@@ -39,7 +39,7 @@ Next, set the branch that we are deploying from to `main` to deploy what's on th
 
 You'll then get a choice to deploy from your project's root folder or from a `docs` folder. This feature is used by projects like freeCodeCamp - we used to bundle documentation with our app, so we could deploy just the documentation onto GitHub pages via the `docs` folder. For now, leave it as the `/` (root) folder and hit the "Save" button next to this drop down to save your changes.
 
-One you've saved, you'll see a new input to configure a custom domain. If you have one already, and would like to use it, you can follow the link to the docs to do so. For this lesson, however, we are going to leave this blank.
+Once you've saved, you'll see a new input to configure a custom domain. If you have one already, and would like to use it, you can follow the link to the docs to do so. For this lesson, however, we are going to leave this blank.
 
 You can also see the domain that your new GitHub Pages site has been deployed to. Without a custom domain, this defaults to `<username>.github.io`, where `<username>` is the name of your account (or the organization's account if you are deploying from an org-owned repository). And repository will be served on a path matching the repository's name, `<username>.github.io/<repo-name>`, for instance. If you visit the URL, you will see your site!