From 701ed59276e2841d10387154c6dc1883f1a51a02 Mon Sep 17 00:00:00 2001 From: Renato Monteiro <45536168+monteiro-renato@users.noreply.github.com> Date: Thu, 13 Feb 2025 08:27:45 +0100 Subject: [PATCH] Fix small typo in api-load-testing.md --- docs/sources/k6/next/testing-guides/api-load-testing.md | 4 ++-- docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/k6/next/testing-guides/api-load-testing.md b/docs/sources/k6/next/testing-guides/api-load-testing.md index d4d24e64d..06287cb64 100644 --- a/docs/sources/k6/next/testing-guides/api-load-testing.md +++ b/docs/sources/k6/next/testing-guides/api-load-testing.md @@ -148,7 +148,7 @@ To reach a request-rate target (`RequestsRate`), follow this approach: 1. Set the rate frequency to the time unit of the target. Per second or per minute. 1. Get the number of requests per iteration (`RequestsPerIteration`). -1. Set the iteration rate to the requests per second target divided by the number of requests per iteration. +1. Set the iteration rate to the requests per second target divided by the number of requests per iteration. `rate` = `RequestsRate รท RequestsPerIteration`. To reach target of 50 reqs/s with the previous example: @@ -296,7 +296,7 @@ A load test can run thousands or millions of script iterations, each with dozens Every test should have a goal. Engineering organizations set their reliability goals using [Service Level Objectives](https://en.wikipedia.org/wiki/Service-level_objective) (SLOs) to validate availability, performance, or any performance requirements. -SLOs maybe defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application. +SLOs may be defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application. Some example SLOs could be: - That 99% of APIs returning product information respond in less than 600ms. diff --git a/docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md b/docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md index d4d24e64d..48a28f31b 100644 --- a/docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md +++ b/docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md @@ -296,7 +296,7 @@ A load test can run thousands or millions of script iterations, each with dozens Every test should have a goal. Engineering organizations set their reliability goals using [Service Level Objectives](https://en.wikipedia.org/wiki/Service-level_objective) (SLOs) to validate availability, performance, or any performance requirements. -SLOs maybe defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application. +SLOs may be defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application. Some example SLOs could be: - That 99% of APIs returning product information respond in less than 600ms.