diff --git a/analyzer-comments/elm/ticket-please/assignTicketTo_ignore_cases.md b/analyzer-comments/elm/ticket-please/assignTicketTo_ignore_cases.md
index c319de2ca..8064e1cb3 100644
--- a/analyzer-comments/elm/ticket-please/assignTicketTo_ignore_cases.md
+++ b/analyzer-comments/elm/ticket-please/assignTicketTo_ignore_cases.md
@@ -1,3 +1,3 @@
 # assignTicketTo ignore cases
 
-When there are several `case` patterns that lead to the same value, like it is the case for the ticket statuses in `assignTicketTo`, it is usual to leave them for last and group them with the wildcard `_`.
+When there are several `case` patterns that lead to the same value, as happens for the ticket statuses in `assignTicketTo`, it is usual to leave them for last and group them with the wildcard `_`.
diff --git a/analyzer-comments/elm/ticket-please/assignTicketTo_use_record_update.md b/analyzer-comments/elm/ticket-please/assignTicketTo_use_record_update.md
index f695924d6..4a9ebb35e 100644
--- a/analyzer-comments/elm/ticket-please/assignTicketTo_use_record_update.md
+++ b/analyzer-comments/elm/ticket-please/assignTicketTo_use_record_update.md
@@ -1,4 +1,4 @@
 # assignTicketTo use record update
 
-Once you pattern matched the record from `Ticket` and named it with `as`, the best way to update it is with the record update syntax.
+Once you pattern matched the record from `Ticket` and named it with `as`, the best way to update it is with the [record update syntax](https://elm-lang.org/docs/records#updating-records).
 Try it out!