From 301a20a1768c7d0eb64485c29eb84fc2d67697bd Mon Sep 17 00:00:00 2001
From: Andras Varga <andras@omnetpp.org>
Date: Sat, 18 May 2024 14:29:00 +0200
Subject: [PATCH] posts proofread using llm

---
 _posts/2010-08-05-BGPv4-added.md              |   9 +-
 _posts/2010-08-16-Website-Redesign.md         |   3 +-
 _posts/2010-08-18-blog.md                     |  10 +-
 _posts/2011-02-25-INET-20110225-released.md   |   4 +-
 _posts/2011-03-03-INET-1.99.0-released.md     |   4 +-
 _posts/2011-05-27-INET-1.99.1-released.md     |   6 +-
 _posts/2011-06-11-blog.md                     |   3 +-
 ...11-18-INET-20111118-and-1.99.2-released.md |   1 -
 _posts/2012-02-24-INET-1.99.3-released.md     |   4 +-
 _posts/2012-03-21-INET-1.99.4-released.md     |   8 +-
 _posts/2012-04-02-blog.md                     |   5 +-
 _posts/2012-06-22-INET-1.99.5-released.md     |   7 +-
 _posts/2012-08-07-INET-2.2.0-released.md      |  31 ++--
 _posts/2013-02-01-INET-2.1.0-released.md      |  12 +-
 _posts/2013-08-23-INET-2.2.0-released.md      |  15 +-
 _posts/2014-03-27-INET-2.3.0-released.md      |  63 ++++---
 _posts/2014-06-12-INET-2.4.0-released.md      |  13 +-
 _posts/2014-10-30-INET-2.5.0-released.md      |   3 +-
 _posts/2014-11-10-INET-2.99.0-released.md     |  15 +-
 _posts/2014-11-14-Mailinglist-Change.md       |   4 +-
 _posts/2014-12-09-blog.md                     |   2 +-
 _posts/2015-01-26-blog.md                     |   4 +-
 _posts/2015-03-05-INET-2.6.0-released.md      |   3 +-
 _posts/2015-05-13-INET-2.99.1-released.md     |  44 ++---
 _posts/2015-06-24-INET-3.0.0-released.md      |  55 +++---
 _posts/2015-06-25-blog.md                     |   4 +-
 _posts/2015-10-26-INET-3.1.0-released.md      |   3 +-
 _posts/2015-12-17-INET-3.2.0-released.md      |   3 +-
 _posts/2016-01-22-INET-3.2.1-released.md      |  12 +-
 _posts/2016-03-16-INET-3.2.3-released.md      |   5 +-
 _posts/2016-04-06-INET-3.2.4-released.md      |   7 +-
 _posts/2016-06-03-INET-3.3.0-released.md      |   3 +-
 _posts/2016-06-03-blog.md                     |  13 +-
 _posts/2016-06-17-INET-3.4.0-released.md      |  30 +--
 _posts/2017-02-22-INET-3.5.0-released.md      |   7 +-
 _posts/2017-06-14-INET-3.6.0-released.md      |  66 +++----
 .../2017-08-23-initial-showcases-released.md  |  19 +-
 _posts/2017-08-24-INET-3.99.0-released.md     | 174 +++++++++---------
 ...9-15-ipv4configurator-tutorial-released.md |   7 +-
 _posts/2017-10-02-INET-3.6.2-released.md      |  14 +-
 _posts/2017-10-06-two-showcases-released.md   |   8 +-
 _posts/2017-10-11-three-showcases-released.md |   9 +-
 _posts/2017-11-17-INET-3.99.1-released.md     |  38 ++--
 _posts/2017-12-22-INET-3.6.3-released.md      |   8 +-
 _posts/2017-12-22-INET-3.99.2-released.md     |   2 +-
 _posts/2018-03-22-INET-3.6.4-released.md      |  11 +-
 _posts/2018-04-13-INET-3.99.3-released.md     |  28 +--
 _posts/2018-06-28-INET-4.0.0-released.md      |  44 ++---
 _posts/2018-07-19-showcases-released.md       |   8 +-
 _posts/2018-07-20-showcases-released.md       |   7 +-
 _posts/2018-07-27-showcases-released.md       |   3 +-
 _posts/2018-07-30-showcases-released.md       |   3 +-
 _posts/2018-08-17-showcases-released.md       |   3 +-
 _posts/2018-09-13-showcases-released.md       |   5 +-
 _posts/2018-10-04-showcases-released.md       |   2 +-
 _posts/2018-10-12-showcases-released.md       |   8 +-
 _posts/2018-11-19-showcases-released.md       |   3 +-
 _posts/2019-01-29-INET-4.1.0-released.md      |  64 +++----
 _posts/2019-03-22-showcases-released.md       |   3 +-
 _posts/2019-04-01-showcases-released.md       |   3 +-
 _posts/2019-04-18-INET-3.6.5-released.md      |   3 +-
 _posts/2019-07-10-showcases-released.md       |   1 -
 _posts/2019-11-15-showcases-released.md       |   1 -
 _posts/2020-01-08-INET-4.2.0-released.md      |  24 +--
 _posts/2020-03-26-showcases-released.md       |   3 +-
 _posts/2020-03-26-showcases-released2.md      |   4 +-
 _posts/2021-01-06-INET-3.7.0-released.md      |  15 +-
 _posts/2021-01-11-INET-4.2.2-released.md      |   3 +-
 _posts/2021-01-13-INET-4.3.0-released.md      |   2 +-
 _posts/2021-01-13-blog.md                     |   2 +-
 _posts/2021-04-07-INET-4.3.1-released.md      |   2 +-
 _posts/2021-05-18-INET-4.3.2-released.md      |   3 +-
 _posts/2021-09-01-INET-4.3.3-released.md      |   4 +-
 _posts/2021-10-15-INET-4.3.4-released.md      |  12 +-
 _posts/2021-11-15-INET-4.3.5-released.md      |  13 +-
 _posts/2022-02-08-INET-4.3.7-released.md      |  13 +-
 _posts/2022-04-29-INET-4.3.9-released.md      |   9 +-
 _posts/2022-05-16-INET-4.4.0-released.md      |   8 +-
 _posts/2022-06-15-tsn-released.md             |   1 +
 _posts/2022-07-27-INET-4.4.1-released.md      |   7 +-
 _posts/2023-04-04-INET-4.5.0-released.md      |   9 +-
 _posts/2023-08-25-INET-4.5.1-released.md      |   4 +-
 _posts/2023-08-29-INET-4.5.2-released.md      |   6 +-
 83 files changed, 517 insertions(+), 587 deletions(-)

diff --git a/_posts/2010-08-05-BGPv4-added.md b/_posts/2010-08-05-BGPv4-added.md
index 5164f48..fba8e8e 100644
--- a/_posts/2010-08-05-BGPv4-added.md
+++ b/_posts/2010-08-05-BGPv4-added.md
@@ -1,12 +1,9 @@
 ---
 layout: post
 title: BGPv4 Model Contributed to INET
-category: news
----
+category: news---
 
 Helene Lageber has contributed a BGPv4 model to the INET Framework. The
-code is now available in the *topic/bgpv4* branch of the INET repo; it will
+code is now available in the *topic/bgpv4* branch of the INET repository. It will
 be integrated into the INET *master* branch after some refinements and
-testing.
-
-
+testing.
\ No newline at end of file
diff --git a/_posts/2010-08-16-Website-Redesign.md b/_posts/2010-08-16-Website-Redesign.md
index 7fce8a1..5a472dd 100644
--- a/_posts/2010-08-16-Website-Redesign.md
+++ b/_posts/2010-08-16-Website-Redesign.md
@@ -2,6 +2,7 @@
 layout: post
 title: INET Web Site Redesigned
 category: news
+
 ---
 
-The INET Framework's web site has received a face lift.
+The INET Framework's website has received a facelift.
\ No newline at end of file
diff --git a/_posts/2010-08-18-blog.md b/_posts/2010-08-18-blog.md
index d5d871f..b402daf 100644
--- a/_posts/2010-08-18-blog.md
+++ b/_posts/2010-08-18-blog.md
@@ -7,13 +7,13 @@ category: progress
 The following topic branches are currently open in the INET repository:
 
 *   `topic/bgpv4` -- recently contributed BGP protocol (mostly done)
-*   `topic/ethernet` -- changing Ethernet to use channel datarate instead of parameter (mostly done)
+*   `topic/ethernet` -- changing Ethernet to use channel datarate instead of a parameter (mostly done)
 *   `topic/ospfrenaming` -- OSPF model code style fixes (mostly done)
 *   `topic/signals` -- signals-based result recording instead of cOutVector/recordScalar (halfway)
-*   `topic/PcapTrace` -- capturing and recording PCAP traces via GUI
-*   `topic/tcp_lwip` -- lwIP integration as alternative TCP (mostly done)
-*   `topic/tcp_socket_read` -- application-level flow control in TCP (in work)
+*   `topic/PcapTrace` -- capturing and recording PCAP traces via the GUI
+*   `topic/tcp_lwip` -- lwIP integration as an alternative TCP (mostly done)
+*   `topic/tcp_socket_read` -- application-level flow control in TCP (in progress)
 *   `topic/tcptransfermode` -- refactoring of TCP send/recvQueueClass to a transferMode parameter (halfway)
 *   `topic/wizards` -- wizards to generate wireless and other networks (halfway)
 
-The plan is to have these branches finished, reviewed, and merged into master over the next few months.
+The plan is to have these branches finished, reviewed, and merged into the master over the next few months.
\ No newline at end of file
diff --git a/_posts/2011-02-25-INET-20110225-released.md b/_posts/2011-02-25-INET-20110225-released.md
index 3943343..80f1af5 100644
--- a/_posts/2011-02-25-INET-20110225-released.md
+++ b/_posts/2011-02-25-INET-20110225-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-20110225 Released
 category: news
----
 
 We are happy to announce a new release of the INET Framework,
 INET-20110225. This release contains `#include` fixes needed for INET to
@@ -10,5 +9,4 @@ compile with OMNeT++ 4.2b1. (If you have your own copy or fork of INET, apply
 [this](https://github.com/inet-framework/inet/commit/869de7139b3bc5cd43443a3fe978c5fec42fe331) and
 [this](https://github.com/inet-framework/inet/commit/c86b8e5bd6e38eabcb677117e27afb7295db422f) patch.)
 Other changes in this INET release include SCTP fixes and additional SCTP statistics by Alberto Cortes.
-[Download](https://github.com/inet-framework/inet/releases/download/master_20110225/inet-20110225-src.tgz)
-
+[Download](https://github.com/inet-framework/inet/releases/download/master_20110225/inet-20110225-src.tgz)
\ No newline at end of file
diff --git a/_posts/2011-03-03-INET-1.99.0-released.md b/_posts/2011-03-03-INET-1.99.0-released.md
index 5c8acea..4f8ab53 100644
--- a/_posts/2011-03-03-INET-1.99.0-released.md
+++ b/_posts/2011-03-03-INET-1.99.0-released.md
@@ -4,6 +4,4 @@ title: Development Snapshot INET-1.99.0
 category: news
 ---
 
-This release is a snapshot of work in progress, please do not use it for
-research. The source is available from the [download page](/Download.html).
-
+This release is a snapshot of the work in progress. Please do not use it for research. The source is available from the [download page](/Download.html).
\ No newline at end of file
diff --git a/_posts/2011-05-27-INET-1.99.1-released.md b/_posts/2011-05-27-INET-1.99.1-released.md
index 50a860e..4ec6a27 100644
--- a/_posts/2011-05-27-INET-1.99.1-released.md
+++ b/_posts/2011-05-27-INET-1.99.1-released.md
@@ -2,10 +2,6 @@
 layout: post
 title: Development Snapshot INET-1.99.1
 category: news
----
 
-Work on INET is progressing fast. The 1.99.x snapshots represent the
-consolidation of the INET codebase as well as integrating various external
-INET extensions created by the community, and will eventually result in a
-2.0 stable release. Download the source [here](/Download.html).
+Work on INET is progressing quickly. The 1.99.x snapshots represent the consolidation of the INET codebase as well as the integration of various external INET extensions created by the community, and will eventually result in a stable 2.0 release. You can download the source [here](/Download.html).
 
diff --git a/_posts/2011-06-11-blog.md b/_posts/2011-06-11-blog.md
index f3939b4..999b852 100644
--- a/_posts/2011-06-11-blog.md
+++ b/_posts/2011-06-11-blog.md
@@ -8,5 +8,4 @@ For the last six months or so, development has taken place in the **master** bra
 
 To see what's been done, check the WHATSNEW file in the repository, or browse the commits directly.
 
-Short-term plans include the integration of the 802.15.4 model from INETMANET, HttpTools and MiXiM.
-
+Short-term plans include the integration of the 802.15.4 model from INETMANET, HttpTools, and MiXiM.
\ No newline at end of file
diff --git a/_posts/2011-11-18-INET-20111118-and-1.99.2-released.md b/_posts/2011-11-18-INET-20111118-and-1.99.2-released.md
index 4c0e9d1..e852197 100644
--- a/_posts/2011-11-18-INET-20111118-and-1.99.2-released.md
+++ b/_posts/2011-11-18-INET-20111118-and-1.99.2-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: "New INET Releases: INET-20111118 (stable), INET-1.99.2 (development)"
 category: news
----
 
 INET-20111118 is an update of the previous stable INET version to the
 just-released OMNeT++ 4.2, with a few bug fixes. The other download,
diff --git a/_posts/2012-02-24-INET-1.99.3-released.md b/_posts/2012-02-24-INET-1.99.3-released.md
index 65be2d0..9230b79 100644
--- a/_posts/2012-02-24-INET-1.99.3-released.md
+++ b/_posts/2012-02-24-INET-1.99.3-released.md
@@ -2,9 +2,7 @@
 layout: post
 title: "New INET Development Release: INET-1.99.3"
 category: news
----
 
-We have just released a new version from the development branch of INET.
+We have just released a new version of the development branch of INET.
 You can download INET-1.99.3 [here](/Download.html), or read what's new in this version
 [here](https://github.com/inet-framework/inet/blob/integration_1.99.3/WHATSNEW).
-
diff --git a/_posts/2012-03-21-INET-1.99.4-released.md b/_posts/2012-03-21-INET-1.99.4-released.md
index e4e2447..470960c 100644
--- a/_posts/2012-03-21-INET-1.99.4-released.md
+++ b/_posts/2012-03-21-INET-1.99.4-released.md
@@ -1,11 +1,9 @@
 ---
 layout: post
 title: "New INET Development Release: INET-1.99.4"
-category: news
----
+category: news---
 
 We have just released a new version from the development branch of INET. It
-contains some features that did not make into the previous version. You can
+contains some features that did not make it into the previous version. You can
 download INET-1.99.4 [here](/Download.html), or read what's new in this version
-[here](https://github.com/inet-framework/inet/blob/integration_1.99.4/WHATSNEW).
-
+[here](https://github.com/inet-framework/inet/blob/integration_1.99.4/WHATSNEW).
\ No newline at end of file
diff --git a/_posts/2012-04-02-blog.md b/_posts/2012-04-02-blog.md
index 3ca46dd..113df14 100644
--- a/_posts/2012-04-02-blog.md
+++ b/_posts/2012-04-02-blog.md
@@ -6,10 +6,9 @@ category: progress
 
 Now that INET-1.99.4 has been released, we are currently concentrating on code and protocol reviews.
 
-Additional short term plans:
+Additional short-term plans:
 
 *   Implement DiffServ.
 *   Merge/integrate the MiXiM project with INET.
 *   Implement Node failure/recovery support.
-*   Implement IPv6NetworkConfigurator (should work like the current IPv4NetworkConfigurator).
-
+*   Implement IPv6NetworkConfigurator (should work like the current IPv4NetworkConfigurator).
\ No newline at end of file
diff --git a/_posts/2012-06-22-INET-1.99.5-released.md b/_posts/2012-06-22-INET-1.99.5-released.md
index 164e1bc..40a8aa6 100644
--- a/_posts/2012-06-22-INET-1.99.5-released.md
+++ b/_posts/2012-06-22-INET-1.99.5-released.md
@@ -2,10 +2,5 @@
 layout: post
 title: "New INET Development Release: INET-1.99.5"
 category: news
----
-
-We have just released the last 1.99.x version for the development branch of
-INET. Highlights of this release are a new DiffServ framework and the
-overhaul of the OSPFv2 model. You can download INET-1.99.5 [here](/Download.html), or
-read what's new in this version [here](https://github.com/inet-framework/inet/blob/integration_1.99.5/WHATSNEW).
 
+We have just released the latest 1.99.x version for the development branch of INET. The main highlights of this release include a new DiffServ framework and the complete overhaul of the OSPFv2 model. You can download INET-1.99.5 [here](/Download.html), or read about the new features and changes in this version [here](https://github.com/inet-framework/inet/blob/integration_1.99.5/WHATSNEW).
\ No newline at end of file
diff --git a/_posts/2012-08-07-INET-2.2.0-released.md b/_posts/2012-08-07-INET-2.2.0-released.md
index 1444e5f..70d5230 100644
--- a/_posts/2012-08-07-INET-2.2.0-released.md
+++ b/_posts/2012-08-07-INET-2.2.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-2.0.0 Stable Release Available
 category: news
----
 
 We are happy to announce the INET Framework 2.0.0 release. The INET
 Framework is an open-source communication networks simulation package for
@@ -18,38 +17,38 @@ New features:
 *   Result recording has been ported to use the new signal-based statistics collection framework; this allows better separation of the model and the statistic collection code.
 *   New Differentiated Services framework for QoS simulations.
 *   New IPv4NetworkConfigurator for more powerful configuration of IP networks.
-*   New protocols: DHCP, BGPv4; interated xMIPv6 (mobile IPv6).
+*   New protocols: DHCP, BGPv4; integrated xMIPv6 (mobile IPv6).
 *   New MANET routing protocols (from INETMANET): AODV, DSR, BATMAN, DYMO, OLSR
 *   New PcapRecorder module for capturing traffic traces.
 *   New VoIP application that allows sending an actual voice stream over the network.
 *   Integrated HttpTools for simulating HTTP-based applications.
 *   New mobility modules including TraCI (taken over from the Veins project)
 *   Added an LwIP-based TCP implementation.
-*   Writing a manual for INET has been started and already made a great progress.
+*   Writing a manual for INET has been started and already made great progress.
 
 Improvements:
 
 *   Node models refactored for better extensibility (StandardHost, AdhocHost, WirelessHost, Router).
-    *   Different types of TCP, UDP and SCTP applications can co-exist in the same host.
-    *   Alternate UDP and TCP implementation can be plugged-in. Three independent TCP implementations are available (OMNeT++ native, LwIP, NSC)
-    *   Inside a host, submodules are instantiated only if they are actually required.
-    *   Configurable hooks have been added in the network layer to allow packet drop/duplication scenarios.
-    *   Routers now support an unlimited number of wireless, Ethernet, point-to-point and external interfaces.
-    *   Mobility support in Router and StandardHost is now optional.
-    *   AccessPoints now have both wireless and Ethernet interfaces (bridged).
+*   Different types of TCP, UDP, and SCTP applications can co-exist on the same host.
+*   Alternate UDP and TCP implementations can be plugged-in. Three independent TCP implementations are available (OMNeT++ native, LwIP, NSC)
+*   Inside a host, submodules are instantiated only if they are actually required.
+*   Configurable hooks have been added in the network layer to allow packet drop/duplication scenarios.
+*   Routers now support an unlimited number of wireless, Ethernet, point-to-point, and external interfaces.
+*   Mobility support in Router and StandardHost is now optional.
+*   AccessPoints now have both wireless and Ethernet interfaces (bridged).
 *   Revised OSPFv2 model.
 *   TCP: Transmission mode (byte count, object and byte stream) is now specified by the application.
-*   UDP: multicast, broadcast and TTL support. Improved socket API.
-*   IPv6: implemented default router selection, tunneling and datagram fragmentation/reassembly for PPP links.
+*   UDP: multicast, broadcast, and TTL support. Improved socket API.
+*   IPv6: implemented default router selection, tunneling, and datagram fragmentation/reassembly for PPP links.
 *   IPv4: reimplemented multicast routing
 *   Ethernet: EtherMAC refactored for better readability; added reconnect support, better PAUSE support, support for 40 and 100 Gigabit Ethernet.
-*   Ethernet datarate is now configured on the channels (not in the MAC). Also added new Ethernet channel types: Eth10M, Eth100M, Eth1G, Eth10G, Eth40G and Eth100G
+*   Ethernet datarate is now configured on the channels (not in the MAC). Also added new Ethernet channel types: Eth10M, Eth100M, Eth1G, Eth10G, Eth40G, and Eth100G
 *   IEEE802.11 a/b/g/s model: Unified several implementations into a single MAC module.
 *   Multiple radio support for wireless hosts; radio infrastructure has been refactored.
-*   Refactoring: Mobility support is now completely independent of the radio infrastructure and it is compatible with the MiXiM mobility modules.
-*   A comprehensive test suite has be devised, and deployed in a continuous testing environment (Jenkins).
+*   Refactoring: Mobility support is now completely independent of the radio infrastructure and is compatible with the MiXiM mobility modules.
+*   A comprehensive test suite has been devised and deployed in a continuous testing environment (Jenkins).
 *   A large number of bug fixes and other improvements.
 
 You can find the detailed change log [here](https://github.com/inet-framework/inet/blob/v2.0.0/WHATSNEW).
 
-You can download INET-2.0.0 [here](/Download.html).
+You can download INET-2.0.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2013-02-01-INET-2.1.0-released.md b/_posts/2013-02-01-INET-2.1.0-released.md
index 2c275ae..f49e557 100644
--- a/_posts/2013-02-01-INET-2.1.0-released.md
+++ b/_posts/2013-02-01-INET-2.1.0-released.md
@@ -10,7 +10,7 @@ OMNeT++ 4.2 or 4.3.
 
 NEW:
 
-*   Added a new module to model an "internet cloud". The component can be configured to model packet delay, datarate and drop probability between each input-output interface pair. The parameter matrix is provided as an XML configuration file. See the README file in src/nodes/internetcloud for further details.
+*   Added a new module to model an "internet cloud". The component can be configured to model packet delay, data rate and drop probability between each input-output interface pair. The parameter matrix is provided as an XML configuration file. See the README file in src/nodes/internetcloud for further details.
 *   New SimpleVoIPReceiver/Sender applications that gather MOS (Mean Opinion Score) for measuring voice quality.
 *   Added HNA support to the Batman protocol (MANET)
 
@@ -55,7 +55,7 @@ Manetrouting:
 AODV:
 
 *   AODV's hand-written descriptors were replaced with generated ones.
-*   aodv\_msg\_struct.h: added getter methods expected by the generated descriptors removed hand-written aodv\_msg\_struct_descriptor.cc
+*   aodv_msg_struct.h: added getter methods expected by the generated descriptors removed hand-written aodv_msg_struct_descriptor.cc
 
 Batman:
 
@@ -65,21 +65,21 @@ Batman:
 *   Fixed several memory leaks
 *   Fixed routing table corruption and possible crash when multiple radios were used in a single host
 *   Fixed decapsulation of incoming packets. Now it checks for the type of decapsulated packet.
-*   Fix for a problem when aggregated batman packets were dropped erronously.
+*   Fix for a problem when aggregated batman packets were dropped erroneously.
 *   Added HNA support. Nodes can advertise external networks, so traffic towards those networks can be routed correctly. Use the announcedNetworks parameter to specify multiple connected external networks.
 *   Added SourceModifier script to help the conversion from the original batmand code.
     *   fixes spaces, tabs and empty lines
     *   replaces some c-style structs to c++-style classes
     *   replaces some batmand specified list manipulators with c++ code
     *   replaces malloc/free with new/delete
-    *   removes prof\_start()/prof\_stop() calls
+    *   removes prof_start()/prof_stop() calls
 
 Examples:
 
 *   Added a new simulation with wired and wireless hosts exchanging UDP data via an AccessPoint. It shows how to use the IPv4NetworkConfigurator to mix wired and wireless networks.
 *   Fixes for BGP examples.
 *   New example to demonstrate HNA support in Batman.
-*   Hostautoconf examample moved to the adhoc folder.
+*   Hostautoconf example moved to the adhoc folder.
 
 Other changes:
 
@@ -95,4 +95,4 @@ Other changes:
 *   Pcap now records on ALL interfaces by default (including external IFs). Added Enter_Method for better error reporting if a packet cannot be serialized. Also added an icon for PcapRecorder.
 *   Several TCP related fixes.
 
-You can download INET-2.1.0 [here](/Download.html).
+You can download INET-2.1.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2013-08-23-INET-2.2.0-released.md b/_posts/2013-08-23-INET-2.2.0-released.md
index 86f6930..8323799 100644
--- a/_posts/2013-08-23-INET-2.2.0-released.md
+++ b/_posts/2013-08-23-INET-2.2.0-released.md
@@ -2,30 +2,29 @@
 layout: post
 title: INET-2.2.0 Stable Release Available
 category: news
----
 
 We are happy to announce the latest stable version of the INET Framework. This version requires OMNeT++ 4.2 or 4.3.
 
 New features:
 
-*   Simulating shutdown, crash, reboot and similar events for network nodes. This is made possible by a new mechanism called lifecycle infrastructure. For node shutdown/crash/startup/etc, a LifecycleOperation (e.g. NodeShutdownOperation) is applied to the submodule tree of the network node (host or router) by a LifecycleController module. Each module can decide how to handle the operation and how to store the resulting state (up/down,etc). Operations can be multi-stage, and don't need to complete immediately (i.e. they can take nonzero simulation time and multiple events to complete).
+*   Simulating shutdown, crash, reboot, and similar events for network nodes. This is made possible by a new mechanism called lifecycle infrastructure. For node shutdown/crash/startup/etc, a LifecycleOperation (e.g., NodeShutdownOperation) is applied to the submodule tree of the network node (host or router) by a LifecycleController module. Each module can decide how to handle the operation and how to store the resulting state (up/down, etc). Operations can be multi-stage and don't need to complete immediately (i.e., they can take nonzero simulation time and multiple events to complete).
 
-*   Static IP4 configuration: A new module, IPv4NodeConfigurator was added to IPv4NetworkLayer. This module is necessary because IPv4NetworkConfigurator cannot configure the node after a restart (see newly introduced node lifecycle operations above), since being a global module, it doesn't know about node lifecycle events. The new module listens to node lifecycle events, and configures the node's routing table and interfaces according to configuration computed by the network's global IPv4NetworkConfigurator module. Initialization-time node configuration is also carried out by the new module.
+*   Static IPv4 configuration: A new module, IPv4NodeConfigurator, was added to IPv4NetworkLayer. This module is necessary because IPv4NetworkConfigurator cannot configure the node after a restart (see newly introduced node lifecycle operations above), since being a global module, it doesn't know about node lifecycle events. The new module listens to node lifecycle events and configures the node's routing table and interfaces according to the configuration computed by the network's global IPv4NetworkConfigurator module. Initialization-time node configuration is also carried out by the new module.
 
 *   New TCP congestion control algorithms: TCP Vegas, TCP Westwood
 
-*   Added IdealWirelessNic (IdealRadio + IdealWirelessMac). This is a highly abstracted wireless NIC that consists of a unit disk radio and a trivial MAC protocol. It offers simplicity for scenarios where Layer 1 and Layer 2 effects can be completely ignored, for example testing the basic functionality of a wireless ad-hoc routing protocol.
+*   Added IdealWirelessNic (IdealRadio + IdealWirelessMac). This is a highly abstracted wireless NIC that consists of a unit disk radio and a trivial MAC protocol. It offers simplicity for scenarios where Layer 1 and Layer 2 effects can be completely ignored, for example, testing the basic functionality of a wireless ad-hoc routing protocol.
 
 *   SCTP received several new features: new strategies for SCTP stream scheduling; SCTP Stream Reset (RFC 6525); SCTP Authentication (RFC 4895); Add-IP feature for SCTP (RFC 5061); NR_SACK feature to SCTP; Partial Reliability SCTP (RFC 3758); SCTP packet drop feature (draft-stewart-sctp-pktdrprep-15.txt); SCTP "sack immediately" feature (draft-ietf-tsvwg-sctp-sack-immediately); several alternatives to send fast retransmissions on SCTP
 
 *   Loopback interface module added. Loopback used to be a special case inside the IPv4/IPv6 modules, now it is handled completely like any other interface, with a separate Loopback module.
 
-*   EtherSwitch, AccessPoint: Bare EtherMAC modules have been replaced with EthernetInterface, so that external queues can be used (useful for e.g. QoS).
+*   EtherSwitch, AccessPoint: Bare EtherMAC modules have been replaced with EthernetInterface so that external queues can be used (useful for e.g., QoS).
 
-*   InterfaceTable, NIC, NetworkLayer: Revert to earlier behavior of determining networkLayerGateIndex. Now the module connected to a NIC must have gate vectors called ifIn and ifOut. If it doesn't, the code decides that the NIC is not directly connected to a network layer, and leaves networkLayerGateIndex unfilled.
+*   InterfaceTable, NIC, NetworkLayer: Revert to earlier behavior of determining the networkLayerGateIndex. Now the module connected to a NIC must have gate vectors called ifIn and ifOut. If it doesn't, the code decides that the NIC is not directly connected to a network layer and leaves networkLayerGateIndex unfilled.
 
-*   In addition, there were several bugfixes and smaller improvements
+*   In addition, there were several bug fixes and smaller improvements.
 
 See the WHATSNEW and per-directory ChangeLog files for further details.
 
-You can download INET-2.2.0 [here](/Download.html).
+You can download INET-2.2.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2014-03-27-INET-2.3.0-released.md b/_posts/2014-03-27-INET-2.3.0-released.md
index f0787f1..9009cea 100644
--- a/_posts/2014-03-27-INET-2.3.0-released.md
+++ b/_posts/2014-03-27-INET-2.3.0-released.md
@@ -2,67 +2,66 @@
 layout: post
 title: INET-2.3.0 Stable Release Available
 category: news
----
 
 We are happy to announce the latest stable version of the INET Framework. This version requires OMNeT++ 4.3 or 4.4.
 
-This release contains several new protocols, and a lot of changes that were backported from the current integration branch (destined to be INET 3.0).
+This release contains several new protocols and a lot of changes that were backported from the current integration branch (destined to be INET 3.0).
 
 Application startTime/stopTime fixes:
 
-*   apps start sending at startTime, and send their last packet before stopTime
-*   negative stopTime means sending forever
-*   if startTime and stopTime are the same, the app sends a single packet only (except TCP apps)
+- apps start sending at startTime and send their last packet before stopTime
+- negative stopTime means sending forever
+- if startTime and stopTime are the same, the app sends a single packet only (except TCP apps)
 
 DHCPServer and Client:
 
-*   The whole implementation has been reviewed to bring it closer to the standards defined in RFC 2131 and 2132.
-*   Major changes were made both in client's and server's state machines. It is now extended with new states (INIT-REBOOT, REBOOTING) and with new message types (DHCPNAK, DHCPDECLINE). The new states allow the user to model scenarios with lifecycle events.
-*   The server's performance model has been removed.
-*   The internal representation of the DHCP options were moved to the DHCPOptions INET message definition file.
-*   Limitation: The client module currently does not support multiple DHCP servers and BOOTP relay agents.
+- The whole implementation has been reviewed to bring it closer to the standards defined in RFC 2131 and 2132.
+- Major changes were made in both the client's and server's state machines. It is now extended with new states (INIT-REBOOT, REBOOTING) and with new message types (DHCPNAK, DHCPDECLINE). The new states allow the user to model scenarios with lifecycle events.
+- The server's performance model has been removed.
+- The internal representation of the DHCP options has been moved to the DHCPOptions INET message definition file.
+- Limitation: The client module currently does not support multiple DHCP servers and BOOTP relay agents.
 
 SCTP improvements submitted by Irene Rungeler and Thomas Dreibholz:
 
-*   added CMT support (Concurrent Multipath Transfer)
-*   added SCTP NAT support
-*   added support for using SCTP over IPv6
+- added CMT support (Concurrent Multipath Transfer)
+- added SCTP NAT support
+- added support for using SCTP over IPv6
 
 STP / RSTP support (802.1d) added to the EthernetSwitch:
 
-*   STP: added IEEE 802.1D-1998 implementation of Spanning Tree Protocol. The source code is based on the ANSA (<https://github.com/kvetak/ANSA>) implementation.
-*   RSTP: added IEEE 802.1D-2004 implementation of Spanning Tree Protocol. The source code is based on Juan Luis Garrote Molinero's implementation from INETMANET.
-*   Interfaces can be configured using the new L2NetworkConfigurator module. This module allows one to configure network scenarios at Layer 2.
-*   Replaced the EtherSwitch relay unit with a new, STP/RSTP capable one. The CPU and memory modelling are no longer supported in this relay unit.
+- STP: added IEEE 802.1D-1998 implementation of Spanning Tree Protocol. The source code is based on the ANSA (<https://github.com/kvetak/ANSA>) implementation.
+- RSTP: added IEEE 802.1D-2004 implementation of Spanning Tree Protocol. The source code is based on Juan Luis Garrote Molinero's implementation from INETMANET.
+- Interfaces can be configured using the new L2NetworkConfigurator module. This module allows one to configure network scenarios at Layer 2.
+- Replaced the EtherSwitch relay unit with a new, STP/RSTP capable one. The CPU and memory modeling are no longer supported in this relay unit.
 
-Nodes automatically pick-up the network configuration on restart:
+Nodes automatically pick up the network configuration on restart:
 
-*   An IPv4NodeConfigurator module has been added to hosts, which is responsible for configuring the host on restart based on information stored in the IPv4NetworkConfigurator module.
+- An IPv4NodeConfigurator module has been added to hosts, which is responsible for configuring the host on restart based on the information stored in the IPv4NetworkConfigurator module.
 
 INetFilter::IHook API:
 
-*   Modules can now hook into the IP module with the new 'NetFilter' API. Routing protocols can be implemented now without modifying the IP module's code. ManetRoutingBase, InternetCloud and ARP have been updated to use the new 'NetFilter' API.
+- Modules can now hook into the IP module with the new 'NetFilter' API. Routing protocols can be implemented now without modifying the IP module's code. ManetRoutingBase, InternetCloud, and ARP have been updated to use the new 'NetFilter' API.
 
 Added new routing protocols:
 
-*   RIP (networklayer/routing/rip)
-*   GPSR (networklayer/routing/gpsr)
-*   DYMO (networklayer/routing/dymo)
+- RIP (networklayer/routing/rip)
+- GPSR (networklayer/routing/gpsr)
+- DYMO (networklayer/routing/dymo)
 
-These protocols use INetFilter::IHook, too.
+These protocols use INetFilter::IHook as well.
 
 Revised Mobility code: Split the 'models' directory into multiple directories:
 
-*   contract - specifies the interface of mobility models
-*   common - shared files among mobility models that are not complete mobility models
-*   static - mobility models that actually don't move
-*   single - mobility models controlling only one moving object
-*   group - mobility models controlling multiple interlinked moving objects
+- contract - specifies the interface of mobility models
+- common - shared files among mobility models that are not complete mobility models
+- static - mobility models that actually don't move
+- single - mobility models controlling only one moving object
+- group - mobility models controlling multiple interlinked moving objects
 
 Radio:
 
-*   Added the Stanford University Interim radio propagation model contributed by Konrad Polys and Krzysztof Grochla.
+- Added the Stanford University Interim radio propagation model contributed by Konrad Polys and Krzysztof Grochla.
 
-In addition, there were several bugfixes and smaller improvements See the WHATSNEW and per-directory ChangeLog files for further details.
+In addition, there were several bug fixes and smaller improvements. See the WHATSNEW and per-directory ChangeLog files for further details.
 
-You can download INET-2.3.0 [here](/Download.html).
+You can download INET-2.3.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2014-06-12-INET-2.4.0-released.md b/_posts/2014-06-12-INET-2.4.0-released.md
index 9b21c40..826451b 100644
--- a/_posts/2014-06-12-INET-2.4.0-released.md
+++ b/_posts/2014-06-12-INET-2.4.0-released.md
@@ -2,20 +2,19 @@
 layout: post
 title: INET-2.4.0 Stable Release Available
 category: news
----
 
 We are happy to announce the latest stable version of the INET Framework.
 This version requires OMNeT++ 4.3 or 4.4.
 
 This release contains some smaller fixes:
 
-*   Added support for link break detection in IdealWireless. (using the NF\_LINK\_BREAK signal)
-*   VoIPStream updated to match the latest version of ffmpeg library.
+*   Added support for link break detection in IdealWireless (using the NF\_LINK\_BREAK signal).
+*   VoIPStream updated to match the latest version of the ffmpeg library.
 *   Added packet printers that can dump packet data in OMNeT++ 4.5/Tkenv in the packet trace window.
-*   Fixed non-conformant 802.11 WAITACK timeout computation
+*   Fixed non-conformant 802.11 WAITACK timeout computation.
 
-and a new routing protocol:
+And a new routing protocol:
 
-*   Brand new AODV implementation in network/routing folder (backported from the integration branch).
+*   Brand new AODV implementation in the network/routing folder (backported from the integration branch).
 
-You can download INET-2.4.0 [here](/Download.html).
+You can download INET-2.4.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2014-10-30-INET-2.5.0-released.md b/_posts/2014-10-30-INET-2.5.0-released.md
index 7facf94..aee15f2 100644
--- a/_posts/2014-10-30-INET-2.5.0-released.md
+++ b/_posts/2014-10-30-INET-2.5.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-2.5.0 Stable Release Available
 category: news
----
 
 We are happy to announce the latest stable version of the INET Framework.
 This version requires OMNeT++ 4.6.
@@ -12,4 +11,4 @@ This release contains some smaller fixes:
 *   Compiles with OMNeT++ 4.6 with C++11 compatibility turned on.
 *   added netperfmeter application by Thomas Dreibholz
 
-You can download INET-2.5.0 [here](/Download.html).
+You can download INET-2.5.0 [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2014-11-10-INET-2.99.0-released.md b/_posts/2014-11-10-INET-2.99.0-released.md
index bdea442..62d3b46 100644
--- a/_posts/2014-11-10-INET-2.99.0-released.md
+++ b/_posts/2014-11-10-INET-2.99.0-released.md
@@ -2,28 +2,27 @@
 layout: post
 title: INET-2.99.0 Development Release Available
 category: news
----
 
-This release is a snapshot of the development that has begun in early 2013,
-and will culminate in the release of INET-3.0. The code is work in
+This release is a snapshot of the development that began in early 2013,
+and will culminate in the release of INET-3.0. The code is a work in
 progress, which means all details may still change until 3.0 is reached.
 
 The highlights of this release are:
 
 *   Network layer refactoring that allows higher layer protocols (including
-    routing protocols) to be written in a network protocol agnostic manner.
+    routing protocols) to be written in a network protocol-agnostic manner.
 
 *   A new physical layer model that builds upon the INET and MiXiM physical
-    layers, and brings them to new heights. Design goals were extreme
+    layers and brings them to new heights. Design goals were extreme
     modularity, extensibility, the ability to support (and easily switch
     between) various levels of detail, and the ability to add support for
     exploiting various pieces of parallel hardware.
 
 *   Extensive refactoring aimed at improving code quality. It includes
-    directory restructuring, code formatting, refactoring of init stages and
-    publish-subscribe communication, and more.
+    directory restructuring, code formatting, refactoring of init stages, and
+    publish-subscribe communication, among other improvements.
 
 This version requires OMNeT++ 4.6 or later. Read
 [what's new](https://github.com/inet-framework/inet/blob/v2.99.0/WHATSNEW) and
 [download INET-2.99.0](https://github.com/inet-framework/inet/releases/download/v2.99.0/inet-2.99.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2014-11-14-Mailinglist-Change.md b/_posts/2014-11-14-Mailinglist-Change.md
index 7dbbc84..d05f5ec 100644
--- a/_posts/2014-11-14-Mailinglist-Change.md
+++ b/_posts/2014-11-14-Mailinglist-Change.md
@@ -2,12 +2,10 @@
 layout: post
 title: Mailing List Name Change
 category: news
----
 
 Service Announcement: We have renamed the *inetframework-devel@googlegroups.com*
 mailing list to *inetframework-contrib@googlegroups.com*, to better reflect the
 purpose of the list as a discussion forum for those who contribute to INET. If
 you are already subscribed, you don't need to do anything, except for maybe
 updating your mail filter rules. The mailing list continues to be available
-at the updated web address <https://groups.google.com/forum/#!forum/inetframework-contrib>.
-
+at the updated web address <https://groups.google.com/forum/#!forum/inetframework-contrib>.
\ No newline at end of file
diff --git a/_posts/2014-12-09-blog.md b/_posts/2014-12-09-blog.md
index 318824c..42652f1 100644
--- a/_posts/2014-12-09-blog.md
+++ b/_posts/2014-12-09-blog.md
@@ -11,4 +11,4 @@ What we've been doing since the INET-2.99.0 pre-release:
 *   Set up a Coverity account for detecting defects via static code analysis
 *   Introducing C++11 features in the code (nullptr, auto, in-class member initializers)
 *   Working on the manual
-*   Merged the PIM/IGMPv3 topic branch into integration
+*   Merged the PIM/IGMPv3 topic branch into integration
\ No newline at end of file
diff --git a/_posts/2015-01-26-blog.md b/_posts/2015-01-26-blog.md
index 954c53f..f8bff2e 100644
--- a/_posts/2015-01-26-blog.md
+++ b/_posts/2015-01-26-blog.md
@@ -7,10 +7,10 @@ excerpt: <p>We added a bit/symbol-level physical layer model for the IEEE 802.11
 
 We added a bit/symbol-level physical layer model for the IEEE 802.11 OFDM PHY,
 and a generic APSK model for experimentation. The implementation includes
-forward error correction, scambling, interleaving and modulation. 
+forward error correction, scrambling, interleaving, and modulation. 
 We have also started to run simulations to compare the symbol-level models
 with frame-level simulations for model verification.
 
 We have fixed more than 300 defects found by Coverity, decreasing Defect Density to 0.5/kLoC.
 
-We plan to release 2.99.1 in the next few weeks.
+We plan to release 2.99.1 in the next few weeks.
\ No newline at end of file
diff --git a/_posts/2015-03-05-INET-2.6.0-released.md b/_posts/2015-03-05-INET-2.6.0-released.md
index a5d3f87..812e528 100644
--- a/_posts/2015-03-05-INET-2.6.0-released.md
+++ b/_posts/2015-03-05-INET-2.6.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-2.6.0 Stable Release Available
 category: news
----
 
 We are happy to announce the latest stable version of the INET Framework.
 This version requires OMNeT++ 4.6 or OMNeT++ 5.0b1.
@@ -13,4 +12,4 @@ This version requires OMNeT++ 4.6 or OMNeT++ 5.0b1.
 * fixed an issue with too small initial value of 'ssthreshold' in TCP
 * fixed window scaling in TCP
 
-You can download it from [here](/Download.html).
+You can download it from [here](/Download.html).
\ No newline at end of file
diff --git a/_posts/2015-05-13-INET-2.99.1-released.md b/_posts/2015-05-13-INET-2.99.1-released.md
index abd051a..dfcea5a 100644
--- a/_posts/2015-05-13-INET-2.99.1-released.md
+++ b/_posts/2015-05-13-INET-2.99.1-released.md
@@ -2,49 +2,33 @@
 layout: post
 title: INET-2.99.1 Development Release Available
 category: news
----
 
-This release is the second snapshot of the development that has begun in 
-early 2013, and will culminate in the release of INET-3.0. The code is 
-now fairly stable and we do not expect major changes before 3.0.
+This release is the second snapshot of the development that has begun in early 2013, and will culminate in the release of INET-3.0. The code is now fairly stable and we do not expect major changes before 3.0.
 
 The highlights of this release are:
 
-*  Includes a new packet/bit/symbol level physical layer model for the 802.11
-   OFDM PHY according to the IEEE 802.11-2012 standard, and a hypothetical
-   generic packet/bit/symbol level APSK physical layer model for further
-   experimentation. The new implementations include forward error correction
-   encoding/decoding, scrambling/descrambling, interleaving/deinterleaving, and
-   modulation/demodulation.
+* Includes a new packet/bit/symbol level physical layer model for the 802.11 OFDM PHY according to the IEEE 802.11-2012 standard, and a hypothetical generic packet/bit/symbol level APSK physical layer model for further experimentation. The new implementations include forward error correction encoding/decoding, scrambling/descrambling, interleaving/deinterleaving, and modulation/demodulation.
 
-*  Contains fixes for more than 300 defects found by Coverity, an online C++
-   static code analysis tool. The reported Defect Density is decreased to
-   0.5/kLoC which is considered a result. You can find the detailed results at
-   https://scan.coverity.com/projects/3472
+* Contains fixes for more than 300 defects found by Coverity, an online C++ static code analysis tool. The reported Defect Density is decreased to 0.5/kLoC which is considered a result. You can find the detailed results at https://scan.coverity.com/projects/3472
 
-*  Contains several other memory leak and memory management fixes reported by
-   valgrind memcheck.
+* Contains several other memory leak and memory management fixes reported by valgrind memcheck.
 
-*  Modernizes C++ source code using new C++11 features such as nullptr, auto
-   types, range loop, override, etc.
+* Modernizes C++ source code using new C++11 features such as nullptr, auto types, range loop, override, etc.
 
-*  A new tool to enable/disable INET features from the command line.
+* A new tool to enable/disable INET features from the command line.
 
-*  Rewritten serializer classes
+* Rewritten serializer classes
 
-*  SCTP improvements
+* SCTP improvements
 
-*  New IGMPv3, PIM-DM and PIM-SM models.
+* New IGMPv3, PIM-DM and PIM-SM models.
 
-*  Improved IPv4NetworkConfigurator
+* Improved IPv4NetworkConfigurator
 
-*  TUN/TAP virtual network interfaces
+* TUN/TAP virtual network interfaces
 
-*  New wireless tutorial
+* New wireless tutorial
 
-*  Added INET version macros (INET_VERSION, INET_PATCH_LEVEL)
+* Added INET version macros (INET_VERSION, INET_PATCH_LEVEL)
 
-This version requires OMNeT++ 4.6 or later. Read
-[what's new](https://github.com/inet-framework/inet/blob/v2.99.1/WHATSNEW) and
-[download INET-2.99.1](https://github.com/inet-framework/inet/releases/download/v2.99.1/inet-2.99.1-src.tgz)
-now.
+This version requires OMNeT++ 4.6 or later. Read [what's new](https://github.com/inet-framework/inet/blob/v2.99.1/WHATSNEW) and [download INET-2.99.1](https://github.com/inet-framework/inet/releases/download/v2.99.1/inet-2.99.1-src.tgz) now.
\ No newline at end of file
diff --git a/_posts/2015-06-24-INET-3.0.0-released.md b/_posts/2015-06-24-INET-3.0.0-released.md
index 7c77f56..cfb9e21 100644
--- a/_posts/2015-06-24-INET-3.0.0-released.md
+++ b/_posts/2015-06-24-INET-3.0.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.0.0 Stable Release Available
 category: news
----
 
 INET 3.0.0 is now available for download. This release contains a lot of 
 new features and fixes compared to 2.6. 
@@ -13,54 +12,54 @@ with 2.6 so you may need to adjust your models after upgrading.
 Highlights:
 
 *  A new physical layer model that builds upon the INET and MiXiM physical
-   layers, and brings them to new heights. Design goals were extreme
-   modularity, extensibility, the ability to support (and easily switch
-   between) various levels of detail, and the ability to add support for
-   exploiting various pieces of parallel hardware.
+layers and brings them to new heights. Design goals were extreme
+modularity, extensibility, the ability to support (and easily switch
+between) various levels of detail, and the ability to add support for
+exploiting various pieces of parallel hardware.
 *  Includes a new packet/bit/symbol level physical layer model for the 802.11
-   OFDM PHY according to the IEEE 802.11-2012 standard, and a hypothetical
-   generic packet/bit/symbol level APSK physical layer model for further
-   experimentation. The new implementations include forward error correction
-   encoding/decoding, scrambling/descrambling, interleaving/deinterleaving, and
-   modulation/demodulation.
+OFDM PHY according to the IEEE 802.11-2012 standard and a hypothetical
+generic packet/bit/symbol level APSK physical layer model for further
+experimentation. The new implementations include forward error correction
+encoding/decoding, scrambling/descrambling, interleaving/deinterleaving, and
+modulation/demodulation.
 *  Extensive refactoring aimed at improving code quality. It includes
-   directory restructuring, code formatting, refactoring of init stages and
-   publish-subscribe communication, and more.
+directory restructuring, code formatting, refactoring of init stages and
+publish-subscribe communication, and more.
 *  Modernized C++ source code using new C++11 features such as nullptr, auto
-   types, range loop, override, etc.
+types, range loop, override, etc.
 *  Network layer refactoring that allows higher layer protocols (including
-   routing protocols) to be written in a network protocol agnostic manner.
+routing protocols) to be written in a network protocol-agnostic manner.
 *  Numerous SCTP improvements
-*  New IGMPv3, PIM-DM and PIM-SM models
+*  New IGMPv3, PIM-DM, and PIM-SM models
 *  Improved IPv4NetworkConfigurator to support multi-path routing scenarios.
 *  TUN/TAP virtual network interfaces
 *  Network Emulation feature no longer depends on OMNeT++ to detect the presence
-   of PCAP. Instead the feature can be turned on/off by the user.
+of PCAP. Instead, the feature can be turned on/off by the user.
 *  Improved response time on external interfaces.
 *  Added support for sending NF_LINK_BREAK signal from BMAC and CSMA. This is 
-   required for certain routing protocols (i.e. AODV) to function properly.
+required for certain routing protocols (i.e., AODV) to function properly.
 *  Added a new power model:
-   - Removed obsolete classes: IBattery, BasicBattery, InetSimpleBattery and Energy.
+   - Removed obsolete classes: IBattery, BasicBattery, InetSimpleBattery, and Energy.
    - Added new interfaces: IEnergyConsumer, IEnergyStorage, and IEnergyGenerator.
-   - Added implementations: IdealEnergyStorage, and SimpleEnergyStorage.
+   - Added implementations: IdealEnergyStorage and SimpleEnergyStorage.
 *  Added a new physical environment model and removing obsolete classes: 
-   Obstacle, ObstacleControl, and AnnotationManager.
+Obstacle, ObstacleControl, and AnnotationManager.
 *  Added new geometry model: 
-   - orientation related classes: EulerAngles, Rotation, and Quaternion.
-   - basic 3D geometry classes: LineSegment, Box, Plane, and Polygon.
+   - Orientation related classes: EulerAngles, Rotation, and Quaternion.
+   - Basic 3D geometry classes: LineSegment, Box, Plane, and Polygon.
    - 3D convex shapes: Cuboid, Sphere, Prism, and Polyhedron.
-   - geometry cache data structures: SpatialGrid, QuadTree, and BVHTree.
+   - Geometry cache data structures: SpatialGrid, QuadTree, and BVHTree.
 *  Added support for drawing the physical objects on a compound module canvas
-   (Tkenv) in 2D as seen from a configured view angle.
+(Tkenv) in 2D as seen from a configured view angle.
 *  Rewritten packet serializer classes.
 *  Added a new StaticConcentricMobility similar to StaticGridMobility that places
-   nodes on concentric circles.
+nodes on concentric circles.
 *  Removed TracCI and TraCIScenarioManager because these modules are maintained
-   in the Veins framework.
-*  New step by step wireless tutorial
+in the Veins framework.
+*  New step-by-step wireless tutorial
 *  A new tool to enable/disable INET features from the command line
 
 This version requires OMNeT++ 4.6 or later. Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.0.0/WHATSNEW) file for more detail and
 [download INET-3.0.0](https://github.com/inet-framework/inet/releases/download/v3.0.0/inet-3.0.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2015-06-25-blog.md b/_posts/2015-06-25-blog.md
index 2ea13a2..07bf099 100644
--- a/_posts/2015-06-25-blog.md
+++ b/_posts/2015-06-25-blog.md
@@ -7,9 +7,9 @@ category: progress
 Now that INET 3.0 has been released, we made some changes to the git repository:
 
 * The old `master` branch has been renamed to `v2.x`. It will hold maintenance commits
-  for the  INET 2.x.
+for the INET 2.x.
 * The `master` branch has been set to the commit containing the 3.0 release.
 * The `integration` branch will contain the changes scheduled for INET 4.0.
 
 We hope that you find the changes in INET 3.0 useful and will start using it 
-in your own projects.
+in your own projects.
\ No newline at end of file
diff --git a/_posts/2015-10-26-INET-3.1.0-released.md b/_posts/2015-10-26-INET-3.1.0-released.md
index 8305d6b..b25b9de 100644
--- a/_posts/2015-10-26-INET-3.1.0-released.md
+++ b/_posts/2015-10-26-INET-3.1.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.1.1 Stable Release Available
 category: news
----
 
 INET 3.1.1 is now available for download. 
 
@@ -16,4 +15,4 @@ Highlights:
 This version requires OMNeT++ 4.6 or later. Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.1.1/WHATSNEW) file for more detail and
 [download INET-3.1.1](https://github.com/inet-framework/inet/releases/download/v3.1.1/inet-3.1.1-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2015-12-17-INET-3.2.0-released.md b/_posts/2015-12-17-INET-3.2.0-released.md
index aad43aa..bea19aa 100644
--- a/_posts/2015-12-17-INET-3.2.0-released.md
+++ b/_posts/2015-12-17-INET-3.2.0-released.md
@@ -2,11 +2,10 @@
 layout: post
 title: INET-3.2.0 Stable Release Available
 category: news
----
 
 For this release, we put a lot of work into refining and validating the new, extensible 802.11 MAC model to make it ready for replacing the old codebase. We used the ns-3 Wifi model for validation. This INET version, in addition to other improvements and bug fixes, also compiles with the recently released 3rd beta of OMNeT++ 5.0.
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.2.0/WHATSNEW) file for more detail and
 [download INET-3.2.0](https://github.com/inet-framework/inet/releases/download/v3.2.0/inet-3.2.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2016-01-22-INET-3.2.1-released.md b/_posts/2016-01-22-INET-3.2.1-released.md
index 04aedf2..ae651ab 100644
--- a/_posts/2016-01-22-INET-3.2.1-released.md
+++ b/_posts/2016-01-22-INET-3.2.1-released.md
@@ -6,12 +6,12 @@ category: news
 
 This minor version fixes several issues reported since the latest release.
 
-- 802.11 MAC model: EDCA, rate control crashes fixed
-- Radio: Fixed handling of abort reception/transmission.
-- Added missing INET_API defines
-- Physical layer: Fixed memory issues detected by valgrind
+- 802.11 MAC model: EDCA, rate control crashes have been fixed.
+- Radio: Handling of aborting reception/transmission is now fixed.
+- Added missing INET_API defines.
+- Physical layer: Memory issues detected by valgrind have been fixed.
 
 Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.2.1/WHATSNEW) file for more detail and
+[what's new](https://github.com/inet-framework/inet/blob/v3.2.1/WHATSNEW) file for more details and
 [download INET-3.2.1](https://github.com/inet-framework/inet/releases/download/v3.2.1/inet-3.2.1-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2016-03-16-INET-3.2.3-released.md b/_posts/2016-03-16-INET-3.2.3-released.md
index 667de60..723a5d1 100644
--- a/_posts/2016-03-16-INET-3.2.3-released.md
+++ b/_posts/2016-03-16-INET-3.2.3-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.2.3 Stable Release Available
 category: news
----
 
 This is a minor maintenance release that requires either OMNeT++ 4.6, 
 or 5.0rc or later. (Earlier test versions of OMNeT++ will not work.)
@@ -10,9 +9,9 @@ or 5.0rc or later. (Earlier test versions of OMNeT++ will not work.)
   - build: updated inet_featuretool (the same like the opp_featuretool in OMNeT++ 5.0 rc)
   - several fixes to make it compatible with both OMNeT++ 4.6 and 5.0
   - smoke and fingerprint tests are running on both OMNeT++ 4.6 and 5.0
-  - some varaiable renames and fixes in ieee802.11
+  - some variable renames and fixes in ieee802.11
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.2.3/WHATSNEW) file for more detail and
 [download INET-3.2.3](https://github.com/inet-framework/inet/releases/download/v3.2.3/inet-3.2.3-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2016-04-06-INET-3.2.4-released.md b/_posts/2016-04-06-INET-3.2.4-released.md
index 239638c..dae287d 100644
--- a/_posts/2016-04-06-INET-3.2.4-released.md
+++ b/_posts/2016-04-06-INET-3.2.4-released.md
@@ -2,15 +2,14 @@
 layout: post
 title: INET-3.2.4 Stable Release Available
 category: news
----
 
 This is a minor maintenance release that requires either OMNeT++ 4.6,
 or 5.0. (Earlier test versions of OMNeT++ will not work.)
 
-  - build: updated inet_featuretool (the same like the opp_featuretool in OMNeT++ 5.0)
+  - build: updated inet_featuretool (the same as the opp_featuretool in OMNeT++ 5.0)
   - minor fixes to make it build under both OMNeT++ 4.6 and 5.0
 
 Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.2.4/WHATSNEW) file for more detail and
+[what's new](https://github.com/inet-framework/inet/blob/v3.2.4/WHATSNEW) file for more details and
 [download INET-3.2.4](https://github.com/inet-framework/inet/releases/download/v3.2.4/inet-3.2.4-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2016-06-03-INET-3.3.0-released.md b/_posts/2016-06-03-INET-3.3.0-released.md
index 93db6d9..3ea31d4 100644
--- a/_posts/2016-06-03-INET-3.3.0-released.md
+++ b/_posts/2016-06-03-INET-3.3.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.3.0 Stable Release Available
 category: news
----
 
 This release requires either OMNeT++ 4.6 or 5.0. (Earlier test versions of OMNeT++ will not work.)
 
@@ -74,4 +73,4 @@ Ethernet:
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.3.0/WHATSNEW) file for more detail and
 [download INET-3.3.0](https://github.com/inet-framework/inet/releases/download/v3.3.0/inet-3.3.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2016-06-03-blog.md b/_posts/2016-06-03-blog.md
index 9e1dc18..3180672 100644
--- a/_posts/2016-06-03-blog.md
+++ b/_posts/2016-06-03-blog.md
@@ -2,15 +2,12 @@
 layout: post
 title: Heading towards INET 4.0
 category: progress
----
 
-With the release of INET 3.3 we are starting to work towards INET 4.0 which will
-contain numerous improvements that will require OMNeT++ 5.0. INET 3.3 is the last 
-release that will work with both OMNeT++ 4.6 and 5.0. 
+With the release of INET 3.3, we are starting to work towards INET 4.0, which will contain numerous improvements that will require OMNeT++ 5.0. INET 3.3 is the last release that will work with both OMNeT++ 4.6 and 5.0. 
 
 Major features to be added in INET 4.0:
 
-* A rewritten wireless tutorial
-* Enhanced visualization (2D/3D)
-* Reorganized StandardHost internals that will enable better configurability
-* Enhanced Ieee 802.11 MAC
+- A rewritten wireless tutorial
+- Enhanced visualization (2D/3D)
+- Reorganized StandardHost internals that will enable better configurability
+- Enhanced IEEE 802.11 MAC
\ No newline at end of file
diff --git a/_posts/2016-06-17-INET-3.4.0-released.md b/_posts/2016-06-17-INET-3.4.0-released.md
index 0f944a2..15393a2 100644
--- a/_posts/2016-06-17-INET-3.4.0-released.md
+++ b/_posts/2016-06-17-INET-3.4.0-released.md
@@ -6,18 +6,18 @@ category: news
 
 This INET release requires OMNeT++ 5.0 or later. This is due to the new visualization feature
 which uses the Canvas and OSG APIs introduced in OMNeT++ 5.0. Most other parts of the
-codebase still builds with OMNeT++ 4.6.
+codebase still build with OMNeT++ 4.6.
 
-Highlights is this release:
+Highlights in this release:
 
 Tutorials:
 
   - Added a Wireless Tutorial (tutorials/wireless). The tutorial consists of
     several simulation models of increasing complexity, demonstrating the INET
     architecture and features related to wireless communication networks. The
-    models are accompanied by a text which explains each step, complete with
+    models are accompanied by text which explains each step, complete with
     screenshots and recorded animations.
-  - Added draft for a visualization tutorial.
+  - Added a draft for a visualization tutorial.
 
 Visualizers:
 
@@ -32,12 +32,12 @@ Visualizers:
     models. They are responsible for displaying various aspects of the simulation
     in a graphical user interface. The most common mechanism they use is looking
     up other modules and/or subscribing to the signals they emit. The visualizer
-    modules are compatible with both Tkenv and Qtenv. In Qtenv they are able to
+    modules are compatible with both Tkenv and Qtenv. In Qtenv, they are able to
     display on both a 2D canvas and a 3D OSG scene.
 
-Instrument figures:
+Instrument Figures:
 
-  - Implemented a facility that allows one to display various gauges, meters
+  - Implemented a facility that allows one to display various gauges, meters,
     and indicators in the network graphics that take their inputs from signals.
     The "gadgets" themselves are figures that are added into the network using
     @figure properties, and they are driven by signals via @statistic properties,
@@ -64,7 +64,7 @@ Radio:
 
   - The physical environment model has been extended to include a ground model.
     Ground models need to implement the IGround interface that currently
-    contains a getElevation() method. A very simple implementation, FlatGround
+    contains a getElevation() method. A very simple implementation, FlatGround,
     is also provided.
   - The TwoRayGroundReflection model has been updated to use the ground model
     of the physical environment.
@@ -72,21 +72,21 @@ Radio:
 
 Mobility:
 
-  - Mobility models now use the initialZ parameter even if position is
+  - Mobility models now use the initialZ parameter even if the position is
     initialized from the display string.
   - Added VehicleMobility that simulates turning at waypoints.
-  - Now all mobile nodes face (i.e. set the  orientation to) the direction of
-    movement. This affects radio reception when direction antenna is used.
+  - Now all mobile nodes face (i.e., set the orientation to) the direction of
+    movement. This affects radio reception when a directional antenna is used.
 
-Physical enviromment:
+Physical environment:
 
   - Added geographic coordinate system support.
   - TracingObstacleLoss renamed to DielectricObstacleLoss.
 
 Misc:
 
-  - Added ApplicationPacket that can be used as generic application payload.
-    Currently it contains a sequence number.
+  - Added ApplicationPacket that can be used as a generic application payload.
+    Currently, it contains a sequence number.
   - UDPBasicApp/UDPSink: changed to use ApplicationPacket, and record
     received packet sequence numbers
   - RelayUnit: Added packetReceivedFromLowerSignal and packetSentToLowerSignal signals.
@@ -98,7 +98,7 @@ Misc:
 
 Build:
 
-  - Added a top level 'doc' target to build all INET documentation in a single step
+  - Added a top-level 'doc' target to build all INET documentation in a single step
   - Added project feature tests (tests/features)
 
 Read the
diff --git a/_posts/2017-02-22-INET-3.5.0-released.md b/_posts/2017-02-22-INET-3.5.0-released.md
index 75907d6..217d219 100644
--- a/_posts/2017-02-22-INET-3.5.0-released.md
+++ b/_posts/2017-02-22-INET-3.5.0-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.5.0 Stable Release Available
 category: news
----
 
 This release contains mostly bug fixes and compatibility changes. It requires 
 OMNeT++ 5.1. Earlier versions of OMNeT++ are *not* compatible.
@@ -27,7 +26,7 @@ Visualizers:
 DHCP:
 
   - DHCP fixes.
-  - DHCP can now activated in a Router by setting hasDHCP=true
+  - DHCP can now be activated in a Router by setting hasDHCP=true
   - Added new WirelessNetWith2DHCP example.
 
 Radio:
@@ -40,7 +39,7 @@ SCTP:
 
 GPSR:
 
-  - Allow to specify the interface name in a parameter instead of
+  - Allow specifying the interface name in a parameter instead of
     using a hardcoded interface name.
 
 Fixes:
@@ -62,4 +61,4 @@ Fixes:
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.5.0/WHATSNEW) file for more detail and
 [download INET-3.5.0](https://github.com/inet-framework/inet/releases/download/v3.5.0/inet-3.5.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2017-06-14-INET-3.6.0-released.md b/_posts/2017-06-14-INET-3.6.0-released.md
index 5bedbb9..f4b8919 100644
--- a/_posts/2017-06-14-INET-3.6.0-released.md
+++ b/_posts/2017-06-14-INET-3.6.0-released.md
@@ -9,30 +9,30 @@ minor enhancements. It requires OMNeT++ 5.1 or later.
 
 Highlights in this release:
 
- - On Windows, INET is no longer using the auto-import feature of the linker, because
-   it generated more than 65536 symbols. Dependent projects crashed because of this.
-   All INET APIs now should be prefixed with INET_API macro. (fixes #257)
+- On Windows, INET is no longer using the auto-import feature of the linker, because
+  it generated more than 65536 symbols. Dependent projects crashed because of this.
+  All INET APIs now should be prefixed with INET_API macro. (fixes #257)
 
- - The makefile now generates separate precompiled header for debug and release mode.
-   This is required to be able to quicly switch between release and debug mode in the IDE.
+- The makefile now generates a separate precompiled header for debug and release mode.
+  This is required to be able to quickly switch between release and debug mode in the IDE.
 
- - The IEEE 802.11 MAC model has been extended with several new components. The
-   implementation is entirely based on the standard IEEE 802.11™-2012 Part 11:
-   Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.
+- The IEEE 802.11 MAC model has been extended with several new components. The
+  implementation is entirely based on the standard IEEE 802.11™-2012 Part 11:
+  Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.
 
-   The new architecture is designed to be modular to facilitate experimenting
-   with new policies, features and algorithms within the MAC layer. Users can
-   easily replace individual components with their own implementations. Policies,
-   which most likely to be experimented with, are extracted into their own modules.
+  The new architecture is designed to be modular to facilitate experimenting
+  with new policies, features, and algorithms within the MAC layer. Users can
+  easily replace individual components with their own implementations. Policies,
+  which are most likely to be experimented with, are extracted into their own modules.
 
-   The new model has the following replaceable built-in policies:
+  The new model has the following replaceable built-in policies:
     - ACK policy
     - RTS/CTS policy
     - Originator and recipient block ACK agreement policies
     - MSDU aggregation policy
     - Fragmentation policy
 
-   The new model also separates the following components:
+  The new model also separates the following components:
     - Coordination functions
     - Channel access methods
     - MAC data services
@@ -49,30 +49,30 @@ Highlights in this release:
     - Frame queues
     - TX/RX
 
-   There are several enhancements and new features to the previous version, the
-   most notable are frame exchange sequences, block acknowledgement, and MSDU
-   aggregation.
+  There are several enhancements and new features compared to the previous version, the
+  most notable are frame exchange sequences, block acknowledgement, and MSDU
+  aggregation.
 
-   The new version was thoroughly tested against the old one using fingerprint
-   tests. The tests ensure that the new version doesn't introduce any regression.
-   In fact, the tests brought up a few problems in the old implementation that
-   were fixed in the new one.
+  The new version was thoroughly tested against the old one using fingerprint
+  tests. The tests ensure that the new version doesn't introduce any regression.
+  In fact, the tests brought up a few problems in the old implementation that
+  were fixed in the new one.
 
- - The power model has been extended with support for charge/current based models
-   as opposed to the existing energy/power based ones. A new energy management
-   component has also been added to separate monitoring and controlling of energy
-   consumers and generators from the rest of the model.
+- The power model has been extended with support for charge/current-based models
+  as opposed to the existing energy/power-based ones. A new energy management
+  component has also been added to separate monitoring and controlling energy
+  consumers and generators from the rest of the model.
 
- - New visualizers has been added to display packet drops and link breaks, data
-   contained in interface tables, routes stored in routing tables, queues filled
-   with packets, residual capacity of energy storages, and transport connections
-   between network nodes. The new visualizers are also added to the already existing
-   integrated ones. Note: many features that work with the 2D visualizers currently
-   don't work with the 3D OSG visualizers.
+- New visualizers have been added to display packet drops and link breaks, data
+  contained in interface tables, routes stored in routing tables, queues filled
+  with packets, residual capacity of energy storages, and transport connections
+  between network nodes. The new visualizers have also been added to the already existing
+  integrated ones. Note: many features that work with the 2D visualizers currently
+  don't work with the 3D OSG visualizers.
 
- - Added new features for various tutorials and showcases.
+- Added new features for various tutorials and showcases.
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.6.0/WHATSNEW) file for more detail and
 [download INET-3.6.0](https://github.com/inet-framework/inet/releases/download/v3.6.0/inet-3.6.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2017-08-23-initial-showcases-released.md b/_posts/2017-08-23-initial-showcases-released.md
index 57cb9f0..84125ff 100644
--- a/_posts/2017-08-23-initial-showcases-released.md
+++ b/_posts/2017-08-23-initial-showcases-released.md
@@ -5,25 +5,24 @@ category: news
 ---
 
 We are happy to announce the first showcase examples and tutorials for the
-INET Framework. We have been internally working on these items for over 
-a year. 
+INET Framework. We have been internally working on these items for over
+a year.
 
-Showcases are elaborated example simulations or simulation studies 
-that show off various components and features of the INET Framework. 
-Each showcase consist of a fully configured simulation model that
+Showcases are elaborate example simulations or simulation studies
+that show off various components and features of the INET Framework.
+Each showcase consists of a fully configured simulation model that
 has an associated documentation that describes the goal of the simulation
 study and the simulation setup, and discusses the results.
 
 To see what showcases and tutorials are available, choose the
 **Showcases** and **Tutorials** items from the INET site menu.
 We currently have 10 Visualization showcases and 5 Wireless
-showcases. The Wireless Tutorial which has been available for
-some time has also been updated.
+showcases. The Wireless Tutorial, which has been available for
+some time, has also been updated.
 
 We use the GitHub Pages infrastructure for the showcase and tutorial
-web pages, which means that pages are easy to write (Markdown),
-and easy to be contributed to (via GitHub pull requests).
+web pages, which means that pages are easy to write (Markdown) and easy to contribute to (via GitHub pull requests).
 
 Links:
 * [Showcases](https://inet.omnetpp.org/docs/showcases)
-* [Tutorials](https://inet.omnetpp.org/docs/tutorials)
+* [Tutorials](https://inet.omnetpp.org/docs/tutorials)
\ No newline at end of file
diff --git a/_posts/2017-08-24-INET-3.99.0-released.md b/_posts/2017-08-24-INET-3.99.0-released.md
index f211439..20073be 100644
--- a/_posts/2017-08-24-INET-3.99.0-released.md
+++ b/_posts/2017-08-24-INET-3.99.0-released.md
@@ -20,107 +20,107 @@ The highlights of this release are:
 
 1. Redesigned network node architecture
 
-   The internal structure of network nodes has been changed considerably. These
-   changes have profound effects on how applications are using protocols, and
-   also on how protocols communicate with each other.
-
-   With the new architecture, applications are able to use multiple protocols
-   simultaneously, even if the protocols are part of different protocol layers.
-   For example, in the old model it was impossible for a StandardHost application
-   to use TCP and UDP protocols at the same time. This old restriction has been
-   eliminated. Applications can now talk to any protocol (or several protocols),
-   even several layers below. The dispatch mechanism necessary for that is now
-   built into the new network node architecture.
-
-   Furthermore, protocols don't have to deal with dispatching packets to other
-   protocols or applications any more. In the old architecture, many protocols
-   (e.g. IP) implemented their own mechanisms to communicate with multiple
-   protocols/applications. In the new network node architecture this issue is
-   solved by the dispatching mechanism, and protocols don't need to implement
-   their own dispatching.
-
-   The main component of the new network node architecture is the so-called
-   MessageDispatcher module type. Such modules are responsible for directing
-   packets from one protocol to the other and also between applications and
-   protocols. Most often, MessageDispatcher modules are displayed as horizontal
-   lines between protocol layers inside the network nodes. Protocols and
-   applications connect to the dispatcher module directly above and below them.
-   Dispatchers do not need to be configured because they learn about connected
-   protocols/application at runtime.
-
-   Please refer to the 'src/inet/node/base' and 'src/inet/node/inet' folders for
-   more details.
+The internal structure of network nodes has been changed considerably. These
+changes have profound effects on how applications are using protocols, and
+also on how protocols communicate with each other.
+
+With the new architecture, applications are able to use multiple protocols
+simultaneously, even if the protocols are part of different protocol layers.
+For example, in the old model it was impossible for a StandardHost application
+to use TCP and UDP protocols at the same time. This old restriction has been
+eliminated. Applications can now talk to any protocol (or several protocols),
+even several layers below. The dispatch mechanism necessary for that is now
+built into the new network node architecture.
+
+Furthermore, protocols don't have to deal with dispatching packets to other
+protocols or applications any more. In the old architecture, many protocols
+(e.g. IP) implemented their own mechanisms to communicate with multiple
+protocols/applications. In the new network node architecture this issue is
+solved by the dispatching mechanism, and protocols don't need to implement
+their own dispatching.
+
+The main component of the new network node architecture is the so-called
+MessageDispatcher module type. Such modules are responsible for directing
+packets from one protocol to the other and also between applications and
+protocols. Most often, MessageDispatcher modules are displayed as horizontal
+lines between protocol layers inside the network nodes. Protocols and
+applications connect to the dispatcher module directly above and below them.
+Dispatchers do not need to be configured because they learn about connected
+protocols/application at runtime.
+
+Please refer to the 'src/inet/node/base' and 'src/inet/node/inet' folders for
+more details.
 
 2. Introduction of packet tags
 
-   Packets no longer carry control info data structures while being passed around
-   in a network node. They have a set of so-called packet tags attached instead.
-   A packet tag is usually a very small data structure that focuses on a single
-   parameterization aspect of one or more protocols. For example, a MacAddressReq
-   tag specifies the requested transmitter and receiver MAC addresses for a MAC
-   protocol.
-
-   In general, packet tags come in three flavors: requests (top down), indications
-   (bottom up), and plain tags (meta data). The naming convention for packet tags
-   is to use the Req, Ind, or Tag suffix respectively. Tags are usually defined
-   in MSG files, so that they can be inspected in the runtime environment.
-
-   Tags can pass through protocol layers and reach far away from the originator
-   protocol in both the downward and upward direction. This allows protocols to
-   implement mechanisms that depend on meta data that is not directly present in
-   a packet. For example, a wireless routing protocol could make more informed
-   decisions when building the routing table by using the SignalPowerInd tag
-   attached by the physical layer. Similarly, an application could attach an
-   InterfaceReq to a packet in order to instruct the routing protocol to use a
-   particular outgoing interface.
-
-   The old control info data structures that were used with packets are no longer
-   available. They have been split into several packet tags. Other control info
-   data structures that were used with commands are left unchanged. All related
-   protocols have been updated to use the new packet tags. New tags have also
-   been introduced which don't have a counterpart in the old data structures.
-
-   Please refer to the MSG files with the 'Tag.msg' suffix for more details.
+Packets no longer carry control info data structures while being passed around
+in a network node. They have a set of so-called packet tags attached instead.
+A packet tag is usually a very small data structure that focuses on a single
+parameterization aspect of one or more protocols. For example, a MacAddressReq
+tag specifies the requested transmitter and receiver MAC addresses for a MAC
+protocol.
+
+In general, packet tags come in three flavors: requests (top down), indications
+(bottom up), and plain tags (metadata). The naming convention for packet tags
+is to use the Req, Ind, or Tag suffix respectively. Tags are usually defined
+in MSG files, so that they can be inspected in the runtime environment.
+
+Tags can pass through protocol layers and reach far away from the originator
+protocol in both the downward and upward direction. This allows protocols to
+implement mechanisms that depend on metadata that is not directly present in
+a packet. For example, a wireless routing protocol could make more informed
+decisions when building the routing table by using the SignalPowerInd tag
+attached by the physical layer. Similarly, an application could attach an
+InterfaceReq to a packet in order to instruct the routing protocol to use a
+particular outgoing interface.
+
+The old control info data structures that were used with packets are no longer
+available. They have been split into several packet tags. Other control info
+data structures that were used with commands are left unchanged. All related
+protocols have been updated to use the new packet tags. New tags have also
+been introduced which don't have a counterpart in the old data structures.
+
+Please refer to the MSG files with the 'Tag.msg' suffix for more details.
 
 3. Introduction of flat packets
 
-   A new packet API is introduced that supports efficient construction, sharing,
-   duplication, encapsulation, aggregation, fragmentation and serialization. The
-   new API also supports dual representation, packet data can be accessed both as
-   raw bytes and as objects.
+A new packet API is introduced that supports efficient construction, sharing,
+duplication, encapsulation, aggregation, fragmentation, and serialization. The
+new API also supports dual representation, packet data can be accessed both as
+raw bytes and as objects.
 
-   The new API contains two layers, the lower layer focuses on the representation
-   of data. The primary building block of the lower layer is the Chunk class and
-   its subclasses. The upper layer builds on top of this and provides the typical
-   packet, queue and buffer abstractions used by protocols.
+The new API contains two layers, the lower layer focuses on the representation
+of data. The primary building block of the lower layer is the Chunk class and
+its subclasses. The upper layer builds on top of this and provides the typical
+packet, queue, and buffer abstractions used by protocols.
 
-   Nearly all protocols (except SCTP) have been changed to use the new packet API.
-   This includes TCP, UDP, IPv4, IPv6, AODV, OSPF, RIP, MPLS, Ethernet, PPP,
-   802.11, etc. Due to the flat nature of the new packet data structure, all old
-   packet data structures (subclasses of cPacket) have been replaced with chunks
-   (subclasses of FieldChunk).
+Nearly all protocols (except SCTP) have been changed to use the new packet API.
+This includes TCP, UDP, IPv4, IPv6, AODV, OSPF, RIP, MPLS, Ethernet, PPP,
+802.11, etc. Due to the flat nature of the new packet data structure, all old
+packet data structures (subclasses of cPacket) have been replaced with chunks
+(subclasses of FieldChunk).
 
-   The various old TCP transfer mode parameters which were used to distinguish
-   between communicating with simple byte counts, objects, or byte streams are
-   obsolete. Applications and protocols are free to use any kind of chunk in any
-   combination. Other protocols will be able to handle such packets transparently
-   using the new API.
+The various old TCP transfer-mode parameters which were used to distinguish
+between communicating with simple byte counts, objects, or byte streams are
+obsolete. Applications and protocols are free to use any kind of chunk in any
+combination. Other protocols will be able to handle such packets transparently
+using the new API.
 
-   Furthermore, all old packet serializer classes have been changed to integrate
-   with the new packet API. This allows the transparent processing of packets
-   by protocols independently whether they are actually represented as a sequence
-   of bytes or as a sequence of field based chunks.
+Furthermore, all old packet serializer classes have been changed to integrate
+with the new packet API. This allows the transparent processing of packets
+by protocols independently of whether they are actually represented as a sequence
+of bytes or as a sequence of field-based chunks.
 
-   NOTE: SCTP has not been ported yet to the new architeture and is currently
-   excluded from the build.
+NOTE: SCTP has not been ported yet to the new architecture and is currently
+excluded from the build.
 
-   Please refer to the 'src/inet/common/packet' and 'test/packet' folders for
-   more details.
+Please refer to the 'src/inet/common/packet' and 'test/packet' folders for
+more details.
 
-4. The new implementation has been extensibly tested. We used fingerprint tests
-   after each change to ensure that all protocol behaviors have been preserved.
+4. The new implementation has been extensively tested. We used fingerprint tests
+after each change to ensure that all protocol behaviors have been preserved.
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.99.0/WHATSNEW) file for more detail and
 [download INET-3.99.0](https://github.com/inet-framework/inet/releases/download/v3.99.0/inet-3.99.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2017-09-15-ipv4configurator-tutorial-released.md b/_posts/2017-09-15-ipv4configurator-tutorial-released.md
index edf0b1d..ad3eb8b 100644
--- a/_posts/2017-09-15-ipv4configurator-tutorial-released.md
+++ b/_posts/2017-09-15-ipv4configurator-tutorial-released.md
@@ -2,16 +2,15 @@
 layout: post
 title: IPv4 Network Configurator Tutorial Released
 category: news
----
 
 How to configure IPv4 addresses and routing tables in an INET simulation
 is a recurring question on the mailing list. It is not always trivial
-how to use INET's netwok configurator for various types of networks,
+how to use INET's network configurator for various types of networks,
 and how to incorporate special requirements. Therefore, we are particularly happy
 to report that we have completed the writing of the
 *IPv4 Network Configurator Tutorial*, and it has been made available
 on the INET site. We hope that the tutorial will be useful, and help
-users get the most of out INET.
+users get the most out of INET.
 
 If you spot errors in the tutorial or have other feedback, you can
 enter your comments by following the "Discussion" links found in the
@@ -19,4 +18,4 @@ tutorial pages themselves. If you wish to contribute, you can do so
 by submitting pull requests against the `inet-tutorials` repository.
 
 Links:
-* [IPv4 Network Configurator Tutorial](https://inet.omnetpp.org/docs/tutorials/configurator/doc/)
+* [IPv4 Network Configurator Tutorial](https://inet.omnetpp.org/docs/tutorials/configurator/doc/)
\ No newline at end of file
diff --git a/_posts/2017-10-02-INET-3.6.2-released.md b/_posts/2017-10-02-INET-3.6.2-released.md
index cbd8847..df108db 100644
--- a/_posts/2017-10-02-INET-3.6.2-released.md
+++ b/_posts/2017-10-02-INET-3.6.2-released.md
@@ -1,3 +1,4 @@
+```markdown
 ---
 layout: post
 title: INET-3.6.2 Stable Release Available
@@ -7,14 +8,15 @@ category: news
 This release contains minor bug fixes and compatibility fixes for the final
 OMNeT++ 5.2 release. It requires OMNeT++ 5.1 or later.
 
- - Tcp: Fixed incorrect connection pointer in rexmitQueue.
- - Edcaf: Fixed aifs calculation for customised aifsn.
- - Visualization: parameter rename
- - inet_featuretool: Removed warning when treating a missing feature in the state files as default.
- - Updated showcases and tutorials.
- - Various fixes to eliminate warnings on clang 4 and gcc 7.x.
+- Tcp: Fixed incorrect connection pointer in rexmitQueue.
+- Edcaf: Fixed aifs calculation for customised aifsn.
+- Visualization: parameter rename
+- inet_featuretool: Removed warning when treating a missing feature in the state files as default.
+- Updated showcases and tutorials.
+- Various fixes to eliminate warnings on clang 4 and gcc 7.x.
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.6.2/WHATSNEW) file for more detail and
 [download INET-3.6.2](https://github.com/inet-framework/inet/releases/download/v3.6.2/inet-3.6.2-src.tgz)
 now.
+```
\ No newline at end of file
diff --git a/_posts/2017-10-06-two-showcases-released.md b/_posts/2017-10-06-two-showcases-released.md
index d74f3b6..7ef7f7c 100644
--- a/_posts/2017-10-06-two-showcases-released.md
+++ b/_posts/2017-10-06-two-showcases-released.md
@@ -5,7 +5,7 @@ category: news
 ---
 
 We are happy to announce the availability of two more showcase examples.
-*Styling and Appearance* discusses how to customize the INET visualizers.
+*Styling and Appearance* discusses how to customize the INET visualisers.
 *The Hidden Node Problem* demonstrates the hidden node problem
 in 802.11 networks and the associated use of the RTS/CTS mechanism.
 
@@ -13,10 +13,10 @@ To see which showcase examples and tutorials are available, choose the
 *Showcases* and *Tutorials* items from the INET site menu.
 
 If you spot errors or have other feedback, you can enter your comments
-by following the "Discussion" links found in the showcases pages themselves.
+by following the "Discussion" links found in the showcase pages themselves.
 If you wish to contribute, you can do so by submitting pull requests
 against the `inet-showcases` repository.
 
 Links:
-* [Styling and Appearance](https://inet.omnetpp.org/docs/showcases/visualizer/styling/doc)
-* [The Hidden Node Problem](https://inet.omnetpp.org/docs/showcases//wireless/hiddennode/doc)
+* [Styling and Appearance](https://inet.omnetpp.org/docs/showcases/visualiser/styling/doc)
+* [The Hidden Node Problem](https://inet.omnetpp.org/docs/showcases/wireless/hiddennode/doc)
\ No newline at end of file
diff --git a/_posts/2017-10-11-three-showcases-released.md b/_posts/2017-10-11-three-showcases-released.md
index 2e3f0d9..8ce711c 100644
--- a/_posts/2017-10-11-three-showcases-released.md
+++ b/_posts/2017-10-11-three-showcases-released.md
@@ -11,18 +11,17 @@ to more complex ones like Rician and Rayleigh fading.
 *Power Consumption* demonstrates the modeling of energy consumption, energy
 storage and generation in INET through the example of a mobile ad-hoc
 network. *Visualizing Transport Connections* shows how to make INET add markers to
-the endpoints of transport connections to help visually matching them.
+the endpoints of transport connections to help visually match them.
 
 To see which showcase examples and tutorials are available, choose the
 *Showcases* and *Tutorials* items from the INET site menu.
 
 If you spot errors or have other feedback, you can enter your comments
-by following the "Discussion" links found in the showcases pages themselves.
+by following the "Discussion" links found on the showcases pages themselves.
 If you wish to contribute, you can do so by submitting pull requests
 against the `inet-showcases` repository.
 
 Links:
 * [Path Loss Models](https://inet.omnetpp.org/docs/showcases/wireless/pathloss/doc)
-* [Power Consumption](https://inet.omnetpp.org/docs/showcases//wireless/power/doc)
-* [Visualizing Transport Connections](https://inet.omnetpp.org/docs/showcases/visualizer/transportconnection/doc)
-
+* [Power Consumption](https://inet.omnetpp.org/docs/showcases/wireless/power/doc)
+* [Visualizing Transport Connections](https://inet.omnetpp.org/docs/showcases/visualizer/transportconnection/doc)
\ No newline at end of file
diff --git a/_posts/2017-11-17-INET-3.99.1-released.md b/_posts/2017-11-17-INET-3.99.1-released.md
index 9f6a48a..f1983d8 100644
--- a/_posts/2017-11-17-INET-3.99.1-released.md
+++ b/_posts/2017-11-17-INET-3.99.1-released.md
@@ -6,7 +6,7 @@ category: news
 
 This release is the second development snapshot of the upcoming INET-4.0 version.
 
-The code is still work in progress, which means some details may change until the
+The code is still a work in progress, which means some details may change until the
 final 4.0 version is released. At the moment, it requires a modified version of
 OMNeT++ 5.1 or 5.2. The modification is distributed as a patch file in the
 'misc/patch' folder.
@@ -16,29 +16,29 @@ The highlights of this release are:
 1. General
  - Dropped obsolete run scripts for individual simulations. The run scripts are
    replaced by a setenv script in the INET installation and separate inet scripts
-   in the bin folder. Run 'setenv' once from the shell to setup the environment
-   variables, and run 'inet', 'inet_release' or 'inet_dbg' from the simulation
+   in the bin folder. Run 'setenv' once from the shell to set up the environment
+   variables, and run 'inet', 'inet_release', or 'inet_dbg' from the simulation
    directory.
  - Removed compatibility macros required for OMNeT++ 4.x builds. This new INET
    version doesn't build with OMNeT++ 4.x versions.
- - Renamed the byte and bit C++ units to B and b respectively. The new names
+ - Renamed the byte and bit C++ units to B and b, respectively. The new names
    were selected to be conformant with the IEC & IEEE unit conventions.
  - Fixed several memory leaks and other minor bugs.
 
 2. Shared pointer
  - Added aliases for std::shared_ptr, std::make_shared, std::dynamic_pointer_cast,
-   etc. to support replacing the shared pointer implementation used by the new
+   etc., to support replacing the shared pointer implementation used by the new
    Packet API.
  - Added a new shared pointer implementation (from Boost) called IntrusivePtr.
    The new implementation uses only 1 counter (no weak counter) that is directly
    added to the shared object using inheritance (thus intrusive). This shared
    pointer is not thread safe, so it doesn't use atomic operations to increment
    and decrement counters, but generally that isn't a requirement for simulation.
-   According to speed measurements (see tests/speed folder) the release builds
+   According to speed measurements (see tests/speed folder), the release builds
    run 5-10% faster.
 
 3. CRC handling
- - CRC insertion and validation code has been refactored and adapted to the new
+ - Refactored and adapted CRC insertion and validation code to the new
    Packet API. This change affects UDP, TCP, IPv4, IPv6, ICMPv4, ICMPv6, Ethernet,
    and IEEE 802.11. The protocol modules have a parameter to control CRC handling.
    They support different CRC operation modes: disabled, declared, and computed.
@@ -46,7 +46,7 @@ The highlights of this release are:
    be selected if packets are recorded in a PCAP file.
 
 4. Ethernet
- - Refactored physical layer packet representation and processing
+ - Refactored physical layer packet representation and processing.
  - Cleaned up MSG files defining ethernet PHY and MAC frames and headers.
 
 5. IEEE 802.2
@@ -66,11 +66,11 @@ The highlights of this release are:
    in terms of symbols.
  - Fixed PHY header length in Ieee80211Radio. Added separate PHY chunks and PHY
    padding bits for completeness. This change doesn't affect the signal duration,
-   because it was alrady correctly computed.
+   because it was already correctly computed.
  - Added descriptors for several parts for signals, transmissions, modes, bands,
-   channels, etc. The new descriptors allow inspecting of the signal meta data
+   channels, etc. The new descriptors allow inspecting the signal meta data
    in the runtime user interface.
- - Extended 802.11 layered error model for packet level simulation.
+ - Extended 802.11 layered error model for packet-level simulation.
 
 7. CsmaCa
  - Added 'fcsMode' parameter and FCS computation and verification.
@@ -87,7 +87,7 @@ The highlights of this release are:
 
 9. Network interface
  - Added the InterfaceEntry class used by InterfaceTable to the corresponding
-   NIC modules, because they represent the same network interface. All network
+   NIC modules because they represent the same network interface. All network
    interface modules are required to have a @class(InterfaceEntry) property in
    their NED definition. This change also allows one to see the internal state
    of a network interface just by selecting its submodule in the runtime user
@@ -97,31 +97,31 @@ The highlights of this release are:
  - Extracted a separate IAntennaGain interface from the IAntenna interface. This
    change allows the transmissions to carry directional selectivity even if the
    transmitter radio gets destroyed during the propagation of the signal.
- - Changed transmitter lookup to use radio identifier instead of internal pointer
+ - Changed transmitter lookup to use radio identifier instead of an internal pointer
    to fix crashes when the condition described above occurs.
  - Separated simsignals for transmission/reception from radio signal departure/arrival.
-   This allows differentiating signals at the receiver which are actually attempted
+   This allows differentiating signals at the receiver that are actually attempted
    to be received as opposed to simply arriving there.
 
 11. MANET routing
  - Adapted all MANET routing protocols (AODV, DYMO, and GPSR) to the refactored
    INetfilter hook interface. Routing protocols query and modify the packet and/or
-   the attached tags as they need.
+   the attached tags as needed.
 
 12. TCP
  - Removed obsolete TCP socket 'dataTransferMode' parameter from all implementations.
-   Applications don't have to decide upfront between sending byte count based, field
+   Applications don't have to decide upfront between sending byte count-based, field
    based, or raw bytes based packets. With the new API, applications can send any
    combination of the above over the same connection.
 
 13. Visualizer
  - Added a new set of integrated visualizer modules called IntegratedMultiVisualizer,
    IntegratedMultiCanvasVisualizer, and IntegratedMultiOsgVisualizer. These modules
-   contain a submodule vector of all special purpose visualizers inside as opposed
+   contain a submodule vector of all special-purpose visualizers inside as opposed
    to a single instance. This change allows, for example, one to easily configure
    several visualizers to display various aspects of the simulation differently.
 
 Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.99.1/WHATSNEW) file for more detail and
+[what's new](https://github.com/inet-framework/inet/blob/v3.99.1/WHATSNEW) file for more details and
 [download INET-3.99.1](https://github.com/inet-framework/inet/releases/download/v3.99.1/inet-3.99.1-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2017-12-22-INET-3.6.3-released.md b/_posts/2017-12-22-INET-3.6.3-released.md
index b06248f..abb4b2f 100644
--- a/_posts/2017-12-22-INET-3.6.3-released.md
+++ b/_posts/2017-12-22-INET-3.6.3-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: INET-3.6.3 Stable Release Available
 category: news
----
 
 This release contains minor bug fixes and compatibility fixes for the
 OMNeT++ 5.3 Preview 1 release. It requires OMNeT++ 5.1 or later.
@@ -25,14 +24,11 @@ Packetdrill:
 
 Ieee802154NarrowbandScalarRadio:
 
-  - The bandwidth was not correctly claculated, leading to incorrect channel allocation
+  - The bandwidth was not correctly calculated, leading to incorrect channel allocation
   - The PHY header was calculated wrong
 
 APSKScalarReceiver:
 
   - Fixed sensitivity bug in APSKScalarReceiver found by Tobias Thiel
 
-Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.6.3/WHATSNEW) file for more detail and
-[download INET-3.6.3](https://github.com/inet-framework/inet/releases/download/v3.6.3/inet-3.6.3-src.tgz)
-now.
+Read the [what's new](https://github.com/inet-framework/inet/blob/v3.6.3/WHATSNEW) file for more detail and [download INET-3.6.3](https://github.com/inet-framework/inet/releases/download/v3.6.3/inet-3.6.3-src.tgz) now.
\ No newline at end of file
diff --git a/_posts/2017-12-22-INET-3.99.2-released.md b/_posts/2017-12-22-INET-3.99.2-released.md
index c0dfc01..82963ef 100644
--- a/_posts/2017-12-22-INET-3.99.2-released.md
+++ b/_posts/2017-12-22-INET-3.99.2-released.md
@@ -182,4 +182,4 @@ The highlights of this release are:
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.99.2/WHATSNEW) file for more detail and
 [download INET-3.99.2](https://github.com/inet-framework/inet/releases/download/v3.99.2/inet-3.99.2-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2018-03-22-INET-3.6.4-released.md b/_posts/2018-03-22-INET-3.6.4-released.md
index 115e34a..10b6fb5 100644
--- a/_posts/2018-03-22-INET-3.6.4-released.md
+++ b/_posts/2018-03-22-INET-3.6.4-released.md
@@ -3,20 +3,21 @@ layout: post
 title: INET-3.6.4 Stable Release Available
 category: news
 ---
+
 This release contains minor bug fixes and compatibility fixes for the
 OMNeT++ 5.3 Preview 4 release. It requires OMNeT++ 5.1 or later.
 
 General:
 
   - Changed some module parameters from double to int.
-  - Corrected memory management issue in radio module.
-  - common: added intWithUnit() ned function.
+  - Corrected a memory management issue in the radio module.
+  - common: added intWithUnit() NED function.
 
 Packet printer:
 
-  - made it compatible with the new message printer API in OMNeT++ 5.3
+  - Made it compatible with the new message printer API in OMNeT++ 5.3.
 
 Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.6.4/WHATSNEW) file for more detail and
+[what's new](https://github.com/inet-framework/inet/blob/v3.6.4/WHATSNEW) file for more details and
 [download INET-3.6.3](https://github.com/inet-framework/inet/releases/download/v3.6.4/inet-3.6.4-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2018-04-13-INET-3.99.3-released.md b/_posts/2018-04-13-INET-3.99.3-released.md
index 7c07978..caa4247 100644
--- a/_posts/2018-04-13-INET-3.99.3-released.md
+++ b/_posts/2018-04-13-INET-3.99.3-released.md
@@ -33,7 +33,7 @@ The highlights of this release are:
    function level documentation has been updated.
 
    For more details, see the related patch at:
-   https://github.com/inet-framework/inet/commit/cf00e516f318893de5f396a498eb11592d8dd1b9
+   [https://github.com/inet-framework/inet/commit/cf00e516f318893de5f396a498eb11592d8dd1b9](https://github.com/inet-framework/inet/commit/cf00e516f318893de5f396a498eb11592d8dd1b9)
 
 3. Packet dissector
 
@@ -47,12 +47,12 @@ The highlights of this release are:
 
    The packet dissector is mostly implemented in the PacketDissector C++ class.
    It relies on small registered protocol-specific dissector classes such as the
-   Ipv4ProtocolDissector. User defined protocols can register their own protocol
+   Ipv4ProtocolDissector. User-defined protocols can register their own protocol
    dissector classes to extend the functionality of the generic packet dissector.
 
 4. Packet filter
 
-   Filtering packets based on the actual data they contain is a long time missing
+   Filtering packets based on the actual data they contain is a long-time missing
    functionality of INET. With the help of the new packet dissector API, it is
    very simple to create such packet filters.
 
@@ -60,18 +60,18 @@ The highlights of this release are:
    packet filter implemented in the PacketFilter C++ class. The expression syntax
    is the same as other OMNeT++ expressions, and the data filter is matched against
    individual parts of the packet as found by the packet dissector. For example,
-   the expression "inet::Ipv4Header and srcAddress(10.0.0.*)" matches all packets
-   that contains an IPv4 header with a '10.0.0' source address prefix.
+   the expression "inet::Ipv4Header and srcAddress(10.0.0.\*)" matches all packets
+   that contain an IPv4 header with a '10.0.0' source address prefix.
 
 5. Packet printer
 
    Based on the new packet dissector, the INET packet printer has been reworked.
    The new packet printer is implemented in the PacketPrinter C++ class. It relies
-   on small protocol specific printer classes to form the user readable string
-   representation. User defined protocols can register their own protocol printer
+   on small protocol-specific printer classes to form the user-readable string
+   representation. User-defined protocols can register their own protocol printer
    classes to extend the functionality of the generic packet printer.
 
-   With the OMNeT++ 5.3 version the message printer API has been changed to provide
+   With the OMNeT++ 5.3 version, the message printer API has been changed to provide
    support for ANSI escape sequences for styling, and for options. The new INET
    packet printer allows showing/hiding columns and control various printing
    features from Qtenv. The new packet printer provides the following columns in
@@ -83,11 +83,11 @@ The highlights of this release are:
 6. Packet tags
 
    With the OMNeT++ 5.3 version, the old experimental API for attaching tag objects
-   to packets is no longer available. Meanwhile INET has been extended with a very
+   to packets is no longer available. Meanwhile, INET has been extended with a very
    similar, although not exactly source code compatible API.
 
    The most important consequence is that cMessage and cPacket instances cannot
-   have tags attached any more. In order to make dispatching non-packet messages
+   have tags attached anymore. In order to make dispatching non-packet messages
    between protocols still possible, two new cMessage subclasses called Request
    and Indication have been introduced. Protocols send instances of said classes
    to request services from other protocols or indicate status changes to other
@@ -157,8 +157,8 @@ The highlights of this release are:
     fit.
 
     The physical environment ground model has been extended with a new OSG based
-    OsgEarthGround model which uses the elevation data of the map. The ground models
-    have been also extended with the computation of the ground normal vector.
+    OsgEarthGround model that uses the elevation data of the map. The ground models
+    have also been extended with the computation of the ground normal vector.
 
     Some globally registered protocol identifiers (e.g. Protocol::ieee80211) have
     been split into separate PHY, MAC, and MGMT protocols to disambiguate packet
@@ -170,9 +170,9 @@ The highlights of this release are:
     main purpose is to simplify MSG files, remove unnecessary C++ customizations,
     and to ease understanding and maintaining these files.
 
-    Potential infinite loop in the GPSR MANET routing has been fixed.
+    A potential infinite loop in the GPSR MANET routing has been fixed.
 
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.99.3/WHATSNEW) file for more detail and
 [download INET-3.99.3](https://github.com/inet-framework/inet/releases/download/v3.99.3/inet-3.99.3-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2018-06-28-INET-4.0.0-released.md b/_posts/2018-06-28-INET-4.0.0-released.md
index 3a4de68..78965c2 100644
--- a/_posts/2018-06-28-INET-4.0.0-released.md
+++ b/_posts/2018-06-28-INET-4.0.0-released.md
@@ -6,7 +6,7 @@ category: news
 
 With the new INET 4.0 release, the development of the old INET 3.x branch is
 stopped. Users are strongly encouraged to use the new INET 4.0 version for new
-projects and also for migrating existing projects. Admittably, migration is not
+projects and also for migrating existing projects. Admittedly, migration is not
 trivial, but there's an 'INET 4.0 Migration Guide' to help with the task under
 the 'doc/misc' folder.
 
@@ -14,7 +14,7 @@ The main changes of the new INET 4.0 major stable release are:
 
 1. Packet API
 
-   The INET Packet API has been completely redesigned to supports efficient
+   The INET Packet API has been completely redesigned to support efficient
    construction, sharing, duplication, encapsulation, aggregation, fragmentation,
    and serialization of packets.
 
@@ -24,7 +24,7 @@ The main changes of the new INET 4.0 major stable release are:
    to packet data, and queueing and buffering packet data.
 
    The new Packet API also makes implementing communication protocols easier. The
-   resulting code looks more similar to the real world implementation. Supporting
+   resulting code looks more similar to the real-world implementation. Supporting
    emulation is pretty much trivial when implementing communication protocols.
 
    For more details on how to use the new Packet API, see the 'INET Developer's Guide'.
@@ -43,7 +43,7 @@ The main changes of the new INET 4.0 major stable release are:
 
    The somewhat outdated 'INET Framework for OMNeT++ Manual' has been reworked
    and split into the 'INET User's Guide' and 'INET Developer's Guide'. Several
-   new detailed showcases have been added and many have been updated, they are
+   new detailed showcases have been added and many have been updated; they are
    available on the INET website.
 
 The highlights of this release since the last development release are:
@@ -66,8 +66,8 @@ The highlights of this release since the last development release are:
    sense that it allows configuring the module type for submodule vector elements.
 
    The replacement of the EthernetInterface queueType and the Ieee80211Interface
-   agentType parameters requires the applications which use them to be updated.
-   The queueType parameter had effect on the dataQueueType of the EtherQosQueue,
+   agentType parameters requires the applications that use them to be updated.
+   The queueType parameter had an effect on the dataQueueType of the EtherQosQueue,
    which is no longer true. The agentType parameter depended on the mgmtType
    parameter, which is also no longer true. These parameters must be set separately.
 
@@ -75,7 +75,7 @@ The highlights of this release since the last development release are:
 
    With the new OMNeT++ 5.4 release, INET supports the automatic conversion of
    non-linear units such as dBm, dBW to W, dB to ratio, etc. All 0/0 and +-1/0
-   parameter value assignments have been replaced with nan and +-inf respectively.
+   parameter value assignments have been replaced with NaN and +-inf respectively.
 
 4. Various renames
 
@@ -93,7 +93,7 @@ The highlights of this release since the last development release are:
     - LdpRouter module -> LdpMplsRouter
     - Rsvp module -> RsvpTe.
     - rsvp_te folder -> rsvpte
-    - Protoco::rsvp global variable -> rsvpte.
+    - Protocol::rsvp global variable -> rsvpte.
 
 5. Packet error representation
 
@@ -102,16 +102,16 @@ The highlights of this release since the last development release are:
    level. The parameter determines on what level the error model introduces
    errors into a packet.
 
-   In many protocols, various corruption modes don't lead to different outcome.
+   In many protocols, various corruption modes don't lead to a different outcome.
    Nevertheless, this change allows implementing IEEE 802.11 A-MPDU aggregation
-   with support to only dropping the individual subframes which are received
+   with support to only dropping the individual subframes that are received
    incorrectly.
 
 6. IEEE 802.11
 
    Thanks to Alfonso Ariza Quintana, the 802.11/ac (VHT PHY) modes have been
-   added to physical layer. Futhermore, the necessary 5GHz bands with 20, 40,
-   80, and 160 Mhz bandwidth have also been added.
+   added to the physical layer. Furthermore, the necessary 5GHz bands with 20, 40,
+   80, and 160 MHz bandwidth have also been added.
 
    The 802.11 mode lookup mechanism has been extended with bandwidth and number
    of spatial streams parameters, and the mechanism has also been relaxed to
@@ -127,20 +127,20 @@ The highlights of this release since the last development release are:
 7. Emulation
 
    The whole emulation support, including the ExternalInterface compound module,
-   the Ext simple module, and the corresponding cSocketRtScheduler have been
+   the Ext simple module, and the corresponding cSocketRtScheduler, have been
    redesigned and heavily refactored. The new C++ scheduler class is called
-   RealTimeScheduler and it is completely independent of the external interfaces.
+   RealTimeScheduler, and it is completely independent of the external interfaces.
 
-   The new scheduler still provides real time simulation execution, but it also
+   The new scheduler still provides real-time simulation execution, but it also
    allows for using the POSIX select mechanism to support I/O operations with
    file descriptors. The external interface hooks into this mechanism to read
-   raw packets via PCAP. Futhermore, the new external interface implementation
+   raw packets via PCAP. Furthermore, the new external interface implementation
    uses dedicated raw sockets to send packets.
 
 8. Lifecycle and scenario management
 
    The LifecycleController module has been removed because the module did not
-   have and is not expected to have any parameters in the future. Therefore the
+   have and is not expected to have any parameters in the future. Therefore, the
    LifecycleController module is no longer needed in the network for the lifecycle
    operations to work. The corresponding LifecycleController C++ class with the
    actual functionality remains there.
@@ -153,12 +153,12 @@ The highlights of this release since the last development release are:
 
 9. RIP
 
-   Thanks to the contributions of Mani Amoozadeh the RIP protocol has been
+   Thanks to the contributions of Mani Amoozadeh, the RIP protocol has been
    refactored to store the protocol specific route data in the routing table
    instead of an internal data structure. The protocol has also been extended
    with new hold-down timer and triggered update parameters.
 
-   Fixed sending updates on interface which is down.
+   Fixed sending updates on an interface that is down.
 
 10. Other notable changes
 
@@ -169,11 +169,11 @@ The highlights of this release since the last development release are:
 
     Several missing protocol dissectors and protocol printers have been added.
 
-    All protocol specific header serializers have been moved to the folder of their
+    All protocol-specific header serializers have been moved to the folder of their
     respective communication protocol.
 
-    In order to suppor more recent OSG Earth versions, the osgEarth::ObjectLocatorNode
+    In order to support more recent OSG Earth versions, the osgEarth::ObjectLocatorNode
     has been replaced with GeoTransform and osg::PositionAttitudeTransform.
 
 [Download INET-4.0.0](https://github.com/inet-framework/inet/releases/download/v4.0.0/inet-4.0.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2018-07-19-showcases-released.md b/_posts/2018-07-19-showcases-released.md
index c51daca..82fcc81 100644
--- a/_posts/2018-07-19-showcases-released.md
+++ b/_posts/2018-07-19-showcases-released.md
@@ -6,14 +6,14 @@ category: news
 
 INET has support for recording PCAP traces from simulations.
 The recording process produces PCAP files that are similar to
-real world PCAP traces, so one can use the same tools and
+real-world PCAP traces, so one can use the same tools and
 techniques for analyzing simulated traffic as used on real
 traffic, such as Wireshark and TCPDump. Knowledge of PCAP
 can be reused in the context of simulations.
 
-This showcase contains an example simulation, which generates
+This showcase contains an example simulation that generates
 and records PCAP traces of TCP, UDP, and ICMP traffic, using
-various physical layer protocols like ethernet and 802.11.
+various physical layer protocols like Ethernet and 802.11.
 
 Links:
-* [PCAP Recording](https://inet.omnetpp.org/docs/showcases/general/pcaprecording/doc/)
+* [PCAP Recording](https://inet.omnetpp.org/docs/showcases/general/pcaprecording/doc/)
\ No newline at end of file
diff --git a/_posts/2018-07-20-showcases-released.md b/_posts/2018-07-20-showcases-released.md
index db6528e..22ac64a 100644
--- a/_posts/2018-07-20-showcases-released.md
+++ b/_posts/2018-07-20-showcases-released.md
@@ -2,15 +2,14 @@
 layout: post
 title: MANET Routing Protocols Showcase Released
 category: news
----
 
-Most routing protocols for mobile adhoc networks (MANETs) can be categorized
+Most routing protocols for mobile ad hoc networks (MANETs) can be categorized
 as being either reactive or proactive. INET contains various routing protocols
 for MANETs from both categories, and from other categories as well.
 
 This showcase demonstrates the configuration and operation of three MANET routing
 protocols with three example simulations, using a reactive (AODV), a proactive (DSDV),
-and a location based (GPSR) routing protocol.
+and a location-based (GPSR) routing protocol.
 
 Links:
-* [MANET Routing Protocols](https://inet.omnetpp.org/docs/showcases/routing/manet/doc/)
+* [MANET Routing Protocols](https://inet.omnetpp.org/docs/showcases/routing/manet/doc/)
\ No newline at end of file
diff --git a/_posts/2018-07-27-showcases-released.md b/_posts/2018-07-27-showcases-released.md
index 0cd2027..ad6db3a 100644
--- a/_posts/2018-07-27-showcases-released.md
+++ b/_posts/2018-07-27-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: Visualizing Radio Medium Activity Showcase Released
 category: news
----
 
 INET contains support for visualizing radio signals as they
 propagate through space, making it easy to see which nodes
@@ -13,4 +12,4 @@ This showcase contains three configurations of increasing
 complexity, each showing different features of the visualization.
 
 Links:
-* [Visualizing Radio Medium Activity](https://inet.omnetpp.org/docs/showcases/routing/manet/doc/)
+* [Visualizing Radio Medium Activity](https://inet.omnetpp.org/docs/showcases/routing/manet/doc/)
\ No newline at end of file
diff --git a/_posts/2018-07-30-showcases-released.md b/_posts/2018-07-30-showcases-released.md
index c3fec8d..e524987 100644
--- a/_posts/2018-07-30-showcases-released.md
+++ b/_posts/2018-07-30-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: MAC Protocols for Wireless Sensor Networks Showcase Released
 category: news
----
 
 There are media access control (MAC) protocols designed specifically
 for wireless sensor networks. INET has several such protocol implementations,
@@ -12,4 +11,4 @@ simulations of a wireless sensor network. In Part 2, we compare the three
 protocols using statistics.
 
 Links:
-* [MAC Protocols for Wireless Sensor Networks](https://inet.omnetpp.org/docs/showcases/wireless/sensornetwork/doc/)
+* [MAC Protocols for Wireless Sensor Networks](https://inet.omnetpp.org/docs/showcases/wireless/sensornetwork/doc/)
\ No newline at end of file
diff --git a/_posts/2018-08-17-showcases-released.md b/_posts/2018-08-17-showcases-released.md
index 6649445..085aef5 100644
--- a/_posts/2018-08-17-showcases-released.md
+++ b/_posts/2018-08-17-showcases-released.md
@@ -2,10 +2,9 @@
 layout: post
 title: Differentiated Services Showcase Released
 category: news
----
 
 This showcase presents an example network that employs DiffServ to provide
 preferential service to voice over other types of traffic.
 
 Links:
-* [Differentiated Services](https://inet.omnetpp.org/docs/showcases/general/diffserv/doc/)
+* [Differentiated Services](https://inet.omnetpp.org/docs/showcases/general/diffserv/doc/)
\ No newline at end of file
diff --git a/_posts/2018-09-13-showcases-released.md b/_posts/2018-09-13-showcases-released.md
index e5ba28b..160d518 100644
--- a/_posts/2018-09-13-showcases-released.md
+++ b/_posts/2018-09-13-showcases-released.md
@@ -2,13 +2,12 @@
 layout: post
 title: Mobility Showcases Released
 category: news
----
 
 These showcases demonstrate various elementary mobility models (both in 2D and 3D)
-and how elementary mobility models (those that describe motion, position and
+and how elementary mobility models (those that describe motion, position, and
 orientation on their own) can be combined to create more complex motion patterns.
 
 Links:
 * [Mobility](https://inet.omnetpp.org/docs/showcases/mobility/basic/doc/)
 * [Combining Mobility Models](https://inet.omnetpp.org/docs/showcases/mobility/combining/doc/)
-* [3D Mobility](https://inet.omnetpp.org/docs/showcases/mobility/spatial/doc/)
+* [3D Mobility](https://inet.omnetpp.org/docs/showcases/mobility/spatial/doc/)
\ No newline at end of file
diff --git a/_posts/2018-10-04-showcases-released.md b/_posts/2018-10-04-showcases-released.md
index ea83757..de7ece3 100644
--- a/_posts/2018-10-04-showcases-released.md
+++ b/_posts/2018-10-04-showcases-released.md
@@ -12,4 +12,4 @@ canvas in a graphical form. INET supports such visualization in the
 form of inspector figures that display various gauges and meters.
 
 Links:
-* [Instrument Figures](https://inet.omnetpp.org/docs/showcases/visualizer/instrumentfigures/doc/)
+- [Instrument Figures](https://inet.omnetpp.org/docs/showcases/visualizer/instrumentfigures/doc/)
\ No newline at end of file
diff --git a/_posts/2018-10-12-showcases-released.md b/_posts/2018-10-12-showcases-released.md
index 32f43e6..6338df8 100644
--- a/_posts/2018-10-12-showcases-released.md
+++ b/_posts/2018-10-12-showcases-released.md
@@ -1,15 +1,13 @@
 ---
 layout: post
-title: Additional Visiualization Showcases Released
+title: Additional Visualization Showcases Released
 category: news
----
 
 Various new visualization showcases have been added that show how to display
-terrain and urban environment, submodule and node related information and statistics.
+terrain and urban environments, submodule and node-related information, and statistics.
 
 Links:
 * [Visualizing Network Nodes](https://inet.omnetpp.org/docs/showcases/visualizer/networknode/doc/)
 * [Visualizing Terrain and Urban Environment](https://inet.omnetpp.org/docs/showcases/visualizer/earth/doc/)
 * [Visualizing Submodule Information](https://inet.omnetpp.org/docs/showcases/visualizer/submoduleinfo/doc/)
-* [Visualizing Statistics](https://inet.omnetpp.org/docs/showcases/visualizer/statistic/doc/)
-
+* [Visualizing Statistics](https://inet.omnetpp.org/docs/showcases/visualizer/statistic/doc/)
\ No newline at end of file
diff --git a/_posts/2018-11-19-showcases-released.md b/_posts/2018-11-19-showcases-released.md
index d2e51a0..f1ef71a 100644
--- a/_posts/2018-11-19-showcases-released.md
+++ b/_posts/2018-11-19-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: Multiple Wireless Interfaces Showcase Released
 category: news
----
 
 In real life, many wireless devices have multiple radios so that
 they can communicate on multiple wireless networks simultaneously.
@@ -11,4 +10,4 @@ and Bluetooth interfaces, or a dual-band wireless router. This
 showcase demonstrates how such devices can be simulated in INET.
 
 Links:
-* [Multiple Wireless Interfaces](https://inet.omnetpp.org/docs/showcases/wireless/multiradio/doc/)
+* [Multiple Wireless Interfaces](https://inet.omnetpp.org/docs/showcases/wireless/multiradio/doc/)
\ No newline at end of file
diff --git a/_posts/2019-01-29-INET-4.1.0-released.md b/_posts/2019-01-29-INET-4.1.0-released.md
index caef39a..f37c2d9 100644
--- a/_posts/2019-01-29-INET-4.1.0-released.md
+++ b/_posts/2019-01-29-INET-4.1.0-released.md
@@ -5,26 +5,26 @@ category: news
 ---
 
 This is a new minor stable release of the INET 4.x branch. It comes with some
-backward incompatile changes, a few new features, a number of smaller improvements,
+backward incompatible changes, a few new features, a number of smaller improvements,
 and many bug fixes. This version requires OMNeT++ 5.4.1 or later.
 
 The backward incompatible changes are the following:
 
 1. The module initialization stages have been refactored. All stages with numbers
-   in their names (e.g. INITSTAGE_LINK_LAYER_2) have been removed, because their
+   in their names (e.g. INITSTAGE_LINK_LAYER_2) have been removed because their
    intended purpose was not clear, and they were often misused. Several new stages
    have been added to replace the removed stages. The new stages have names which
    express better the specific purposes they are used for (e.g. INITSTAGE_POWER,
    INITSTAGE_GROUP_MOBILITY, INITSTAGE_NETWORK_INTERFACE_CONFIGURATION).
 
    This change most likely results in compilation errors in simulation models
-   which use the affected initialization stages. It may also cause runtime errors
-   if the stage name has not been changed but its usage is slightly modified.
+   that use the affected initialization stages. It may also cause runtime errors
+   if the stage name has not been changed, but its usage is slightly modified.
 
-2. Individual protocol specific data structure fields of InterfaceEntry (e.g. the
+2. Individual protocol-specific data structure fields of InterfaceEntry (e.g., the
    ipv4Data field with type Ipv4InterfaceData stores IP address and netmask) have
    been removed and replaced with a generic API. The new API allows storing any
-   number of arbitrary protocol specific data structures in the network interface
+   number of arbitrary protocol-specific data structures in the network interface
    similarly to packet tags. All affected protocols have been updated.
 
    This change always results in compilation errors in affected simulation models.
@@ -32,73 +32,73 @@ The backward incompatible changes are the following:
 3. The old ExtInterface module (used for emulation) has been split into several
    modules. There are separate modules for using simulated network interfaces from
    the host OS, and also for using host OS network interfaces from the simulation.
-   The new external interfaces no longer rely on PCAP, they rather use host OS
-   raw sockets and TUN/TAP interfaces. Besides ethernet, the new version also
+   The new external interfaces no longer rely on PCAP; they rather use host OS
+   raw sockets and TUN/TAP interfaces. Besides Ethernet, the new version also
    provides IEEE 802.11 network interface emulation. A new external UDP protocol
    module is also added, which allows INET applications to be tested unmodified
    on real networks using the UDP protocol of the host OS.
 
-   This change results in runtime errors in simulations which use the modified
-   models. Configuration of affected simulations have to be updated.
+   This change results in runtime errors in simulations that use the modified
+   models. Configuration of affected simulations has to be updated.
 
 4. Replaced EulerAngles with Quaternion to represent orientation (and angular
    velocity, and angular acceleration) in mobility models to avoid gimbal lock
-   and ambigous state representation. Euler angles are easy for human consumption
+   and ambiguous state representation. Euler angles are easy for human consumption
    but they are generally considered a bad idea for representing 3D orientation.
 
    This change always results in compilation errors in affected simulation models.
 
 5. Moved MAC address parameters from MAC modules to the corresponding network
-   interface modules (e.g. EtherMac -> EthernetInterface). The reason is that
+   interface modules (e.g., EtherMac -> EthernetInterface). The reason is that
    MAC address really belongs to the network interface and often management or
    other network interface submodules need access to it.
 
-   This change results in runtime errors in simulations which use the modified
-   parameters. Configuration of affected simulations have to be updated.
+   This change results in runtime errors in simulations that use the modified
+   parameters. Configuration of affected simulations has to be updated.
 
 The backward compatible changes are the following:
 
 6. Many applications have been extended with support for lifecycle operations.
    Applications can be started, stopped, and crashed individually using the same
-   ScenarioManager script which is also used to control the lifecycle operations
+   ScenarioManager script, which is also used to control the lifecycle operations
    of network nodes. These applications also subclass from a common ApplicationBase.
-   Similarly to applications, network interfaces also support lifecycle operations,
+   Similarly to applications, network interfaces also support lifecycle operations;
    they can be brought down and up using the ScenarioManager.
 
-7. Two new protocol groups (for UDP and TCP) have been added which allow the
+7. Two new protocol groups (for UDP and TCP) have been added, which allow the
    identification of application protocols based on port numbers. The application
    protocols may not even be implemented in INET, yet they can still be identified
-   (e.g. when using emulation) and displayed in the Qtenv packet log window.
+   (e.g., when using emulation) and displayed in the Qtenv packet log window.
 
-8. The PacketPrinter has been extended with a new type column which contains
-   the protocol specific packet type (e.g. ECHO_REQUEST for ICMPv4). The packet
-   type is contributed by the protocol specific packet printer. This feature helps
-   understanding packet logs in Qtenv. With the new version, the printer is also
+8. The PacketPrinter has been extended with a new type column, which contains
+   the protocol-specific packet type (e.g., ECHO_REQUEST for ICMPv4). The packet
+   type is contributed by the protocol-specific packet printer. This feature helps
+   understand packet logs in Qtenv. With the new version, the printer is also
    capable of providing a reasonably good enough packet name for packets received
-   from external sources (e.g. an external network interface during emulation).
+   from external sources (e.g., an external network interface during emulation).
 
 9. Modules that provide emulation support have been extended with a new host OS
    network namespace parameter. This feature allows, for example, running multiple
-   linux BABEL daemons in their own network namespaces (with their own routing
-   tables etc.) and connecting each one to the same simulation which provides
+   Linux BABEL daemons in their own network namespaces (with their own routing
+   tables etc.) and connecting each one to the same simulation, which provides
    mobility and wireless connectivity. For another example, it allows connecting
-   multiple docker containers running in separate network namespaces again to
+   multiple Docker containers running in separate network namespaces again to
    the same simulation. Unfortunately, the network namespace feature is only
    available on Linux at the moment.
 
 10. Added two new socket classes, EthernetSocket and Ieee8022LlcSocket, which
     allow applications to directly use the link layer protocols on a particular
-    network interface. For example, an application can send and receive ethernet
+    network interface. For example, an application can send and receive Ethernet
     frames directly, bypassing network and transport layer protocols.
 
-11. Added IEEE 802.1Q VLAN tag (C tag and S tag) support to ethernet interfaces.
-    Virtual ethernet networks can be statically configured using ethernet interface
+11. Added IEEE 802.1Q VLAN tag (C tag and S tag) support to Ethernet interfaces.
+    Virtual Ethernet networks can be statically configured using Ethernet interface
     parameters of switches and hosts. Additionally, all network nodes can have
     any number of virtual network interfaces which can be configured to request
     VLAN tagging. This feature allows using multiple different virtual networks
     on the same physical network on a per application basis.
 
-12. Raphael Riebl contributed support for ether type discrimantion for IEEE 802.11p
+12. Raphael Riebl contributed support for ether type discrimination for IEEE 802.11p
     networks in the 5.9 GHz band. The new modules provide both IEEE 802.11 EPD and
     IEEE 802.11 LPD as required by the standard. The LLC module is automatically
     selected based on the opMode and band parameters.
@@ -116,7 +116,7 @@ The backward compatible changes are the following:
 14. Other notable changes
 
 - Updated a few mobility models to provide better parameterization for 3D.
-- Added ClnsAddress and ClnsAddressType from ANSA project.
+- Added ClnsAddress and ClnsAddressType from the ANSA project.
 - Added a new antenna model for rotationally symmetric antenna lobes.
 - Added linear and logarithmic antenna lobe visualization.
 - Extended IPv4 network configuration with support for configuring isolated networks.
@@ -124,4 +124,4 @@ The backward compatible changes are the following:
 - Numerous other bug fixes and small improvements.
 
 [Download INET-4.1.0](https://github.com/inet-framework/inet/releases/download/v4.1.0/inet-4.1.0-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2019-03-22-showcases-released.md b/_posts/2019-03-22-showcases-released.md
index 632b52c..2ffa0a5 100644
--- a/_posts/2019-03-22-showcases-released.md
+++ b/_posts/2019-03-22-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: IEEE 802.15.4 Smart Home Showcase Released
 category: news
----
 
 IEEE 802.15.4 is a widely used standard for wireless sensor networks.
 INET has support for simulating various IEEE 802.15.4 physical and MAC
@@ -11,4 +10,4 @@ available in INET. It contains an example simulation which features
 a wireless sensor network.
 
 Links:
-* [IEEE 802.15.4 Smart Home](https://inet.omnetpp.org/docs/showcases/wireless/ieee802154/doc/)
+* [IEEE 802.15.4 Smart Home](https://inet.omnetpp.org/docs/showcases/wireless/ieee802154/doc/)
\ No newline at end of file
diff --git a/_posts/2019-04-01-showcases-released.md b/_posts/2019-04-01-showcases-released.md
index 5149474..a12d3ea 100644
--- a/_posts/2019-04-01-showcases-released.md
+++ b/_posts/2019-04-01-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: Modeling Directional Antennas Showcase Released
 category: news
----
 
 This showcase aims to highlight the antenna models available in INET.
 The showcase contains an example simulation which demonstrates the
@@ -11,4 +10,4 @@ known antenna models, while the last one is a universal antenna
 which can model any rotationally symmetrical antenna pattern.
 
 Links:
-* [Modeling Directional Antennas](https://inet.omnetpp.org/docs/showcases/wireless/directionalantennas/doc/)
+* [Modeling Directional Antennas](https://inet.omnetpp.org/docs/showcases/wireless/directionalantennas/doc/)
\ No newline at end of file
diff --git a/_posts/2019-04-18-INET-3.6.5-released.md b/_posts/2019-04-18-INET-3.6.5-released.md
index ee9bf7d..de7e9ba 100644
--- a/_posts/2019-04-18-INET-3.6.5-released.md
+++ b/_posts/2019-04-18-INET-3.6.5-released.md
@@ -3,6 +3,7 @@ layout: post
 title: INET-3.6.5 Stable Release Available
 category: news
 ---
+
 This release contains minor bug fixes and compatibility fixes for the OMNeT++ 5.4.1
 release and for recent Linux distros. It requires OMNeT++ 5.3 or later.
 
@@ -43,4 +44,4 @@ Visualizers:
 Read the
 [what's new](https://github.com/inet-framework/inet/blob/v3.6.5/WHATSNEW) file for more detail and
 [download INET-3.6.5](https://github.com/inet-framework/inet/releases/download/v3.6.5/inet-3.6.5-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2019-07-10-showcases-released.md b/_posts/2019-07-10-showcases-released.md
index 11a1e43..ebf4725 100644
--- a/_posts/2019-07-10-showcases-released.md
+++ b/_posts/2019-07-10-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: "New 802.11 Showcases: Fragmentation, QoS, Block Acknowledgement"
 category: news
----
 
 Three new showcase examples demonstrating the IEEE 802.11 model in INET
 have been released.
diff --git a/_posts/2019-11-15-showcases-released.md b/_posts/2019-11-15-showcases-released.md
index 062151d..a7c96ec 100644
--- a/_posts/2019-11-15-showcases-released.md
+++ b/_posts/2019-11-15-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: "New Emulation Showcases: Testing a Linux Routing Daemon in a Simulated Environment; Using Simulated Applications in a Real Network"
 category: news
----
 
 ### Testing a Linux Routing Daemon in a Simulated Environment
 
diff --git a/_posts/2020-01-08-INET-4.2.0-released.md b/_posts/2020-01-08-INET-4.2.0-released.md
index 16f00f9..eb6e452 100644
--- a/_posts/2020-01-08-INET-4.2.0-released.md
+++ b/_posts/2020-01-08-INET-4.2.0-released.md
@@ -27,13 +27,13 @@ The multidimensional (in terms of space, time, and frequency) analog domain repr
 
 The new implementation is capable of representing all kinds of radio signals such as OFDM, FHSS, UWB, etc. It also allows mixing these wireless technologies arbitrarily. The new API is more flexible in terms of composition, and it allows arbitrary extensions to be combined with existing representations.
 
-The new implementation has better performance than the old one both in terms of memory usage and execution speed. Thanks to the usage of shared pointers, it scales well to large networks with a small memory footprint and is easy to maintain and use. It also has comparable execution speed to the equivalent scalar signal representation. Futhermore, it allows the visualization of the power spectral desnsity of individual signals and the transmission medium in Qtenv.
+The new implementation has better performance than the old one both in terms of memory usage and execution speed. Thanks to the usage of shared pointers, it scales well to large networks with a small memory footprint and is easy to maintain and use. It also has comparable execution speed to the equivalent scalar signal representation. Furthermore, it allows the visualization of the power spectral density of individual signals and the transmission medium in Qtenv.
 
 Simulation models which use the old C++ API will not compile, and need to be updated.
 
 The transmitter `timeGains` and `frequencyGains` NED parameters, which determine the signal power over time and frequency, have been changed in the various dimensional radio models. The new syntax is more expressive and more user friendly. The changed interpretation of these NED parameters will cause an error in existing simulations that use it.
 
-See the presentation from the OMNeT++ Community Summit 2019: https://summit.omnetpp.org/2019/assets/pdf/math.pdf
+See the presentation from the OMNeT++ Community Summit 2019: [https://summit.omnetpp.org/2019/assets/pdf/math.pdf](https://summit.omnetpp.org/2019/assets/pdf/math.pdf)
 
 ### 2. Queueing model
 
@@ -63,7 +63,7 @@ This change may result in compilation errors in existing code.
 
 ### 5. IEEE 802.11 (WiFi)
 
-The IEEE 802.11 model has been changed to have explicit modules for both the PendingQueue and the InProgressFrames. Futhermore, several submodules of the Hcf module have been moved to the Edcaf module to better reflect their usage.
+The IEEE 802.11 model has been changed to have explicit modules for both the PendingQueue and the InProgressFrames. Furthermore, several submodules of the Hcf module have been moved to the Edcaf module to better reflect their usage.
 
 Throughout the 802.11 model has also been extended with several new signals and statistics. The ACK handling mechanism in QoS mode has been fixed.
 
@@ -82,7 +82,7 @@ Several parts of the IEEE 802.11 frame have been renamed to be consistent with t
    Ieee80211CTSFrame -> Ieee80211CtsFrame
 ```
 
-Most simulations are not affected, because the external interface of the 802.11 MAC has not been changed. Nevertheless, simulations which go deeper in the direct parameterization of the 802.11 MAC submodules have to be updated.
+Most simulations are not affected because the external interface of the 802.11 MAC has not been changed. Nevertheless, simulations which go deeper into the direct parameterization of the 802.11 MAC submodules have to be updated.
 
 ### 6. Transmission medium
 
@@ -114,7 +114,7 @@ The UDP and TCP socket options have been extended with time-to-live and type-of-
 
 ### 4. Packet API
 
-The Packet API has also been extended with a `PF_ALLOW_EMPTY` flag to support returning Empty chunks. This feature makes certain algorithms easier to write, because the user doesn't have to check for `nullptr` all over the place.
+The Packet API has also been extended with a `PF_ALLOW_EMPTY` flag to support returning Empty chunks. This feature makes certain algorithms easier to write because the user doesn't have to check for `nullptr` all over the place.
 
 The `PacketDissector::ICallback` interface has been extended with a new callback called `shouldDissectProtocolDataUnit()` for the possibility to stop dissection for performance reasons.
 
@@ -126,14 +126,14 @@ The physical layer dimensional model has been extended with a new `NoiseSource`
 
 The `MediumCanvasVisualizer` has been extended with the visualization of signal power spectrums, signal power spectrograms, and signal power maps. Spectrum figures display signal power density over frequency at a given position and moment of time. Spectogram figures display signal power density over time and frequency at a given position. Power map figures display signal power density over space at a given frequency and moment of time.
 
-All three kinds of figures can be used to display a particular signal or the total power density of transmission medium. The new visualization is also capable of displaying the above for the currently transmitted or received signal automatically while simultaneously comparing it to the total interfering signals and noise using color coding. The visualization takes into account the directional selectivity of radio antennas.
+All three kinds of figures can be used to display a particular signal or the total power density of the transmission medium. The new visualization is also capable of displaying the above for the currently transmitted or received signal automatically while simultaneously comparing it to the total interfering signals and noise using color coding. The visualization takes into account the directional selectivity of radio antennas.
 
 A new "network node", called the Probe, allows the visualization of the total transmission medium power spectral density at any given location. The latest Qtenv supports dragging network nodes with `Shift + left` mouse click. This feature effectively allows the user to explore power spectral density in space by simply dragging a probe node.
 
 See the following example videos:
-https://www.youtube.com/watch?v=oyjX03MSi7s
-https://www.youtube.com/watch?v=Oi1sq23IPYs
-https://www.youtube.com/watch?v=TyYQ53hUrns
+[https://www.youtube.com/watch?v=oyjX03MSi7s](https://www.youtube.com/watch?v=oyjX03MSi7s)
+[https://www.youtube.com/watch?v=Oi1sq23IPYs](https://www.youtube.com/watch?v=Oi1sq23IPYs)
+[https://www.youtube.com/watch?v=TyYQ53hUrns](https://www.youtube.com/watch?v=TyYQ53hUrns)
 
 ### 7. Visualization of street maps
 
@@ -163,7 +163,7 @@ The User's Guide has been extended with a new chapter on the newly added queuein
 
 A new queueing model tutorial has been added. This tutorial contains very minimal explanation, it is rather provided to give a quick glance.
 
-The tutorial is available at: https://inet.omnetpp.org/docs/tutorials/queueing/doc
+The tutorial is available at: [https://inet.omnetpp.org/docs/tutorials/queueing/doc](https://inet.omnetpp.org/docs/tutorials/queueing/doc)
 
 ### 13. Other minor changes
 
@@ -171,7 +171,7 @@ The tutorial is available at: https://inet.omnetpp.org/docs/tutorials/queueing/d
 - PCAP recording has been enhanced with automatic network type detection and optional packet conversion.
 - New PRE and POST module initialization signals have been added for dynamic module creation.
 - A new WeightedHistogramRecorder has been added which records histograms using weighted double values.
-- The packet inspector has been enchanced to display the front, back, and data parts of packets separately in Qtenv. Furthermore, packet tags and data tags are also displayed in children mode.
+- The packet inspector has been enhanced to display the front, back, and data parts of packets separately in Qtenv. Furthermore, packet tags and data tags are also displayed in children mode.
 - All applications have been extended for `CreationTimeTag` to calculate end-to-end delay.
 - Several applications have been extended with ToS and DSCP parameters.
 - The `ManetRouter` has been extended with a parameterizable routingApp submodule.
@@ -188,4 +188,4 @@ The tutorial is available at: https://inet.omnetpp.org/docs/tutorials/queueing/d
 
 Numerous other bug fixes and small improvements.
 
-[Download INET-4.2.0](https://github.com/inet-framework/inet/releases/download/v4.2.0/inet-4.2.0-src.tgz) now.
+[Download INET-4.2.0](https://github.com/inet-framework/inet/releases/download/v4.2.0/inet-4.2.0-src.tgz) now.
\ No newline at end of file
diff --git a/_posts/2020-03-26-showcases-released.md b/_posts/2020-03-26-showcases-released.md
index db32711..8a21201 100644
--- a/_posts/2020-03-26-showcases-released.md
+++ b/_posts/2020-03-26-showcases-released.md
@@ -2,7 +2,6 @@
 layout: post
 title: Visualizing the Spectrum of Radio Signals Showcase Released
 category: news
----
 
 INET supports the visualization of the physical properties of radio signals in the temporal,
 spectral, and spatial dimensions in various forms. This visualization can help you understand,
@@ -10,4 +9,4 @@ for example, why a particular signal was received or not received successfully i
 of interference from other signals or noise.
 
 Links:
-* [Visualizing the Spectrum of Radio Signals](https://inet.omnetpp.org/docs/showcases/visualizer/spectrum/doc/)
+* [Visualizing the Spectrum of Radio Signals](https://inet.omnetpp.org/docs/showcases/visualizer/spectrum/doc/)
\ No newline at end of file
diff --git a/_posts/2020-03-26-showcases-released2.md b/_posts/2020-03-26-showcases-released2.md
index 1d94fc8..12b8392 100644
--- a/_posts/2020-03-26-showcases-released2.md
+++ b/_posts/2020-03-26-showcases-released2.md
@@ -19,7 +19,7 @@ INET’s 802.11 and 802.15.4 models.
 ### Crosstalk
 
 By default, 802.11 hosts and access points in INET are configured to use the same
-Wifi channel (Channel 1.) In reality, however, it is rarely the case. There are many
+Wifi channel (Channel 1). In reality, however, it is rarely the case. There are many
 Wifi networks at the same location, typically spread out on all channels (especially
 in the case of 2.4 GHz Wifi where only a few channels are available, compared to 5 GHz.) 
 Transmissions on many adjacent channels also overlap in frequency and can cause interference.
@@ -31,4 +31,4 @@ interfere with each other.
 
 Links:
 * [Coexistence of IEEE 802.11 and 802.15.4](https://inet.omnetpp.org/docs/showcases/wireless/coexistence/doc/)
-* [Crosstalk Between Adjacent IEEE 802.11 Channels](https://inet.omnetpp.org/docs/showcases/wireless/crosstalk/doc/)
+* [Crosstalk Between Adjacent IEEE 802.11 Channels](https://inet.omnetpp.org/docs/showcases/wireless/crosstalk/doc/)
\ No newline at end of file
diff --git a/_posts/2021-01-06-INET-3.7.0-released.md b/_posts/2021-01-06-INET-3.7.0-released.md
index dd00974..d9de46d 100644
--- a/_posts/2021-01-06-INET-3.7.0-released.md
+++ b/_posts/2021-01-06-INET-3.7.0-released.md
@@ -3,7 +3,7 @@ layout: post
 title: INET-3.7.0 Stable Release Available
 category: news
 ---
-This release adds an IPsec model, improves on UDPBasicApp, and contains small bug fixes. It requires OMNeT++ 5.3 or later, or OMNeT++ 6.0 Preview 9 or 10.
+This release adds an IPsec model, improves UDPBasicApp, and contains small bug fixes. It requires OMNeT++ 5.3 or later or OMNeT++ 6.0 Preview 9 or 10.
 
 IPsec:
 
@@ -12,10 +12,10 @@ The IPsec model implements basic RFC 4301 functionality: Authentication Header (
 The model does not perform actual cryptography. This was an explicit non-goal, as the purpose of the model is to study the effects of the network overhead of IPsec. As a consequence, encryption keys, certificates, and other cryptography-related data do not appear in the model's data structures. However, protocol overhead and a simple performance model to account for the runtime overhead of cryptography are included.
 
 Further limitations:
-  - Transport mode only. Tunnel mode is not supported.
-  - Multicast traffic is not supported.
-  - The anti-replay mechanism is not implemented.
-  - DSCP-based SA selection is not implemented.
+- Transport mode only. Tunnel mode is not supported.
+- Multicast traffic is not supported.
+- The anti-replay mechanism is not implemented.
+- DSCP-based SA selection is not implemented.
 
 UDPBasicApp:
 
@@ -28,7 +28,4 @@ VoIPStream:
 Other:
 - Fixed a number of (previously hidden) subtle ownership problems.
 
-Read the
-[what's new](https://github.com/inet-framework/inet/blob/v3.7.0/WHATSNEW) file for more detail and
-[download INET-3.7.0](https://github.com/inet-framework/inet/releases/download/v3.7.0/inet-3.7.0-src.tgz)
-now.
+Read the [what's new](https://github.com/inet-framework/inet/blob/v3.7.0/WHATSNEW) file for more detail and [download INET-3.7.0](https://github.com/inet-framework/inet/releases/download/v3.7.0/inet-3.7.0-src.tgz) now.
\ No newline at end of file
diff --git a/_posts/2021-01-11-INET-4.2.2-released.md b/_posts/2021-01-11-INET-4.2.2-released.md
index 25b432f..b9dbe74 100644
--- a/_posts/2021-01-11-INET-4.2.2-released.md
+++ b/_posts/2021-01-11-INET-4.2.2-released.md
@@ -3,7 +3,8 @@ layout: post
 title: INET-4.2.2 Stable Release Available
 category: news
 ---
+
 This release contains a compatibility fix to build and run properly on Windows with OMNeT++ 6 Preview 10.
 
 [Download INET-4.2.2](https://github.com/inet-framework/inet/releases/download/v4.2.2/inet-4.2.2-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2021-01-13-INET-4.3.0-released.md b/_posts/2021-01-13-INET-4.3.0-released.md
index 14fe67c..46606c5 100644
--- a/_posts/2021-01-13-INET-4.3.0-released.md
+++ b/_posts/2021-01-13-INET-4.3.0-released.md
@@ -549,4 +549,4 @@ detection and error reporting.
 Qtenv has been extended with filter expressions for the method call animation,
 which provides a better control.
 
-[Download INET-4.3.0](https://github.com/inet-framework/inet/releases/download/v4.3.0/inet-4.3.0-src.tgz) now.
+[Download INET-4.3.0](https://github.com/inet-framework/inet/releases/download/v4.3.0/inet-4.3.0-src.tgz) now.
\ No newline at end of file
diff --git a/_posts/2021-01-13-blog.md b/_posts/2021-01-13-blog.md
index 7822d85..29eed71 100644
--- a/_posts/2021-01-13-blog.md
+++ b/_posts/2021-01-13-blog.md
@@ -4,4 +4,4 @@ title: INET 4.3 with TSN support released
 category: progress
 ---
 
-We have released INET 4.3 containing Time Sensitive Network and Colck Synchronization support.
\ No newline at end of file
+We have released INET 4.3 containing Time Sensitive Network and Clock Synchronization support.
\ No newline at end of file
diff --git a/_posts/2021-04-07-INET-4.3.1-released.md b/_posts/2021-04-07-INET-4.3.1-released.md
index 78dc8af..082079a 100644
--- a/_posts/2021-04-07-INET-4.3.1-released.md
+++ b/_posts/2021-04-07-INET-4.3.1-released.md
@@ -6,4 +6,4 @@ category: news
 This release contains a compatibility fix to build and run properly on OMNeT++ 6 Preview 11.
 
 [Download INET-4.3.1](https://github.com/inet-framework/inet/releases/download/v4.3.1/inet-4.3.1-src.tgz)
-now.
+now.
\ No newline at end of file
diff --git a/_posts/2021-05-18-INET-4.3.2-released.md b/_posts/2021-05-18-INET-4.3.2-released.md
index cc743a9..b8a3b1b 100644
--- a/_posts/2021-05-18-INET-4.3.2-released.md
+++ b/_posts/2021-05-18-INET-4.3.2-released.md
@@ -7,5 +7,4 @@ These maintenance releases contain compatibility fixes for OMNeT++ 6 Preview 11.
 
 [Download INET-4.2.5](https://github.com/inet-framework/inet/releases/download/v4.2.5/inet-4.2.5-src.tgz)
 
-[Download INET-4.3.2](https://github.com/inet-framework/inet/releases/download/v4.3.2/inet-4.3.2-src.tgz)
-
+[Download INET-4.3.2](https://github.com/inet-framework/inet/releases/download/v4.3.2/inet-4.3.2-src.tgz)
\ No newline at end of file
diff --git a/_posts/2021-09-01-INET-4.3.3-released.md b/_posts/2021-09-01-INET-4.3.3-released.md
index 6d3d522..f2bdf9f 100644
--- a/_posts/2021-09-01-INET-4.3.3-released.md
+++ b/_posts/2021-09-01-INET-4.3.3-released.md
@@ -3,6 +3,7 @@ layout: post
 title: INET-4.3.3 and INET 4.2.6 Released
 category: news
 ---
+
 These maintenance releases contain compatibility fixes for OMNeT++ 6.0 Preview 12 and OMNeT++ 5.7 Preview 1 or later.
 
 We are releasing these versions in the hope that they will ease the work of migrating your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
@@ -24,5 +25,4 @@ or alternatively:
 
 [Download INET-4.2.6](https://github.com/inet-framework/inet/releases/download/v4.2.6/inet-4.2.6-src.tgz)
 
-[Download INET-4.3.3](https://github.com/inet-framework/inet/releases/download/v4.3.3/inet-4.3.3-src.tgz)
-
+[Download INET-4.3.3](https://github.com/inet-framework/inet/releases/download/v4.3.3/inet-4.3.3-src.tgz)
\ No newline at end of file
diff --git a/_posts/2021-10-15-INET-4.3.4-released.md b/_posts/2021-10-15-INET-4.3.4-released.md
index f957bd3..d6748be 100644
--- a/_posts/2021-10-15-INET-4.3.4-released.md
+++ b/_posts/2021-10-15-INET-4.3.4-released.md
@@ -5,7 +5,7 @@ category: news
 ---
 These maintenance releases contain compatibility fixes for OMNeT++ 6.0 Preview 13 and OMNeT++ 5.7.
 
-We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre13 to help migrating your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
+We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre13 to help migrate your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
 
 - INET 3.7.x: OMNeT++ 5.3 - 5.6.2
 - INET 3.8.0: OMNeT++ 5.7.0, 6.0pre13
@@ -14,18 +14,18 @@ We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre13 to h
 - INET 4.3.3: OMNeT++ 6.0pre12
 - INET 4.3.4: OMNeT++ 6.0pre13
 
-If you have a project that uses OMNeT++ 5.x and INET 3.x we recommend to migrate in several smaller steps (at least internally):
+If you have a project that uses OMNeT++ 5.x and INET 3.x, we recommend migrating in several smaller steps (at least internally):
 
 1. Migrate to OMNeT++ 5.7
 2. Migrate to INET 3.8
-3. Migrate to OMNeT++ 6.0 
+3. Migrate to OMNeT++ 6.0
 4. Migrate to INET 4.2
-5. Finally migrate to INET 4.3
+5. Finally, migrate to INET 4.3
 
-(step 3 and 4 can be done in reverse order, too)
+(Steps 3 and 4 can be done in reverse order, too)
 
 [Download INET-4.3.4](https://github.com/inet-framework/inet/releases/download/v4.3.4/inet-4.3.4-src.tgz)
 
 [Download INET-4.2.7](https://github.com/inet-framework/inet/releases/download/v4.2.7/inet-4.2.7-src.tgz)
 
-[Download INET-3.8](https://github.com/inet-framework/inet/releases/download/v3.8.0/inet-3.8.0-src.tgz)
+[Download INET-3.8](https://github.com/inet-framework/inet/releases/download/v3.8.0/inet-3.8.0-src.tgz)
\ No newline at end of file
diff --git a/_posts/2021-11-15-INET-4.3.5-released.md b/_posts/2021-11-15-INET-4.3.5-released.md
index 7045d33..cb28950 100644
--- a/_posts/2021-11-15-INET-4.3.5-released.md
+++ b/_posts/2021-11-15-INET-4.3.5-released.md
@@ -1,11 +1,12 @@
 ---
 layout: post
-title: INET-4.3.5, 4.2.8 and 3.8.1 Released
+title: INET-4.3.5, 4.2.8, and 3.8.1 Released
 category: news
 ---
+
 These maintenance releases contain compatibility fixes for OMNeT++ 6.0 Preview 14 and OMNeT++ 5.7.
 
-We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre14 to help migrating your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
+We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre14 to help migrate your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
 
 - INET 3.7.x: OMNeT++ 5.3 - 5.6.2
 - INET 3.8.1: OMNeT++ 5.7.0, 6.0pre14
@@ -15,18 +16,18 @@ We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0pre14 to h
 - INET 4.3.4: OMNeT++ 6.0pre13
 - INET 4.3.5: OMNeT++ 6.0pre14
 
-If you have a project that uses OMNeT++ 5.x and INET 3.x we recommend to migrate in several smaller steps (at least internally):
+If you have a project that uses OMNeT++ 5.x and INET 3.x, we recommend migrating in several smaller steps (at least internally):
 
 1. Migrate to OMNeT++ 5.7
 2. Migrate to INET 3.8
 3. Migrate to OMNeT++ 6.0
 4. Migrate to INET 4.2
-5. Finally migrate to INET 4.3
+5. Finally, migrate to INET 4.3
 
-(step 3 and 4 can be done in reverse order, too)
+(Steps 3 and 4 can be done in reverse order too).
 
 [Download INET-4.3.5](https://github.com/inet-framework/inet/releases/download/v4.3.5/inet-4.3.5-src.tgz)
 
 [Download INET-4.2.8](https://github.com/inet-framework/inet/releases/download/v4.2.8/inet-4.2.8-src.tgz)
 
-[Download INET-3.8.1](https://github.com/inet-framework/inet/releases/download/v3.8.1/inet-3.8.1-src.tgz)
+[Download INET-3.8.1](https://github.com/inet-framework/inet/releases/download/v3.8.1/inet-3.8.1-src.tgz)
\ No newline at end of file
diff --git a/_posts/2022-02-08-INET-4.3.7-released.md b/_posts/2022-02-08-INET-4.3.7-released.md
index a93420e..df88400 100644
--- a/_posts/2022-02-08-INET-4.3.7-released.md
+++ b/_posts/2022-02-08-INET-4.3.7-released.md
@@ -1,29 +1,30 @@
 ---
 layout: post
-title: INET-4.3.7, 4.2.9 and 3.8.2 Released
+title: INET-4.3.7, 4.2.9, and 3.8.2 Released
 category: news
 ---
+
 These maintenance releases contain compatibility fixes for OMNeT++ 6.0 Release Candidate 1 and OMNeT++ 5.7.
 
-We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0rc1 to help migrating your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
+We are releasing these versions along with OMNeT++ 5.7 and OMNeT++ 6.0rc1 to help migrate your project to OMNeT++ 6.0. Here is an OMNeT++ compatibility list for various INET versions:
 
 - INET 3.7.x: OMNeT++ 5.3 - 5.6.2
 - INET 3.8.2: OMNeT++ 5.7.0, 6.0rc1
 - INET 4.2.5: OMNeT++ 5.4.1 - 5.6.2
 - INET 4.2.9: OMNeT++ 5.7.0, 6.0rc1
 
-If you have a project that uses OMNeT++ 5.x and INET 3.x we recommend to migrate in several smaller steps (at least internally):
+If you have a project that uses OMNeT++ 5.x and INET 3.x, we recommend migrating in several smaller steps (at least internally):
 
 1. Migrate to OMNeT++ 5.7
 2. Migrate to INET 3.8
 3. Migrate to OMNeT++ 6.0
 4. Migrate to INET 4.2.9
-5. Finally migrate to INET 4.3.7 (or the master branch)
+5. Finally, migrate to INET 4.3.7 (or the master branch)
 
-(step 3 and 4 can be done in reverse order, too)
+(Steps 3 and 4 can be done in reverse order, too)
 
 [Download INET-4.3.7](https://github.com/inet-framework/inet/releases/download/v4.3.7/inet-4.3.7-src.tgz)
 
 [Download INET-4.2.9](https://github.com/inet-framework/inet/releases/download/v4.2.9/inet-4.2.9-src.tgz)
 
-[Download INET-3.8.2](https://github.com/inet-framework/inet/releases/download/v3.8.2/inet-3.8.2-src.tgz)
+[Download INET-3.8.2](https://github.com/inet-framework/inet/releases/download/v3.8.2/inet-3.8.2-src.tgz)
\ No newline at end of file
diff --git a/_posts/2022-04-29-INET-4.3.9-released.md b/_posts/2022-04-29-INET-4.3.9-released.md
index c9bb5c0..b873394 100644
--- a/_posts/2022-04-29-INET-4.3.9-released.md
+++ b/_posts/2022-04-29-INET-4.3.9-released.md
@@ -1,8 +1,9 @@
 ---
 layout: post
-title: INET-4.3.9, 4.2.10 and 3.8.3 Released
+title: INET-4.3.9, 4.2.10, and 3.8.3 Released
 category: news
 ---
+
 These maintenance releases contain compatibility fixes for OMNeT++ 6.0 and OMNeT++ 5.7.
 
 Here is an OMNeT++ compatibility list for various INET versions:
@@ -12,13 +13,13 @@ Here is an OMNeT++ compatibility list for various INET versions:
 - INET 4.2.5: OMNeT++ 5.4.1 - 5.6.2
 - INET 4.2.10: OMNeT++ 5.7.0, 6.0
 
-If you have a project that uses OMNeT++ 5.x and INET 3.x we recommend to migrate in several smaller steps (at least internally):
+If you have a project that uses OMNeT++ 5.x and INET 3.x, we recommend migrating in several smaller steps (at least internally):
 
 1. Migrate to OMNeT++ 5.7
 2. Migrate to INET 3.8
 3. Migrate to OMNeT++ 6.0
 4. Migrate to INET 4.2.10
-5. Finally migrate to INET 4.3.9 (or the master branch)
+5. Finally, migrate to INET 4.3.9 (or the master branch)
 
 (step 3 and 4 can be done in reverse order, too)
 
@@ -26,4 +27,4 @@ If you have a project that uses OMNeT++ 5.x and INET 3.x we recommend to migrate
 
 [Download INET-4.2.10](https://github.com/inet-framework/inet/releases/download/v4.2.10/inet-4.2.10-src.tgz)
 
-[Download INET-3.8.3](https://github.com/inet-framework/inet/releases/download/v3.8.3/inet-3.8.3-src.tgz)
+[Download INET-3.8.3](https://github.com/inet-framework/inet/releases/download/v3.8.3/inet-3.8.3-src.tgz)
\ No newline at end of file
diff --git a/_posts/2022-05-16-INET-4.4.0-released.md b/_posts/2022-05-16-INET-4.4.0-released.md
index 3b94a1a..36f70b8 100644
--- a/_posts/2022-05-16-INET-4.4.0-released.md
+++ b/_posts/2022-05-16-INET-4.4.0-released.md
@@ -5,12 +5,12 @@ category: news
 ---
 This is a new minor stable release of the INET 4.x branch. The highlight of this release is the implementation of several Time-Sensitive Networking (TSN) features. Also, INET is now fully licensed under LGPL.
 
-Experimental Python support has been added for running simulations concurrently and optionally on an SSH cluster. This is mostly useful for running parameter studies, automated testing and optimizing parameters.
+Experimental Python support has been added for running simulations concurrently and optionally on an SSH cluster. This is mostly useful for running parameter studies, automated testing, and optimizing parameters.
 
-There are also a number of small improvements, and several bug fixes. Some changes are backward incompatible, so existing models may need to be updated. This version requires OMNeT++ 6.0 or later.
+There are also a number of small improvements and several bug fixes. Some changes are backward incompatible, so existing models may need to be updated. This version requires OMNeT++ 6.0 or later.
 
 For a complete list of all added, removed, and changed folders, NED modules, packet chunks, packet tags, statistics, C++ classes, and signals please refer to the ChangeLog file in the src folder.
 
-For general overview see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.4.0/WHATSNEW)
+For a general overview, see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.4.0/WHATSNEW).
 
-[Download INET-4.4.0](https://github.com/inet-framework/inet/releases/download/v4.4.0/inet-4.4.0-src.tgz)
+[Download INET-4.4.0](https://github.com/inet-framework/inet/releases/download/v4.4.0/inet-4.4.0-src.tgz)
\ No newline at end of file
diff --git a/_posts/2022-06-15-tsn-released.md b/_posts/2022-06-15-tsn-released.md
index 00dffec..6e2f8e0 100644
--- a/_posts/2022-06-15-tsn-released.md
+++ b/_posts/2022-06-15-tsn-released.md
@@ -3,6 +3,7 @@ layout: post
 title: Time-Sensitive Networking (TSN) Introduced in INET
 category: news
 ---
+
 Key features of TSN were added to the INET Framework in version 4.4 (requires OMNeT++ 6.0).
 The model was developed together with an automotive industry partner to ensure relevance
 and is able to simulate the most important features of this domain. TSN refers to a set of IEEE 802 standards that make Ethernet deterministic by default. TSN components in INET are composable, making them easy to modify and experiment with. They can also be used together in non-standard novel ways, or with other tools such as external solvers for gate scheduling.
diff --git a/_posts/2022-07-27-INET-4.4.1-released.md b/_posts/2022-07-27-INET-4.4.1-released.md
index 85e1610..a4c5790 100644
--- a/_posts/2022-07-27-INET-4.4.1-released.md
+++ b/_posts/2022-07-27-INET-4.4.1-released.md
@@ -3,13 +3,14 @@ layout: post
 title: INET-4.4.1 Released
 category: news
 ---
+
 This is a minor bugfix release, mostly fixing linker errors on Windows for projects depending on INET.
 
 - Fixed #758
 - Added several INET_API markers to fix linker errors on Windows
-- Fixed duplicate symbol linker errors on Windows when using template classes as a base class. 
+- Fixed duplicate symbol linker errors on Windows when using template classes as a base class.
 - Fixed some inline method declarations.
 
-For general overview see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.4.1/WHATSNEW)
+For a general overview, see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.4.1/WHATSNEW).
 
-[Download INET-4.4.1](https://github.com/inet-framework/inet/releases/download/v4.4.1/inet-4.4.1-src.tgz)
+[Download INET-4.4.1](https://github.com/inet-framework/inet/releases/download/v4.4.1/inet-4.4.1-src.tgz)
\ No newline at end of file
diff --git a/_posts/2023-04-04-INET-4.5.0-released.md b/_posts/2023-04-04-INET-4.5.0-released.md
index 69e6e07..6fff7e5 100644
--- a/_posts/2023-04-04-INET-4.5.0-released.md
+++ b/_posts/2023-04-04-INET-4.5.0-released.md
@@ -3,12 +3,13 @@ layout: post
 title: INET-4.5.0 Released
 category: news
 ---
+
 This is a new minor stable release within the INET 4.x branch. The main feature of this release is the ability to concurrently run multiple simulations within the same process (requires OMNeT++ 7.0 preview 2 or later), along with an extended Ethernet cut-through switching functionality.
 
-There are also a number of small improvements, and several bug fixes. Some changes are backward incompatible, so existing models may need to be updated. This version requires OMNeT++ 6.0 or later.
+There are also a number of small improvements and several bug fixes. Some changes are backward incompatible, so existing models may need to be updated. This version requires OMNeT++ 6.0 or later.
 
-For a complete list of all added, removed, and changed folders, NED modules, packet chunks, packet tags, statistics, C++ classes, and signals please refer to the ChangeLog file in the src folder.
+For a complete list of all added, removed, and changed folders, NED modules, packet chunks, packet tags, statistics, C++ classes, and signals, please refer to the ChangeLog file in the src folder.
 
-For general overview see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.0/WHATSNEW)
+For a general overview, see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.0/WHATSNEW).
 
-[Download INET-4.5.0](https://github.com/inet-framework/inet/releases/download/v4.5.0/inet-4.5.0-src.tgz)
+[Download INET-4.5.0](https://github.com/inet-framework/inet/releases/download/v4.5.0/inet-4.5.0-src.tgz)
\ No newline at end of file
diff --git a/_posts/2023-08-25-INET-4.5.1-released.md b/_posts/2023-08-25-INET-4.5.1-released.md
index 3652159..8f37b0a 100644
--- a/_posts/2023-08-25-INET-4.5.1-released.md
+++ b/_posts/2023-08-25-INET-4.5.1-released.md
@@ -5,6 +5,6 @@ category: news
 ---
 This patch release resolves a Windows-specific linker error (missing symbols) that occurred when trying to build model frameworks based on INET. It was fixed by adding INET_API annotations where they were missing.
 
-For general overview see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.1/WHATSNEW)
+For a general overview, see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.1/WHATSNEW).
 
-[Download INET-4.5.1](https://github.com/inet-framework/inet/releases/download/v4.5.1/inet-4.5.1-src.tgz)
+[Download INET-4.5.1](https://github.com/inet-framework/inet/releases/download/v4.5.1/inet-4.5.1-src.tgz)
\ No newline at end of file
diff --git a/_posts/2023-08-29-INET-4.5.2-released.md b/_posts/2023-08-29-INET-4.5.2-released.md
index 38d7c98..f30477f 100644
--- a/_posts/2023-08-29-INET-4.5.2-released.md
+++ b/_posts/2023-08-29-INET-4.5.2-released.md
@@ -3,8 +3,8 @@ layout: post
 title: INET-4.5.2 Released
 category: news
 ---
-A minor patch release of INET 4.5 has been released containing several [fixes](https://github.com/inet-framework/inet/compare/v4.5.1...v4.5.2) since the 4.5.1 version.
+A minor patch release of INET 4.5 has been released, containing several [fixes](https://github.com/inet-framework/inet/compare/v4.5.1...v4.5.2) since the 4.5.1 version.
 
-For general overview see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.2/WHATSNEW)
+For a general overview, see [WHATSNEW](https://github.com/inet-framework/inet/blob/v4.5.2/WHATSNEW).
 
-[Download INET-4.5.2](https://github.com/inet-framework/inet/releases/download/v4.5.2/inet-4.5.2-src.tgz)
+[Download INET-4.5.2](https://github.com/inet-framework/inet/releases/download/v4.5.2/inet-4.5.2-src.tgz)
\ No newline at end of file
