update terminology for Agent to align with system components

[jeremycaine]

An agent has an identity by URI. But they are not necessarily the software that makes the LWS client HTTP requests to the LWS server. Therefore clarify the agent -> LWS client -> LWS server terminology.

---

Preview | Diff

[acoburn]

Does this PR supersede #159? Given the amount of discussion on that other PR, I would recommend closing this PR and continuing the work on #159

[jeremycaine]

On this week's call I asked that and the group said raise a separate PR against the Terminology section . Meanwhile I have update the diagrams in #159 to reflect agent rather than human user.

[acoburn]

On this week's call I asked that and the group said raise a separate PR against the Terminology section . Meanwhile I have update the diagrams in #159 to reflect agent rather than human user.

This PR does much more than modify the terminology section. Small, focused PRs make review much easier. If the intent of this PR is to add one sentence to the agent definition in the terminology section, I would recommend that this PR only include that change.

[elf-pavlik]

@jeremycaine maybe you created branch used for this PR from branch used for #159 rather than from main?

[jeremycaine]

it was my intent to change one sentence to the agent definition in the terminology section - but clearly I've done something wrong and created this PR from the #159 branch - my gh skills fail me.
how do you want me to resolve, close this and reopen on main (I might need help)

[acoburn]

There are several ways to do this, but here's what I would do in this situation: rename the local branch to something else; create a new branch with the same (agent-clarity) name and then cherry pick the relevant commit to that branch. Finally, you will need to force push the branch to the remote.

You first want to make sure that your local repository is up-to-date w.r.t the upstream repository. You should first check that you have the w3c/lws-protocol repository listed as a remote:

$ git remote -v

One of the items should include the w3c/lws-protocol repository (not just your own fork). If it is not present, you should add it:

$ git remote add upstream https://github.com/w3c/lws-protocol

Then, update the main branch of your local clone:

$ git checkout main
$ git fetch upstream
$ git pull upstream main

Now, rename the local branch to something else and create a new branch named agent-clarity

$ git checkout -m agent-clarity agent-clarity-old
$ git checkout -b agent-clarity

Now, cherry-pick the relevant commit and force-push

$ git cherry-pick 39eebcec5f624c6f6659e5c404e3c8819ed2cb27
$ git push -f origin agent-clarity

Finally, remove the unused branch

$ git branch -D agent-clarity-old

---

An alternative is to just close this PR and delete your local branch, starting from scratch from main:

$ git pull upstream main
$ git checkout -b new-agent-clarity

Make your changes and then push to origin like normal and open a new PR

$ git add ...
$ git commit -m "... message ..."
$ git push origin new-agent-clarity

---

Generally speaking, be sure that, whenever you begin work, your local fork is up-to-date with respect to the w3c/lws-protocol repository's main branch.

[jeremycaine]

great thanks @acoburn I will do this later today - I think I was on one of my PR branches when I created the new one.