Streaming blog post - Laura's review comments

[lauracowen]

• "However, as your application grows, your users need to wait longer for a response from the LLM." - this doesn't quite follow. It's the increase in size of the request to the LLM and/or the response you're expecting from the LLM, surely, that increases response times? Maybe rephrase slightly?

• "in doing so reducing delays and increasing responsiveness." - again just a niggle that streaming reduces "perceived delays" and increases "perceived responsiveness". It doesn't change the actual response times to/from the LLM.

• "how to enable two-way communication between client and server endpoints and how to stream tokens from your LLM to your application client UI with Jakarta WebSocket." - at this stage, I think it's worth not saying "tokens" and just say something like "how to stream responses from your LLM". Also, not sure of the relevance of "two-way communication between client and server endpoints" at this point, based on what you've said already and the focus of the post seems to be on the LLM bit. So would it make sense to just say "how to stream responses from your LLM to your application client UI with Jakarta WebSocket."? That you do client/server communication kind of goes without saying if you're using WebSocket (I think?) but specifying it here feels like a distraction from the overall point of the blog post.

• Other than that though, I like the intro - it's to-the-point and clear. :)

• "You can use the IBM Semeru Runtime" - the product name should be plural, and also remove "the" to say "You can use IBM Semeru Runtimes"

• "choose either of them" -> "choose any of them" (as there are more than two choices)

• Rephrase the last bit of the prereqs sentence because it's not quite grammatical. Something like: "...them. Set up the AI provider by following..."

  • You could shorten the last bit to "Prerequisits and Environment Setup instructions".

How to set up streaming chat? section (and in fact all the subsequent sections)

• I think this should use the style we use in the guides. It's confusing to follow what's happening at the moment.
  • The first sentence sounds like an instruction rather than an introduction to what is in this section.
  • Then telling the reader to see the respective Java files before showing the code snippet is a bit confusing because it's not clear if that snippet is what's in the file (without looking).
• "OpenLiberty" should be "Open Liberty" (always two words).

Could you ask Morgan @shin19991207 to review, please, and to help re-jig the info in the how-to sections? I think the info is probably all there, it's just the ordering.

Then there needs to be some kind of conclusion paragraph/section that reaffirms what the user has achieved in completing the tutorial in this blog post.

In the Where Next section, give them something more specific to look at than just all the guides. Pick a relevant one that would be useful to do next to learn more, eg about websockets.