Update 03-FAQs-on-PureScript.md (#615)

Pursuit no longer requires, or even allows, parentheses around a symbol in the search box.

01-Getting-Started/03-FAQs-on-PureScript.md

@@ -57,7 +57,7 @@ The average time for learning FP languages in general is usually 3-6 months due
 - The syntax for FP languages are paradigmatically different than the syntax with which most developers are familiar (C/Java/Python). It takes a while to get used to a "different" syntax family before it feels normal. Until it feels normal, reading through code examples will be harder.
     - This project's `Syntax` folder exists to counter the above issue.
 - Related to the above, FP languages often use symbol-based aliases to refer to functions that are well-known to FP Programmers instead of those functions' literal names (e.g. `<$>` instead of `map`, `<$` instead of `voidRight`, `$>` instead of `voidLeft`). It's more concise and similarities between these symbol-based aliases add meaning to them, such as their "direction." Since new learners do not already know that to which function a symbol refers, it can be hard to know what that function even does.
-    - [A Pursuit search that wraps the symbol in parenthensis (e.g. `(<$>)`)](https://pursuit.purescript.org/search?q=%28%3C%24%3E%29) fixes this problem
+    - [A Pursuit search for the symbol (e.g. `<$>`)](https://pursuit.purescript.org/search?q=%3C%24%3E) fixes this problem
     - This project's `Type Classes/ReadMe.md#Functions` section explains how to read the `Type Classes/assets/Type-Class-Functions.xlsx` file, which provides a table that indicates what those symbol-based fuction names are and from where they come.
 - Due to their powerful type systems, FP languages trade errors that occur when running the program (runtime errors) with errors that occur when attempting to build the program via the compiler (compile-time errors). To understand how to debug these compile-time "your program would not work if it was built" errors, one must have a strong understanding of how the compiler and its type system works.
     - This project's `Syntax` folder (and more specifically, the `Syntax/Type-Level Programming Syntax` folder) explain enough to help one understand why some (but not all) problems arise.