minor formatting changes to faq

reference/faq.mdx

@@ -12,17 +12,17 @@ Wave telemetry is very minimal, anonymized, completely optional, and you can opt
 
 ## What shells does Wave Terminal support?
 
-We currently support `bash` and `zsh`. Your environment (including variables, functions, and aliases) is read from the standard bash and zsh startup files (.bash_profile and .zshrc). In order to customize Wave's environment at startup Wave will set the environment variable `WAVESHELL`.
+We currently support *bash* and *zsh*. Your environment (including variables, functions, and aliases) is read from the standard bash and zsh startup files (`.bash_profile` and `.zshrc`). In order to customize Wave's environment at startup Wave will set the environment variable `WAVESHELL`.
 
 ## How do I specify SSH options such as PubkeyAcceptedKeyTypes?
 
-Currently there is no way to specify these option in the Connections UI. A workaround is to add the options to your ~/.ssh/config file. Wave Terminal uses ssh natively under the hood and so any options set in your ssh config will be picked up by Wave directly.
+Currently there is no way to specify these option in the Connections UI. A workaround is to add the options to your `~/.ssh/config` file. Wave Terminal uses ssh natively under the hood and so any options set in your ssh config will be picked up by Wave directly.
 
 ## How can I disable automatic update checks?
 
 By default, Wave will query our GitHub releases feed to determine if any new releases have been published. This check happens once on launch and then again every 8 hours. We use the unauthenticated GitHub REST API and while we do not collect any telemetry on these calls, we cannot guarantee that GitHub will not collect its own telemetry.
 
-If you would like to disable the automatic update checks, you can toggle the "Check for Updates" button in the Settings to the off position (the white circle should be on the left and the button should be grey).
+If you would like to disable the automatic update checks, you can toggle the "*Check for Updates*" button in the Settings to the off position (the white circle should be on the left and the button should be grey).
 
 ## What is your business model, how do you plan on making money?
 
@@ -40,7 +40,7 @@ Wave Terminal uses the JetBrains Mono font which includes 142 code-specific liga
 
 To reload your configuration files and reset the environment of a tab, you should run the command `reset` or (`/reset`).
 
-Wave loads your bash configuration by executing bash with the -l and -i options (so it is an interactive login shell).  That means any changes need to be in your .bash_profile to take effect (unless your .bash_profile also sources your .bashrc).  Note that sessions are persistent in Wave, so even if you change your startup files the changes won't take effect in any currently open tabs (unless you explicitly run `reset`).
+Wave loads your bash configuration by executing bash with the *-l* and *-i* options (so it is an interactive login shell).  That means any changes need to be in your `.bash_profile` to take effect (unless your `.bash_profile` also sources your `.bashrc`).  Note that sessions are persistent in Wave, so even if you change your startup files the changes won't take effect in any currently open tabs (unless you explicitly run `reset`).
 
 ## Do I need to install mshell/waveshell on remote machines to use Wave Terminal?
 
@@ -60,4 +60,4 @@ Yes (must have Wave v0.6.0 or later). If you run `/reset shell=zsh` or `/reset s
 
 When building v0.6.0 we noticed some irregularities in how we were storing bash shell state.  Specifically if your rcfiles produced any spurious output (invalid aliases was a common culprit), the shell state might be saved, but in a broken way.  While migrating to v0.6.0 we flagged any of these invalid states and show this message.
 
-Clicking "reset shell state" (or running the slash command `/reset`) will force Wave to re-read your bash config files and produce a new valid state.  Note that after running the reset, your cwd and environment will be reset as if this was a new session.
+Clicking "*reset shell state*" (or running the slash command `/reset`) will force Wave to re-read your bash config files and produce a new valid state.  Note that after running the reset, your cwd and environment will be reset as if this was a new session.