fix: blog spelling errors detected by vale

Signed-off-by: Terry Howe <terrylhowe@gmail.com>
oras-project · Sep 12, 2024 · e5ca939 · e5ca939
1 parent 812dbdd
commit e5ca939
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 8 deletions.
diff --git a/blog/2021-09-15-oras-artifacts-draft-specification-release/index.mdx b/blog/2021-09-15-oras-artifacts-draft-specification-release/index.mdx
@@ -11,7 +11,7 @@ Today, the [OCI Registry As Storage (ORAS)](https://oras.land/) project maintain
 
 ![Net Monitor Graph](./img/net-monitor-graph.png)
 
-As cloud native development continues to grow, we have seen increased community interest in evolving registries to natively store, discover, and pull a graph of supply chain artifacts. Artifact references are important for many use cases such as adding Software Bill of Materials (SBoM), security scan results, and container image signing. With the release of the artifacts specification, end-user tooling can now implement discovery that makes it feasible to determine if there are any references attached to a container image, answering the key question: “What SBOMs or signatures are associated with this container image?” 
+As cloud native development continues to grow, we have seen increased community interest in evolving registries to natively store, discover, and pull a graph of supply chain artifacts. Artifact references are important for many use cases such as adding Software Bill of Materials (SBOM), security scan results, and container image signing. With the release of the artifacts specification, end-user tooling can now implement discovery that makes it feasible to determine if there are any references attached to a container image, answering the key question: “What SBOMs or signatures are associated with this container image?” 
 
 
 The ORAS Project was accepted in June 2021 as a Cloud Native Computing Foundation (CNCF) Sandbox project. It is important that we hear from the community as we advance the artifact-spec capability; if you maintain or are implementing a container registry, we are particularly [interested in your feedback](https://github.com/oras-project/artifacts-spec#community). Working together, we can improve supply chain artifact security in the cloud native ecosystem. 
diff --git a/blog/2022-09-27-oras-0.14-and-future/index.mdx b/blog/2022-09-27-oras-0.14-and-future/index.mdx
@@ -17,9 +17,9 @@ Please see the [Release Notes](https://github.com/oras-project/oras/releases/tag
 
 Prior to ORAS CLI v0.14 release, the ORAS Go library, also released v2.0.0-rc.2 to support [artifacts-spec v1.0.0-rc.2](https://github.com/oras-project/artifacts-spec/releases/tag/v1.0.0-rc.2) and provides new functions to enable developers to build your own OCI client tool.
 
-As cloud native development continues to grow, we have seen increased community interest in evolving registries to natively store, pull, copy, and discover a graph of supply chain artifacts. Artifact references are important for many use cases such as adding Software Bill of Materials (SBoM), security scan results, and container image signatures. 
+As cloud native development continues to grow, we have seen increased community interest in evolving registries to natively store, pull, copy, and discover a graph of supply chain artifacts. Artifact references are important for many use cases such as adding Software Bill of Materials (SBOM), security scan results, and container image signatures. 
 
-This blog will demonstrate how to use ORAS CLI v0.14 to copy an image from a public registry validated by Microsoft to a private registry, then attach an SBoM to it and discover the reference in a tree graph.
+This blog will demonstrate how to use ORAS CLI v0.14 to copy an image from a public registry validated by Microsoft to a private registry, then attach an SBOM to it and discover the reference in a tree graph.
 
 ![ORAS workflow](./img/oras-workflow.png)
 

diff --git a/blog/2023-10-14-lightweight-cloud-registry-oras/index.mdx b/blog/2023-10-14-lightweight-cloud-registry-oras/index.mdx
@@ -15,7 +15,7 @@ What if I told you there was a lightweight alternative?
 ## Everything Should Be a File
 
 One of the great Unix philosophies is the concept of making everything a file.
-Modems, keyboards, printers, disk drives, serial interfaces, configuration, kernel parameteres, IPC, everything and anything is a file that you can `read()` and/or `write()`.
+Modems, keyboards, printers, disk drives, serial interfaces, configuration, kernel parameters, IPC, everything and anything is a file that you can `read()` and/or `write()`.
 
 In a nutshell, this separates a many concerns to the file system layer instead of your program.  
 It allows, among other things, plugging stuff into any program without writing special integration code.
@@ -67,7 +67,7 @@ Now that we have the all the parts, it's just a matter of combining them!
 
 ### Creating some test artifacts
 
-Lets's first create some artifacts!  
+Let us first create some artifacts!  
 ```sh
 echo "Hello World!" > hello.txt
 echo "Goodbye World!" > goodbye.txt
@@ -112,7 +112,7 @@ cat goodbye.txt
 
 Currently[^1] you can't delete your local `oci-layout` artifacts with `oras manifest delete` or `oras blob delete`
 
-Normally it is the registry's responsibility to garbage collect blobs without any references, but in this case the cli does not have the fucntionality (yet).
+Normally it is the registry's responsibility to garbage collect blobs without any references, but in this case the cli does not have the functionality (yet).
 
 It is still possible to just do `rm -rf s3/my-repo`, but that is probably not what you want to do.
 

diff --git a/blog/2024-05-29-oras-1.2.0-and-oras-go-2.5.0/index.mdx b/blog/2024-05-29-oras-1.2.0-and-oras-go-2.5.0/index.mdx
@@ -50,7 +50,7 @@ oras push $REGISTRY/$REPO:$TAG1,$TAG2 sbom.spdx vul-scan.json --format json
 }
 ```
 
-Futhermore, if you want to filter out the value of reference and media type of the pushed artifact in the standard output, use Go template functions as follows:
+If you want to filter out the value of reference and media type of the pushed artifact in the standard output, use Go template functions as follows:
 
 ```bash
 oras push $REGISTRY/$REPO:$TAG1,$TAG2 sbom.spdx vul-scan.json --format go-template='{{.reference}}, {{.mediaType}}'
@@ -86,7 +86,7 @@ There are a few bug fixes and a deprecated feature in this release. For a concre
 
 ORAS installation binary is available on Winget, Homebrew, Snap, GitHub and Docker container image. It can be installed via one simple command. Please see the installation guide for your environment.
 
-The [ORAS GitHub Actions](https://github.com/marketplace/actions/setup-oras) has been upgraded to ORAS CLI v1.2.0. ORAS CLI has also been integrated with the hosted runner machines ([Ubuntu 22.04](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#cli-tools) and [Ubuntu 20.04](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2004-Readme.md#cli-tools)) on GitHub Actions and Azure Devops as a preinstalled software. This delivers out-of-box experience to use ORAS in CI/CD pipelines.
+The [ORAS GitHub Actions](https://github.com/marketplace/actions/setup-oras) has been upgraded to ORAS CLI v1.2.0. ORAS CLI has also been integrated with the hosted runner machines ([Ubuntu 22.04](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#cli-tools) and [Ubuntu 20.04](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2004-Readme.md#cli-tools)) on GitHub Actions and Azure DevOps as a preinstalled software. This delivers out-of-box experience to use ORAS in CI/CD pipelines.
 
 ## What's next for ORAS