Skip to content

Commit

Permalink
docs(faq): fix grammar and typos
Browse files Browse the repository at this point in the history
  • Loading branch information
edwin-shdw authored and JanDeDobbeleer committed Jul 9, 2024
1 parent 3d0c85b commit d6ee191
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions website/docs/faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ oh-my-posh init pwsh --config ~/custom.omp.json | Invoke-Expression
```

:::warning
Forcing the entire session to UTF8 can have unwanted side-effects for other executables. We can't be held liable for that,
Forcing the entire session to UTF8 can have unwanted side effects for other executables. We can't be held liable for that,
consider this a temporary workaround until the original PowerShell [issue][pwsh-20733] is resolved.
:::

Expand Down Expand Up @@ -235,7 +235,7 @@ The issue is that PowerShell on Windows doesn't yet default to UTF-8. Resolve th
If the location contains non-ASCII characters, non-UTF-8 PowerShell may provide a wrong path to Oh My Posh, which can break the initialization.

The scenario for non-ASCII location:
- Your computer has a non-ASCII user name.
- Your computer has a non-ASCII username.
- Your [config file](./installation/customize.mdx) is under your `$HOME`.
:::

Expand All @@ -262,7 +262,7 @@ $OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = New-Obj
### Zsh: No command history (Ctrl+R does not work)

This issue occurs when you're using plain zsh in combination with Oh My Posh.
You fix this by can adding the right configuration to `~/.zshrc`.
You can fix this by adding the right configuration to `~/.zshrc`.

```bash
HISTFILE=~/.zsh_history
Expand Down

0 comments on commit d6ee191

Please sign in to comment.