Minor editorial points to WSDL spec

Marc, Tony and Umit
I was just looking through the (editors' copy) WSDL spec.  Here are some 
minor points - I think that they are all just syntax?
Many thanks
Katy

EDITORIAL SUGGESTION: Change 'or' to 'and/or'
>> 2. Including WSDL Metadata in EPRs
>> 
>> An EPRs metadata section can contain a reference to WSDL metadata or 
can include embedded WSDL metadata.

This suggests that the metadata section contains EITHER a reference OR the 
embedded metadata.  In fact, as stated in section
2.2, the metadata section can include embeded metadata in conjunction with 
a reference:
 
>> In that case, if the InterfaceName or ServiceName elements are also 
included in the metadata section of the EPR, only the ports with the same 
interface as that 
>> specified are to be considered alternative access channels.

I think that the first section should read:
>> 2. Including WSDL Metadata in EPRs
>> 
>> An EPRs metadata section can contain a reference to WSDL metadata 
***and/***or can include embedded WSDL metadata.

EDITORIAL NIT-PICK :o)
Often "EPRs" is used instead of "EPR's" when not talking plural.  e.g.:
>> Including WSDL Metadata in EPRs
>>
>> An ***EPRs*** metadata section can contain a reference to WSDL metadata 
or can include embedded WSDL metadata.

EDITORIAL SUGGESTION:
Section 2.1
Do we need to specify cardinality for InterfaceName, ServiceName and 
EndpointName - i.e. to ensure that there are never multiple ones 
specified?
Section 2.2
As above but with embedded WSDL definitions - do we need to specify max 1?

EDITORIAL SUGGESTION:
New document, (with Anonymous Element):
>> Section 3.2 Anonymous Element
>>      :
>> -   ?optional?: This value indicates that a response endpoint EPR in a 
request message MAY contain an anonymous URI as an address.
Could we add "This defines the default behavior."? Although it is implied 
from the previous section, this might help people reading who aren't 
familiar with the 
text.