Apply suggestions from code review

Co-authored-by: Eelco Dolstra <edolstra@gmail.com>

doc/manual/src/language/values.md

@@ -108,14 +108,14 @@
 
   > **Note**
   >
-  > Absolute paths makes expressions less portable.
+  > Absolute paths make expressions less portable.
   > In the case where a function translates a path literal into an absolute path string for a configuration file, it is recommended to write a string literal instead.
   > This avoids some confusion about whether files at that location will be used during evaluation.
   > It also avoids unintentional situations where some function might try to copy everything at the location into the store.
 
   If the first component of a path is a `~`, it is interpreted such that the rest of the path were relative to the user's home directory.
   For example, `~/foo` would be equivalent to `/home/edolstra/foo` for a user whose home directory is `/home/edolstra`.
-  Path literals that start with `~` are not allowed in [pure](@docroot@/command-ref/conf-file.md#conf-pure-eval) evaluation or flakes.
+  Path literals that start with `~` are not allowed in [pure](@docroot@/command-ref/conf-file.md#conf-pure-eval) evaluation.
 
   Paths can be used in [string interpolation] and string concatenation.
   For instance, evaluating `"${./foo.txt}"` will cause `foo.txt` from the same directory to be copied into the Nix store and result in the string `"/nix/store/<hash>-foo.txt"`.