fix: Removed incorrect notes about precedence

pages/book/expressions.mdx

@@ -4,12 +4,6 @@ import { Callout } from 'nextra/components'
 
 Every operator in Tact forms an expression, but there's much more to uncover as Tact offers a wide range of expressive options to choose from.
 
-<Callout>
-
-  Note, that in Tact all expressions have higher [precedence](/book/operators#precedence) than any given [operator](/book/operators) except for [parentheses](/book/operators#parentheses), which have the highest precedence of all operators and expressions.
-
-</Callout>
-
 ## Literals
 
 Literals represent values in Tact. These are fixed values—not variables—that you _literally_ provide in your code. All literals in Tact are expressions themselves.

pages/book/operators.mdx

@@ -29,7 +29,7 @@ Even though this example may be simple, neglection of precedence rules can often
 
 ## Parentheses, `()`
 
-Parentheses (also can be called round brackets, `(){:tact}`) are more of a punctuation symbols than actual operators, but their [precedence](#precedence) is higher than precedence of any other operator or [expression](/book/expressions). Use parentheses to override order of operations:
+Parentheses (also can be called round brackets, `(){:tact}`) are more of a punctuation symbols than actual operators, but their [precedence](#precedence) is higher than precedence of any other operator. Use parentheses to override order of operations:
 
 ```tact
 5 * 5 - 2;   // 23