Skip to content

Commit

Permalink
fix: fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
edwintye committed Jul 31, 2024
1 parent 0353471 commit 207df23
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ importing this as a submodule is highly recommended as per the hugo official gui
git submodule add https://github.com/alex-shpak/hugo-book.git themes/hugo-book
```

However, our `.github/workflows/hugo.yaml` differs from the official guide in that we our `Checkout` action
However, our `.github/workflows/hugo.yaml` differs from the official guide in that our `Checkout` action
is set to a shallow clone only.

```yaml
Expand Down
2 changes: 1 addition & 1 deletion content/posts/2024-04-14-quick-notes-on-yq-edit.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ tags:
---

One of the best thing about kubernetes, and especially gitops, is that we can re-use the same definitely
across many different environment and clusters via very simple yaml manipulation. Howver, it is also true
across many different environment and clusters via very simple yaml manipulation. However, it is also true
that editing yaml en-masse is not fun and automation is highly desirable. Most people will eventually turn
to `yq`, and at the same time be slightly stuck on the syntax. So I am just out here documenting a few
of the most used commands in my normal work.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -214,9 +214,9 @@ pyroscope.scrape "otel_settings" {

Applying all of the above during and upgrade to `v0.101.0` of the opentelemetry collector contrib where the loadbalancing exporter gain a massive improvements, straight diff:

![profile-diff](/images/2024-07-30-profile-diff-101.png.png)
![profile-diff](/images/2024-07-30-profile-diff-101.png)

and when focused on the `mergeTrace` function where the upgrade took place
and when focused on the `mergeTraces` function where the upgrade took place

![merge-traces](/images/2024-07-30-merge-traces-diff-101.png)

Expand Down

0 comments on commit 207df23

Please sign in to comment.