docs: add notes

---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
  - task: lint_filenames
    status: passed
  - task: lint_editorconfig
    status: passed
  - task: lint_markdown
    status: passed
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: na
  - task: lint_javascript_tests
    status: na
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: na
  - task: lint_typescript_declarations
    status: na
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---

Author: kgryte

lib/node_modules/@stdlib/stats/strided/dztest/README.md

@@ -26,7 +26,11 @@ limitations under the License.
 
 <section class="intro">
 
-TODO: add introduction
+A Z-test commonly refers to a one-sample location test which compares the mean of a set of measurements `X` to a given constant when the standard deviation is known. A Z-test supports testing three different null hypotheses `H0`:
+
+-   `H0: μ ≥ μ0` versus the alternative hypothesis `H1: μ < μ0`.
+-   `H0: μ ≤ μ0` versus the alternative hypothesis `H1: μ > μ0`.
+-   `H0: μ = μ0` versus the alternative hypothesis `H1: μ ≠ μ0`.
 
 </section>
 
@@ -150,6 +154,10 @@ var bool = ( out === results );
 
 <section class="notes">
 
+## Notes
+
+-   As a general rule of thumb, a Z-test is most reliable when `N >= 50`. For smaller sample sizes or when the standard deviation is unknown, prefer a t-test.
+
 </section>
 
 <!-- /.notes -->