1, 2, and 3 John
- Biblical Studies & Commentaries
- Publisher: Pickwick Publications (Wipf and Stock)
- Published: 2025
FritzSearch.com earns a commission on purchases made through Bookshop.org links.
Publisher's Description
This commentary approaches 1, 2, and 3 John as social discourses and seeks to provide insights into the use of language in these epistles within their situational contexts. The method of discourse analysis employed to analyze the texts and linguistic characteristics in 1-3 John is based on the model of systemic functional linguistics proposed by Michael A. K. Halliday. The interpretative task of this commentary is to analyze the ways in which the author draws on the vast resources of language to convey his ideas to the audience and accomplish his purposes. Despite the adoption of systemic functional linguistics, the use of jargon is avoided in the interpretation of the Johannine Epistles and the commentary does not demand from the reader a mastery of this discourse analysis method. The insights offered will help open up the text of 1-3 John in a fresh way.
Endorsements (2)
“Commentaries on the Johannine Epistles continue to pour from the presses. This latest contribution, from Dr. Mavis Leung, covers the ground found in most commentaries, but does so with an eye focused on the social discourse features of the text. Influenced by the systemic functional linguistics proposed by Michael A. K. Halliday, Leung seeks to enrich her exegesis by drawing attention to the writer’s deployment of language to flesh out the social world he shares with his readers.”
“By utilizing a modern theory of language—Systemic Functional Linguistics—and applying it to the common Greek text of 1, 2, and 3 John in the first century, Mavis Leung guides us on an interesting tour of Greek exegesis that may bring immerse us in the social-cultural formation of the author to the first audience. The author’s hortatory aim to the first audience may find echoes to us in our world of idols and self-affirmative ideologies.”
See something wrong on this page? Report a problem