Fix typo (#3093)

Co-authored-by: polluks <polluks@sdf.lonestar.org>

ADVANCED.md

@@ -15,7 +15,7 @@ Advanced fzf examples
   * [Toggling between data sources](#toggling-between-data-sources)
 * [Ripgrep integration](#ripgrep-integration)
   * [Using fzf as the secondary filter](#using-fzf-as-the-secondary-filter)
-  * [Using fzf as interative Ripgrep launcher](#using-fzf-as-interative-ripgrep-launcher)
+  * [Using fzf as interactive Ripgrep launcher](#using-fzf-as-interactive-ripgrep-launcher)
   * [Switching to fzf-only search mode](#switching-to-fzf-only-search-mode)
   * [Switching between Ripgrep mode and fzf mode](#switching-between-ripgrep-mode-and-fzf-mode)
 * [Log tailing](#log-tailing)
@@ -310,7 +310,7 @@ I know it's a lot to digest, let's try to break down the code.
 - Once we selected a line, we open the file with `vim` (`vim
   "${selected[0]}"`) and move the cursor to the line (`+${selected[1]}`).
 
-### Using fzf as interative Ripgrep launcher
+### Using fzf as interactive Ripgrep launcher
 
 We have learned that we can bind `reload` action to a key (e.g.
 `--bind=ctrl-r:execute(ps -ef)`). In the next example, we are going to **bind

README.md

@@ -591,7 +591,7 @@ If ripgrep doesn't find any matches, it will exit with a non-zero exit status,
 and fzf will warn you about it. To suppress the warning message, we added
 `|| true` to the command, so that it always exits with 0.
 
-See ["Using fzf as interative Ripgrep launcher"](https://github.com/junegunn/fzf/blob/master/ADVANCED.md#using-fzf-as-interative-ripgrep-launcher)
+See ["Using fzf as interactive Ripgrep launcher"](https://github.com/junegunn/fzf/blob/master/ADVANCED.md#using-fzf-as-interactive-ripgrep-launcher)
 for a fuller example with preview window options.
 
 ### Preview window