Rework software architecture section by Thomas Kiley

_episodes/15-coding-conventions.md

@@ -438,7 +438,7 @@ because an incorrect comment causes more confusion than no comment at all.
 >> which is helpfully marking inconsistencies with coding guidelines by underlying them.
 >> There are a few things to fix in `inflammation-analysis.py`, for example:
 >>
->>  1. Line 24 in `inflammation-analysis.py` is too long and not very readable.
+>>  1. Line 30 in `inflammation-analysis.py` is too long and not very readable.
 >>     A better style would be to use multiple lines and hanging indent,
 >>     with the closing brace `}' aligned either with
 >>     the first non-whitespace character of the last line of list
@@ -487,7 +487,7 @@ because an incorrect comment causes more confusion than no comment at all.
 >>     Note how PyCharm is warning us by underlying the whole line.
 >>
 >>  4. Only one blank line after the end of definition of function `main`
->>     and the rest of the code on line 30 in `inflammation-analysis.py` -
+>>     and the rest of the code on line 33 in `inflammation-analysis.py` -
 >>     should be two blank lines.
 >>     Note how PyCharm is warning us by underlying the whole line.
 >>

_episodes/30-section3-intro.md

@@ -131,15 +131,10 @@ within the context of the typical software development process:
 - How requirements inform and drive the **design of software**,
   the importance, role, and examples of **software architecture**,
   and the ways we can describe a software design.
-- **Implementation choices** in terms of **programming paradigms**,
-  looking at **procedural**, **functional**, and **object oriented** paradigms of development.
-  Modern software will often contain instances of multiple paradigms,
-  so it is worthwhile being familiar with them and knowing when
-  to switch in order to make better code.
-- How you can (and should) assess and update a software's architecture when
-  requirements change and complexity increases -
-  is the architecture still fit for purpose,
-  or are modifications and extensions becoming increasingly difficult to make?
+- How to improve existing code to be more readable, maintainable and testable.
+- Consider different strategies for writing well designed code, including
+  using **pure functions**, **classes** and **abstractions**.
+- How to create, assess and improve software design.
 
 
 {% include links.md %}