[fix] close parens

Author: MattDodsonEnglish

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/05 constant-arrival-rate.md

@@ -5,7 +5,7 @@ excerpt: 'A fixed number of iterations are started in a specified period of time
 
 With the `constant-arrival-rate` executor, k6 starts a fixed number of iterations over a specified period of time.
 It is an open-model executor, meaning iterations start independently of system response (for details, read
-[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed).
+[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed)).
 
 This executor continues to start iterations at the given rate as long as VUs are available.
 The time to execute an iteration can vary with test logic or the system-under-test response time.

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/06 ramping-arrival-rate.md

@@ -5,7 +5,7 @@ excerpt: 'A variable number of iterations are started in a specified period of t
 
 With the `ramping-arrival-rate` executor, k6 starts iterations at a variable rate.
 It is an open-model executor, meaning iterations start independently of system response (for details, read
-[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed).
+[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed)).
 
 This executor has _stages_ that configure target number of iterations and the time k6 takes to reach or stay at this target.
 Unlike the [ramping VUs executor](/using-k6/scenarios/executors/ramping-vus/), which configures VUs,