anchor.diff:  
   === How to enable syntax highlighting ?
   
  -The mimetype of the files opened in new buffers is detected using the
  +The MIME type of the files opened in new buffers is detected using the
   `file` command, and syntax highlighting enabled automatically when
   possible.
   
   === My file seems to be highlighted with the wrong colors, I thought syntax highlighting was detected automatically ?
   
   The `file` utility has several shortcomings, such as detecting the
  -wrong mimetype for a file containing data with different syntax, e.g.
  +wrong MIME type for a file containing data with different syntax, e.g.
   a Python script containing hardcoded HTML templates detected as an HTML
   file.
   
  -Kakoune does its best at detecting file types (using known extensions
  -for a given format for instance), but not much can be done about those
  -ambiguous cases. You might consider writing a custom `$HOME/.magic` file
  -if needed.
  +Kakoune does its best to detect file types (using known extensions for a
  +given format for instance), but not much can be done about those ambiguous
  +cases. You might consider writing a custom `$HOME/.magic` file if needed.
   
   === Can I disable syntax highlighting completely ?
   
  
positive.code: As a fairly compliant follower of the UNIX philosophy, Kakoune does not
  try to implement features that are best handled by separate, dedicated
  tools. Window splitting in terminals is a prime example of that
  concept, where the editor provides commands to interact with several
  terminal multiplexers (e.g. `tmux`), as opposed to emulating their
  functionalities.
  
  
negative.code: 
  === What shell is used to expand `%sh{}` scopes ?
  
  The server expands shell scopes using the `sh` binary, located in one of
  the directories containing all the POSIX standard utilities. This list of
  directories is stored in a system configuration variable, and queried by
  Kakoune at startup.
  
  In most distributions, `/bin/sh` will end up being used.
  
  