Clarity change: replace "okay" with "not too hard"

In the original sentence, "These are usually okay to fix, as long as you are familiar with the right tools and know what the error messages mean!", readers might understand 'okay' to mean 'allowable'. The sentence reads like "you probably won't cause a problem if you fix this issue" -- when I think it's actually meant to say "these issues probably aren't too difficult to fix".

files/en-us/learn_web_development/core/scripting/what_went_wrong/index.md

@@ -34,7 +34,7 @@ When you built up the "Guess the number" game in the previous article, you may h
 
 Generally speaking, when you do something wrong in code, there are two main types of error that you'll come across:
 
-- **Syntax errors**: These are spelling errors in your code that actually cause the program not to run at all, or stop working part way through — you will usually be provided with some error messages too. These are usually okay to fix, as long as you are familiar with the right tools and know what the error messages mean!
+- **Syntax errors**: These are spelling errors in your code that actually cause the program not to run at all, or stop working part way through — you will usually be provided with some error messages too. These are usually not too hard to fix, as long as you are familiar with the right tools and know what the error messages mean!
 - **Logic errors**: These are errors where the syntax is actually correct but the code is not what you intended it to be, meaning that program runs successfully but gives incorrect results. These are often harder to fix than syntax errors, as there usually isn't an error message to direct you to the source of the error.
 
 Okay, so it's not quite _that_ simple — there are some other differentiators as you drill down deeper. But the above classifications will do at this early stage in your career. We'll look at both of these types going forward.