Apply suggestions from code review

Co-authored-by: Hugh Troeger <troeger.hugh@gmail.com>
finos · Feb 21, 2022 · 6b8bf41 · 6b8bf41
1 parent 3f0b876
commit 6b8bf41
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/api/ref/Errors.md b/docs/api/ref/Errors.md
@@ -54,7 +54,7 @@ enum ChannelError {
 Contains constants representing the errors that can be encountered when calling channels using the [`joinUserChannel`](DesktopAgent#joinuserchannel) or [`getOrCreateChannel`](DesktopAgent#getorcreatechannel) methods, or the [`getCurrentContext`](Channel#getcurrentcontext), [`broadcast`](Channel#broadcast) or [`addContextListener`](Channel#addcontextlistener) methods on the `Channel` object.
 
 #### See also
-* [`DesktopAgent.joinUserChannel`](DesktopAgent#joinusercannel)
+* [`DesktopAgent.joinUserChannel`](DesktopAgent#joinuserchannel)
 * [`DesktopAgent.getOrCreateChannel`](DesktopAgent#getorcreatechannel)
 * [`Channel.broadcast`](Channel#broadcast)
 * [`Channel.addContextListener`](Channel#addcontextlistener)

diff --git a/docs/api/spec.md b/docs/api/spec.md
@@ -299,7 +299,7 @@ fdc3.joinUserChannel(redChannel.id);
 
 Calling `fdc3.broadcast` will now route context to the joined channel.
 
-Channel implementations should ensure that context messages broadcast by an application on a channel should not be delivered back to that same application if they are joined to the channel.
+Channel implementations SHOULD ensure that context messages broadcast by an application on a channel are not delivered back to that same application if they are joined to the channel.
 
   > Prior to FDC3 2.0, 'user' channels were known as 'system' channels. They were renamed in FDC 2.0 to reflect their intended usage, rather than the fact that they are created by system (which could also create 'app' channels). The `joinChannel` function was also renamed to `joinUserChannel` to clarify that it is only intended to be used to join 'user', rather than 'app', channels.