replaced Piazza with more generic "the class forum"

background/background.tex

@@ -199,7 +199,7 @@ \subsection{git}
 \end{lstlisting}
 
 Don't panic, but your repository may be in an unworkable state.
-If you aren't nearing a deadline, come to office hours or ask your question on Piazza, and we'd be happy to help.
+If you aren't nearing a deadline, come to office hours or ask your question on Edstem, and we'd be happy to help.
 In an emergency scenario, delete your repository and re-clone (you'll have to add the \keyword{release} as above).
 \textbf{This will lose any local uncommitted changes. Make sure to copy any files you were working on outside the directory, remove and copy them back in}
 
@@ -986,15 +986,15 @@ \subsection{C Development}
 \subsection{Optional: Just for fun}
 
 \begin{itemize}
-\item Convert a song lyrics into System Programming and C code covered in this wiki book and share on Piazza.
-\item Find, in your opinion, the best and worst C code on the web and post the link to Piazza.
-\item Write a short C program with a deliberate subtle C bug and post it on Piazza to see if others can spot your bug.
-\item Do you have any cool/disastrous system programming bugs you've heard about? Feel free to share with your peers and the course staff on Piazza.
+\item Convert a song lyrics into System Programming and C code covered in this wiki book and share on the class forum.
+\item Find, in your opinion, the best and worst C code on the web and post the link to the class forum.
+\item Write a short C program with a deliberate subtle C bug and post it on the class forum to see if others can spot your bug.
+\item Do you have any cool/disastrous system programming bugs you've heard about? Feel free to share with your peers and the course staff on the class forum.
 \end{itemize}
 
-\section{UIUC Specific Guidelines}
+\section{University of Illinois Specific Guidelines}
 
-\subsection{Piazza}
+\subsection{The class forum}
 
 TAs and student assistants get a ton of questions.
 Some are well-researched, and some are not.
@@ -1004,18 +1004,18 @@ \subsection{Piazza}
 \begin{enumerate}
 \item Am I running on my Virtual Machine?
 \item \textbf{Did I check the man pages?}
-\item Have I searched for similar questions/followups on Piazza?
+\item Have I searched for similar questions/followups on the class forum?
 \item Have I read the MP/Lab specification completely?
 \item Have I watched all of the videos?
 \item Did I Google the error message and a few permutations thereof if necessary? How about StackOverflow.
 \item Did I try commenting out, printing, and/or stepping through parts of the code bit by bit to find out precisely where the error occurs?
 \item \textbf{Did I commit my code to git in case the TAs need more context?}
-\item Did I include the console/GDB/Valgrind output **AND** code surrounding the bug in my Piazza post?
+\item Did I include the console/GDB/Valgrind output **AND** code surrounding the bug in my the class forum post?
 \item Have I fixed other segmentation faults unrelated to the issue I'm having?
 \item Am I following good programming practice? (i.e. encapsulation, functions to limit repetition, etc)
 \end{enumerate}
 
-The biggest tip that we can give you when asking a question on piazza if you want a swift answer is to \textbf{ask your question like you were trying to answer it}. Like before you ask a question, try to answer it yourself. If you are thinking about posting
+The biggest tip that we can give you when asking a question on the class forum if you want a swift answer is to \textbf{ask your question like you were trying to answer it}. Like before you ask a question, try to answer it yourself. If you are thinking about posting
 
 \begin{quote}
 Hi, My code got a 50% on the autograder. I tried testing it a lot, but couldn't get it to fail. Can you give me some hints as to the test cases