Wording fixup again

Author: tytan652

text/0045-add-notion-of-protocol.md

@@ -100,10 +100,10 @@ In the future, if we want to support a protocol that doesn't use a server URL, t
 
 #### About service JSON file
 
-- For `services` objects, a `"protocol"` field will be added. This will be used to indicate the protocol for services in situation where:
+- For `services` objects, a `"protocol"` field will be added. This will be used to indicate the protocol for services in situation where one of these is true:
   - The protocol can not be deduced from server's URL prefix.
-  - The service is RTMP but has an HTTP URL as its server URL and it has custom code to request the true server URL through an API in the plugin. In this case the protocol will be enforced to the right protocol.
-- Services that use a protocol that is not registered will not be shown. e.g. OBS Studio without RTMPS support will not show services and servers that rely on RTMPS.
+  - The service is RTMP but has an HTTP URL as its server URL and it has custom code to request the true server URL through an API in the plugin. In this case the protocol will be enforced to the right protocol (e.g., Dacast, YouNow).
+- Services that use a protocol that is not registered will not be shown. For example, OBS Studio without RTMPS support will not show services and servers that rely on RTMPS.
 - Codecs field for audio and video will be added to allow services to limit which codec is compatible with the service.
 - `"output"` field in the `"recommended"` object will be deprecated, but it will be kept for backward compatibility. `const char *(*get_output_type)(void *data)` in `obs_service_info` will no longer be used by `rtmp-services`.
   - The JSON schema will be modified to require the `"protocol"` field when the protocol is not auto-detectable. The same for the `"output"` field to keep backward compatibility.
@@ -114,7 +114,7 @@ In the future, if we want to support a protocol that doesn't use a server URL, t
 
 The user can set a custom server through the service "Custom…", the protocol will be deduced based on URL prefixes from service outputs and default to RTMP if no matches.
 
-NOTE: Allowing the user to manually choose the protocol (e.g. HLS) is part of RFC 39.
+NOTE: Allowing the user to manually choose the protocol (e.g., HLS) is part of RFC 39.
 
 ### Audio encoders