mirror of
https://github.com/JanDeDobbeleer/oh-my-posh.git
synced 2024-11-09 20:44:03 -08:00
docs: correct typos
This commit is contained in:
parent
2a8787cf71
commit
59edcc7ed0
|
@ -6,8 +6,8 @@ Only the latest [release][releases] is supported.
|
||||||
|
|
||||||
## Reporting a Vulnerability
|
## Reporting a Vulnerability
|
||||||
|
|
||||||
Vulnerabilities can be send in via [email][email] to avoid publishing in the open.
|
Vulnerabilities can be sent in via [email][email] to avoid publishing in the open.
|
||||||
Oh My Posh does not have a bountry program, neither do we respond to beg bounties.
|
Oh My Posh does not have a bounty program, neither do we respond to bug bounties.
|
||||||
|
|
||||||
For valid security concerns, you can expect a response within 48 hours,
|
For valid security concerns, you can expect a response within 48 hours,
|
||||||
and credit is given once an acceptable fix is found and published.
|
and credit is given once an acceptable fix is found and published.
|
||||||
|
|
|
@ -240,7 +240,7 @@ for any palette color reference in templates/colors.
|
||||||
|
|
||||||
When you want to display the same **sequence of colors** (background and foreground) regardless of which segments are active, you can
|
When you want to display the same **sequence of colors** (background and foreground) regardless of which segments are active, you can
|
||||||
make use of the cycle property. This property is a list of colors which are used one after the other in a continuous loop. A defined
|
make use of the cycle property. This property is a list of colors which are used one after the other in a continuous loop. A defined
|
||||||
cycle always gets precendence over everything else.
|
cycle always gets precedence over everything else.
|
||||||
|
|
||||||
```json
|
```json
|
||||||
...
|
...
|
||||||
|
|
|
@ -39,7 +39,7 @@ Click Push on the top of the screen and select `Force Push` to bring the changes
|
||||||
**I only have 1 commit**
|
**I only have 1 commit**
|
||||||
|
|
||||||
To reword the last commit, we can make use of git's `--amend` switch to add something to our latest commit (code, changes, rewording).
|
To reword the last commit, we can make use of git's `--amend` switch to add something to our latest commit (code, changes, rewording).
|
||||||
Use the following comands to rephrase the last commit and get that change merged!
|
Use the following commands to rephrase the last commit and get that change merged!
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
git commit --amend -m "feat: better worded feature"`
|
git commit --amend -m "feat: better worded feature"`
|
||||||
|
@ -52,7 +52,7 @@ If all of your commits need to go to main because it makes sense to treat these
|
||||||
functionality to reword any commit between `main` and your `HEAD`. To start an interactive rebase, type `git rebase -i main`.
|
functionality to reword any commit between `main` and your `HEAD`. To start an interactive rebase, type `git rebase -i main`.
|
||||||
|
|
||||||
This will open your `$EDITOR` and you can mark the commits you want to reword with `reword` (or `r`) rather than `pick`.
|
This will open your `$EDITOR` and you can mark the commits you want to reword with `reword` (or `r`) rather than `pick`.
|
||||||
Exiting that file will start the rebase and spwan your `$EDITOR` to alter the commit message for each commit you marked as `reword`.
|
Exiting that file will start the rebase and spawn your `$EDITOR` to alter the commit message for each commit you marked as `reword`.
|
||||||
|
|
||||||
Once done, use `git push --force` to bring the changes to the pull request.
|
Once done, use `git push --force` to bring the changes to the pull request.
|
||||||
|
|
||||||
|
|
|
@ -53,7 +53,7 @@ Always proceed with caution to maintain a balance between system performance and
|
||||||
|
|
||||||
You can use the `oh-my-posh debug` functionality to see where Oh My Posh spends its time.
|
You can use the `oh-my-posh debug` functionality to see where Oh My Posh spends its time.
|
||||||
In case there's no clear culprit (timings indicate everything's OK), chances are some modules are the culprit.
|
In case there's no clear culprit (timings indicate everything's OK), chances are some modules are the culprit.
|
||||||
We bootstrap a few PowerShell modules to maximise compatibility, but sometimes these can introduce unwanted side-effects.
|
We bootstrap a few PowerShell modules to maximize compatibility, but sometimes these can introduce unwanted side-effects.
|
||||||
|
|
||||||
The modules we support are:
|
The modules we support are:
|
||||||
|
|
||||||
|
|
|
@ -79,7 +79,7 @@ Please refer to the [Environment Variable][templates-environment-variables] page
|
||||||
|
|
||||||
| Name | Type | Description |
|
| Name | Type | Description |
|
||||||
| ---------- | --------- | --------------------------------------------------------------- |
|
| ---------- | --------- | --------------------------------------------------------------- |
|
||||||
| `.Seconds` | `float64` | a number reprecenting the total tracked time in seconds |
|
| `.Seconds` | `float64` | a number representing the total tracked time in seconds |
|
||||||
| `.Text` | `string` | a string with human readable tracked time (eg: "2 hrs 30 mins") |
|
| `.Text` | `string` | a string with human readable tracked time (eg: "2 hrs 30 mins") |
|
||||||
|
|
||||||
[wt]: https://wakatime.com
|
[wt]: https://wakatime.com
|
||||||
|
|
Loading…
Reference in a new issue