bug#30276: typos in the manual (api-macros, vm)

[Matt Wette]

A couple typos in the maual

--- api-macros.texi-fix 2018-01-28 13:22:52.305712852 -0800
+++ api-macros.texi 2017-11-19 11:22:01.0 -0800
@@ -1280,7 +1280,7 @@
 
 In this way @code{(macroexpand @var{foo})} is equivalent to

 @code{(macroexpand @var{foo} 'e '(eval))}.  The second argument is the
-mode (@code{'e} for ``eval'') and the third is the
+mode (@code{'e} for ``eval'') and the second is the
 eval-syntax-expanders-when parameter (only @code{eval} in this default
 setting).
 
--- vm.texi	2017-05-13 09:41:37.0 -0700

+++ vm.texi-fix 2018-01-28 13:21:31.621618026 -0800
@@ -719,7 +719,7 @@
 
 For calls, both in tail position and in non-tail position, we require

 that the procedure and the arguments already be shuffled into place
-befor the call instruction.  ``Into place'' for a tail call means that
+before the call instruction.  ``Into place'' for a tail call means that
 the procedure should be in slot 0, relative to the @code{fp}, and the
 arguments should follow.  For a non-tail call, if the procedure is in
 @code{fp}-relative slot @var{n}, the arguments should follow from slot

bug#30154: [PATCH] web: Add http-patch.

[Mark H Weaver]

Arun Isaac  writes:

> Mark H Weaver  writes:
>
>> Since PATCH was removed from HTTP over 18 years ago, and is clearly not
>> valid HTTP/1.1, I wonder if it makes sense to add this.
>
>> Do you have a use case where you need it?
>
> Yes, I was using the PowerDNS HTTP API, and some of their API requests
> need the PATCH method.
>
> https://doc.powerdns.com/md/httpapi/api_spec/
>
> If you think it's not a good idea to include http-patch in guile, maybe
> we can export define-http-verb and/or request so that it is easy for
> users to create their own custom HTTP methods. WDYT?

I would prefer to export the 'request' procedure from (web client),
although it should probably be exported as a different name, maybe
'http-request'.  Would that work for you?

   Mark