From 8168d76e4f8312a686198ad5014e4f4a9af3732f Mon Sep 17 00:00:00 2001
From: TobiasNx <61879957+TobiasNx@users.noreply.github.com>
Date: Mon, 7 Oct 2024 15:24:24 +0200
Subject: [PATCH] Fix missing `

---
 docs/flux/Flux-User-Guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/flux/Flux-User-Guide.md b/docs/flux/Flux-User-Guide.md
index 3401643..fd57af5 100644
--- a/docs/flux/Flux-User-Guide.md
+++ b/docs/flux/Flux-User-Guide.md
@@ -98,7 +98,7 @@ To learn about the available options of a command, execute Flux without argument
 To some commands the entire environment can be given as an argument. This is done with the `*` character: `fix("tranformation.fix", *)`. In this case Fix gains access to all variable assignments made in Flux.
 (See also [Addressing Pieces of Data: FIX-Path and the record structure in FIX ](../fix/Fix-User-Guide.html#addressing-pieces-of-data-fix-path-and-the-record-structure-in-fix)).
 
-Note that unlike shell pipes, the data flowing between Flux commands is _typed_. This means that only commands with matching signatures can be combined. Commands expect a certain input and provide a certain output like: `StreamReceiver, `Object`, `Reader` and others.
+Note that unlike shell pipes, the data flowing between Flux commands is _typed_. This means that only commands with matching signatures can be combined. Commands expect a certain input and provide a certain output like: `StreamReceiver`, `Object`, `Reader` and others.
 
 To lookup the signatures, again: execute Flux without arguments. It will list all available commands, including signatures. Or simply have a look at the  [list of available FLUX commands in this documentation.](flux-commands.html)