This is an automated email from the ASF dual-hosted git repository.

asorokoumov pushed a commit to branch website-poc-from-asf-template
in repository https://gitbox.apache.org/repos/asf/otava-website.git

commit 26d98bbfffe6d1dee62596caee4bc99fae41f934
Author: Alex Sorokoumov <[email protected]>
AuthorDate: Sat Mar 22 16:04:40 2025 -0700

    Pick up latest changes in docs
---
 docs/basics.md                            | 5 +++--
 docs/getting-started.md                   | 4 ++--
 src/components/HomepageFeatures/index.tsx | 4 +++-
 3 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/docs/basics.md b/docs/basics.md
index 2c179f2..640c0b2 100644
--- a/docs/basics.md
+++ b/docs/basics.md
@@ -162,8 +162,9 @@ $ otava regressions <test or group> --branch <branch> 
--since-version <version>
 $ otava regressions <test or group> --branch <branch> --since-commit <commit>
 ```
 
-Sometimes when working on a feature branch, you may run the tests multiple 
times,
-creating more than one data point. To ignore the previous test results, and 
compare
+When comparing two branches, you generally want to compare the tails of both 
test histories, and
+ specifically a stable sequence from the end that doesn't contain any changes 
in itself.
+ To ignore the older test results, and compare
 only the last few points on the branch with the tail of the main branch,
 use the `--last <n>` selector. E.g. to check regressions on the last run of 
the tests
 on the feature branch:
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 15d5250..54ae59c 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -100,8 +100,8 @@ This command prints interesting results of all runs of the 
test and a list of ch
 A change-point is a moment when a metric value starts to differ significantly 
from the values of the earlier runs and
 when the difference is statistically significant.
 
-Otava calculates the probability (P-value) that the change point was caused by 
chance - the closer to zero, the more
-"sure" it is about the regression or performance improvement. The smaller is 
the actual magnitude of the change, the
+Otava calculates the probability (P-value) that the change point was not 
caused by chance - the closer to zero, the more
+ certain it is about the regression or performance improvement. The smaller 
the magnitude of the change, the
 more data points are needed to confirm the change, therefore Otava may not 
notice the regression immediately after the first run
 that regressed.
 
diff --git a/src/components/HomepageFeatures/index.tsx 
b/src/components/HomepageFeatures/index.tsx
index 879b597..5e1a53b 100644
--- a/src/components/HomepageFeatures/index.tsx
+++ b/src/components/HomepageFeatures/index.tsx
@@ -25,7 +25,9 @@ export default function HomepageFeatures(): JSX.Element {
     <section className={styles.features}>
       <div className="container">
         <div className={clsx("text--center", "padding-horiz--md")}>
-          <h2>Otava - Mapping Performance Changes</h2>
+          <h2>
+            Otava - Change Detection for Continuous Performance Engineering
+          </h2>
           <p className={styles.description}>
             Otava performs statistical analysis of performance test results
             stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It

Reply via email to