Edited 17_conclusion.asciidoc with Atlas code editor

17_conclusion.asciidoc

@@ -49,7 +49,7 @@ Payment channels are an abstraction that is operated by two channel partners. As
 
 Eltoo:: A proposed channel mechanism that uses input-rebinding to significantly simplify the operation of payment channels and remove the need for the penalty mechanism. It needs a new Bitcoin signature type before it can be implemented
 
-==== Opt-in End-To-End Features
+==== Opt-In End-to-End Features
 
 Point Time-Locked Contracts (PTLCs):: A different approach to HTLCs, PTLCs can increase privacy, reduce information leaked to intermediary nodes and operate more efficiently than HTLC-based channels.
 
@@ -64,7 +64,7 @@ HODL invoices:: Payments where the final HTLC is not collected, committing the s
 Onion routed message services:: The onion routing mechanism, and the underlying public key databse of nodes can be used to send data that is unrelated to payments, such as text messages or forum posts. The use of Lightning to enable paid messaging as a solution to spam posts and sybil attacks (spam) is another innovation that was implemented independently of the core protocol.
 
 [[lapps]]
-=== Lightning Applications (Lapps)
+=== Lightning Applications (LApps)
 
 While still in their infancy, we are already seeing the emergence of interesting Lightning Applications. Broadly defined as an application that uses the Lightning Protocol or a Lightning client as a component, LApps are the application layer of Lightning. LApps are being built for simple games, messaging applications, micro-services, payable-APIs, paid dispensers (eg. fuel pumps), derivative trading systems, and much more.