docs: fix copy

---
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: passed
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---

Author: kgryte

lib/node_modules/@stdlib/ndarray/base/full/README.md

@@ -75,7 +75,7 @@ This function accepts the following arguments:
 
 ## Notes
 
--   If `value` is a number and `dtype` is a complex [data type][@stdlib/ndarray/dtypes], the function creates an output ndarray with a complex number whose real component equals the provided scalar `value` and whose imaginary component is zero.
+-   If `value` is a number and `dtype` is a complex [data type][@stdlib/ndarray/dtypes], the function casts the number to a complex number whose real component equals the provided scalar `value` and whose imaginary component is zero.
 -   A `value` must be able to safely cast to the output ndarray [data type][@stdlib/ndarray/dtypes]. Scalar values having floating-point data types (both real and complex) are allowed to downcast to a lower precision data type of the same kind (e.g., a scalar double-precision floating-point number can be used to fill a `'float32'` output ndarray).
 
 </section>