You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@skywalking.apache.org by ke...@apache.org on 2026/08/24 10:29:01 UTC

(skywalking-eyes) branch main updated: docs: fix typo seperated -> separated (#283)

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

kezhenxu94 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/skywalking-eyes.git


The following commit(s) were added to refs/heads/main by this push:
     new a196742  docs: fix typo seperated -> separated (#283)
a196742 is described below

commit a196742f472feaffafea537ce5a2a4c3c53a8de4
Author: Vaibhav Srivastava <va...@gmail.com>
AuthorDate: Mon Aug 24 15:58:55 2026 +0530

    docs: fix typo seperated -> separated (#283)
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 515685e..a1bed67 100644
--- a/README.md
+++ b/README.md
@@ -884,7 +884,7 @@ header:
 17. The `files` are the files that declare the dependencies of a project, typically, `go.mod` in Go project, `pom.xml` in maven project, and `package.json` in NodeJS project. If it's a relative path, it's relative to the `.licenserc.yaml`.
 18. Declare the licenses which cannot be identified by this tool.
 19. The `name` of the dependency, The name is different for different projects, `PackagePath` in Go project, `GroupID:ArtifactID` in maven project, `PackageName` in NodeJS project. You can use file pattern as described in [the doc](https://pkg.go.dev/path/filepath#Match).
-20. The `version` of the dependency, comma seperated string (such as `1.0,2.0,3.0`), if this is empty, it means all versions of the dependency.
+20. The `version` of the dependency, comma separated string (such as `1.0,2.0,3.0`), if this is empty, it means all versions of the dependency.
 21. The [SPDX ID](https://spdx.org/licenses/) of the dependency license.
 22. The minimum percentage of the file that must contain license text for identifying a license, default is `75`.
 23. The dependencies that should be excluded when analyzing the licenses, this is useful when you declare the dependencies in `pom.xml` with `compile` scope but don't distribute them in package. (Note that non-`compile` scope dependencies are automatically excluded so you don't need to put them here).