formatting nits

fediversity.md

@@ -130,14 +130,23 @@ Economic outcomes:
 Some specific possible quantitative estimates include:
 
 1.  Developer engagement:
+
     Given that making portable services the default will need more of the open-source community to engage on this issue, we may measure for example developer engagement in social channels, support channels, issue trackers, as well as code forge metrics such as bookmarks, forks, merge requests, and third-party projects building upon our work or citing us as a source of inspiration.
+
 1.  User adoption:
+
     If our project is successful in providing a user-friendly and privacy-focused platform for digital autonomy, it could attract a significant number of users.
+
 1.  Cost savings:
+
     By promoting the use of open-source software and decentralised infrastructure, our project could lead to cost savings for public organisations.
+
 1.  Data portability:
+
     The focus on data portability could have significant benefits for users, allowing them to easily switch between online platforms and take their data with them.
+
 1.  Market disruption:
+
     If our project is successful, it could have far-reaching impacts.
     For example, if our software gains a significant share of the market, it could lead to more competition among online software services, potentially leading to improved user privacy and better options for data management.
 
@@ -145,12 +154,17 @@ There are several requirements and potential barriers that may determine whether
 Some of them are:
 
 1.  Technical challenges:
+
     As seen in our technology section, our project encompasses bridging numerous existing software packages, meaning project success depends on successfully integrating these.
+
 1.  Funding and resources:
+
     The project will require adequate funding and resources to achieve its desired outcomes and impacts.
     The project team will need to secure sufficient funding and resources to cover the costs of software development, partnerships, and promotion.
     Failure to secure adequate funding and resources may limit the project's ability to achieve its desired outcomes and impacts.
+
 1.  Competition:
+
     The project will face competition from other digital service offerings, including properietary ones and offerings oriented at self-hosting open-source projects.
     The project team will need to differentiate the platform and demonstrate its unique features and benefits.
     Failure to differentiate the platform from its competitors may limit the project's ability to achieve its desired outcomes and impacts.
@@ -167,10 +181,15 @@ We've identified multiple dissemination measures we can apply to our project in
 
 1.  Offering automated dev-ops workflows.
 1.  Ensuring external developers empowered to contribute:
+
     We want for external developers to feel empowered similar to core developers, which we aim to achieve using accessible documentation, reproducible project infrastructure, tests doubling as live documentation of our components, a module upstreamed to nixpkgs, as well as by offering a familiar interface by making our core abstraction a NixOS configuration.
+
 1.  Developing key messages:
-    We'll develop clear, concise, and compelling messaging that highlight the benefits and unique features of our project, such as the focus on **user control**, **privacy**, and **data & service portability**.
+
+    We'll develop clear, concise, and compelling messaging that highlight the benefits and unique features of our project, such as the focus on **user control**, **data protection**, and **service portability**.
+
 1.  Using multiple channels:
+
     We will be utilising a variety of channels to reach our target audiences outlined above, among which through online communities, social media, webinars, blog posts, tech conferences and press releases.
 
 Concrete examples of dissemination activities for our project will include:
@@ -180,7 +199,7 @@ Concrete examples of dissemination activities for our project will include:
 -   Creating a comprehensive user guide and knowledge base that provides detailed instructions and answers to common questions about the software, and making this guide available on the platform's website and social media channels.
 -   Hosting a webinar series that showcases the features and functionalities of our software, and provides tips and best practices for using it effectively.
 -   Participating in relevant conferences and events to raise awareness of our project and engage with potential users and partners, such as those focused on Nix, and showcasing our software in demos and presentations.
-    These will include developer events like [NixCon](https://nixcon.org), [FOSDEM](https://fosdem.org/) and [CCC Congress](https://events.ccc.de/) to inform a diverse audience of the benefits of our stack and the other NGI technology solutions we are promoting.
+    These will include developer events such as [NixCon](https://nixcon.org), [FOSDEM](https://fosdem.org/) and [CCC Congress](https://events.ccc.de/) to inform a diverse audience of the benefits of our stack and the other NGI technology solutions we are promoting.
 
 ### Communication
 
@@ -191,10 +210,13 @@ Our communication strategies are already partially integrated in the disseminati
 There are several communication strategies and measures that we will utilise during the whole lifespan of the project:
 
 1.  Developing a project website:
+
     A project website will serve as a central hub of information about our project.
     It will be used to share updates, news, publications, and other project-related information.
     The website will be designed to be accessible and user-friendly.
+
 1.  Using social media:
+
     We will reach out to Fediverse channels (e.g. Mastodon, Pixelfed, Peertube and Owncast) as well as commercial social media platforms such as BlueSky, Threads, and LinkedIn to reach a wider audience and share project-related news and updates.
     Social media are used to engage with stakeholders and respond to their queries and feedback.
     While our values may be closer aligned with the open-source social media, we will also still have use for the commercial ones to spread our message initially.
@@ -369,7 +391,7 @@ Other ethics issues
 
 As detailed in Part B, Fediversity in addition to pursuing its goals directly, will further contribute 15% of its budget to the development of related digital commons through financial support in the form of grants awarded to third parties through bi-monthly open calls for proposals.
 
-In this annexe we describe the following aspects of this financial support by detailing our approach to managing a dedicated fund supporting a series of open calls related to Fediversity:
+In this annex we describe the following aspects of this financial support by detailing our approach to managing a dedicated fund supporting a series of open calls related to Fediversity:
 
 -   Objectives and results obtained of third party financial support
 -   Specifications of third party financial support