anchor.diff:  
   === What shell is used to expand `%sh{}` scopes ?
   
  -The server expands shell scopes using the `sh` binary, stored in one of the
  -directories where all the POSIX standard utilities can be found -this list
  -of directories is stored in a system configuration variable, and queried
  -by Kakoune at startup.
  +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.
   
  
positive.code: 
  The name of the project is pronounced "Kak-oon", and is a word taken from a
  New Caledonian dialect based on French. It means a hard blow, usually a punch,
  but generally refers to a blow into which all of one's strength went.
  
  === Is there going to be a Windows port of Kakoune ?
  
  As many features provided by UNIX systems would be missing, or if anything
  much less efficient on a Windows system, the incentive to porting the
  project to this operating system is pretty low.
  
  Moreover, you can get pretty decent performance by using Kakoune on Cygwin
  (which is officially supported).
  
  == Interfacing
  
  
negative.code: 
  === How to enable syntax highlighting ?
  
  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 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 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 ?
  
  