Suggestions by @nomisRev

content/blog/2024-10-04-arrow-2-0.md

@@ -29,7 +29,7 @@ empower developers to write more succinct and readable code.
 
 One of the core concepts when working with typed errors is the distinction
 between fail-first and [accumulation of errors](/learn/typed-errors/working-with-typed-errors/#accumulating-different-computations). Until now, the latter mode
-required using `parZip` and `parMap`, which sometimes obscure the actual
+required using `zipOrAccumulate` and `mapOrAccumulate`, which sometimes obscure the actual
 flow of the computation.
 
 In Arrow 2.0 we have sprinkled some DSL dust over `Raise`, and now you can
@@ -38,13 +38,13 @@ general, any `RaiseAccumulate`) you use `by accumulating` to execute some
 computation keeping all the errors.
 
 ```kotlin
-// version with parZip
-parZip(
+// version with `zipOrAccumulate`
+zipOrAccumulate(
     { checkOneThing() },
     { checkOtherThing() }
 ) { a, b -> doSomething(a, b) }
 
-// version with accumulate
+// version with `accumulate`
 accumulate {
     val a by accumulating { checkOneThing() }
     val b by accumulating { checkOtherThing() }