removeo missed mentions of Learn Software application

assignments.yml

@@ -203,7 +203,7 @@ team:
       description: All repositories have at least a "B" Grade on Code Climate.
       worth: 10.0
     - section: "[Infrastructure] Operational Excellence"
-      description: CI, Exceptions, Logging, and all other services listed in the requirements & `service.yml` example are all setup. Bootstrap script works. Service.yml is uploaded with no errors in the Learn Software App.
+      description: CI, Exceptions, Logging, and all other services listed in the requirements & `service.yml` example are all setup. Bootstrap script works. Service.yml is uploaded with no errors.
       worth: 5.0
     - section: "[Assignment Meta] Video"
       description: A short video (~1.5 to 3 min) with a short write up (some bullet points explaining the video) has been provided that indicates the flows that have been implemented. This allows the teaching staff to mark and is often highly valued in a production company. Please note any areas which are still under development, or not fully implemented. Keep in mind the majority of the paths _should_ be implemented.

assignments/a5.md

@@ -174,7 +174,7 @@ Release bodies must include:
 ## Notes
 
 - `service.yml`: This file must be in a specific format and be submitted with no errors. See <https://csc491.dcsil.ca/assignments/a5/> ('Details' of #1, under 'Requirements') for more details on this file.
-- `script/bootstrap`: You can run automated "bootstrap checks" from your repo's profile in the Learn Software app. This functionality will run your script on Mac and Linux. It is not required for it to pass on both, but you should aim for it to pass on at least one of the systems.
+- `script/bootstrap`: It is not required for it to pass on both Mac and Linux, but you should aim for it to pass on at least one of the systems.
 - Logging setup: This is a logging pipeline, like AWS CloudWatch or Sumologic on Heroku
 - NOTE: You must provide a screenshot of the dashboard running your application or releasing the app if applicable. Failure to do so will result in a 0 on the production section, or -50% if you can provide one late.
 - Credentials:

assignments/a7.md

@@ -79,7 +79,7 @@ Release bodies must include:
 | [Product] Design & Accessibility  | The application has a consistent look and feel. You didn't rely on default styles (see below). The flows are not incoherent. This will be a highly subjective area, so feel free to ask for advice before submission (please don't ask the day before, or day of, submission). [Checklist for accessiblity](./accessibility_checklist.md) is filled out and submitted in the team repo | 10.0 |
 | [Infrastructure] Test Coverage  | Tests should cover at least 65% of your application and upload to Code Climate. | 15.0 |
 | [Infrastructure] Code Quality  | All repositories have at least a "B" Grade on Code Climate. | 10.0 |
-| [Infrastructure] Operational Excellence  | CI, Exceptions, Logging, and all other services listed in the requirements & `service.yml` example are all setup. Bootstrap script works. Service.yml is uploaded with no errors in the Learn Software App. | 5.0 |
+| [Infrastructure] Operational Excellence  | CI, Exceptions, Logging, and all other services listed in the requirements & `service.yml` example are all setup. Bootstrap script works. Service.yml is uploaded with no errors. | 5.0 |
 | [Assignment Meta] Video  | A short video (~1.5 to 3 min) with a short write up (some bullet points explaining the video) has been provided that indicates the flows that have been implemented. This allows the teaching staff to mark and is often highly valued in a production company. Please note any areas which are still under development, or not fully implemented. Keep in mind the majority of the paths _should_ be implemented. | 5.0 |
 | Participation & Teamwork (Individual Grade) | Effectively worked as a team member and shared equitable work load during this assignment.<br>Communication was regular and effective & acted in accordance with team principles. | 15.0 |
 | | **Total:** | 100 |

assignments/participation_teamwork.md

@@ -25,7 +25,7 @@ Note that some of these can be easily tracked (GitHub issues, Pull Requests, com
 - Students make a demonstrable effort to join a team by EOD of the first week of class in which you have CSC454/2527 and CSC491/2600 (e.g. if you only have CSC491/2600 in the first week, this is due by the end of the next week)
 - Teams are required to enable and set up standups. CSC491 Students are required to answer the standups at least 8 of the 12 weeks, though they are recommended to answer every week for their team's benefit.
   - Standups must include the questions "What did you work on since the last update?" and "What do you plan to work on next?"
-- Students are required to comment on the "Participation" assignment on the Learn Software app. It must include a paragraph outlining:
+- Students are required to comment on the "Participation" assignment on Quercus. It must include a paragraph outlining:
   - An overview of the work they did for all team projects and assignments
   - An overview of work other CSC491/2600 students did for the CSC491/2600 assignments
   - A general sentiment if you think the work was split fairly

other_pages/schedule.md

@@ -32,7 +32,7 @@ This is a class schedule indicating what we aim to do each week and the recommen
 
 **Summary**
 
-- Lectures are primarilyy syncronous via the Learn Software application
+- Lectures are primarily syncronous during lecture time
 - We will try to bring in some guest speakers
 - 1 TA Lecture
 - 4-5 class working periods