chore: fix some comments

applications/panic.md

@@ -96,7 +96,7 @@ Currently a number of node operators are using other tools, such as [Grafana](ht
 
 For a more in-depth review of the team’s past experiences, go to the team’s [LinkedIn profiles](#Team-LinkedIn-Profiles) section.
 
-Dylan Galea has been involved in the development of [PANIC for Polkadot](https://github.com/SimplyVC/panic_polkadot) in both frontend and backend work. He has been part of the backend team during the implementation of the [Polkadot API server](https://github.com/SimplyVC/polkadot_api_server) and [PANIC for Cosmos](https://github.com/SimplyVC/panic_cosmos) and helped in the fulfilment of technical reviews for [PANIC for Oasis](https://github.com/SimplyVC/panic_oasis).
+Dylan Galea has been involved in the development of [PANIC for Polkadot](https://github.com/SimplyVC/panic_polkadot) in both frontend and backend work. He has been part of the backend team during the implementation of the [Polkadot API server](https://github.com/SimplyVC/polkadot_api_server) and [PANIC for Cosmos](https://github.com/SimplyVC/panic_cosmos) and helped in the fulfillment of technical reviews for [PANIC for Oasis](https://github.com/SimplyVC/panic_oasis).
 
 Guilherme Zimmermann was previously a full stack developer on the [blog](https://www.betsson.com/en/blog/) and [promotions platform](https://www.betsson.com/en/promotions) of Betsson Group. He was also involved in the [public billing module](https://www.philips.ae/healthcare/resources/landing/tasy) of Philips Healthcare as a full stack developer. His efforts are now focused on the PANIC UI together with the development of Simply VC’s open source [UI Kit](https://www.npmjs.com/package/@simply-vc/uikit).
 

applications/sarp-basic-functionality.md

@@ -12,7 +12,7 @@ This application is a response to the RFP [Static Analysis for Runtime Pallets](
 
 [Runtime Pallets](https://docs.substrate.io/learn/runtime-development/) are modules for writing the business logic of blockchains in [Substrate](https://github.com/paritytech/substrate) (a Rust framework for building blockchains). These are usually concise pieces of standalone code with relatively few dependencies and clear specifications, hence tractable targets for performing static analysis and verification. The code quality of a runtime pallet is crucial, as even minor defects can result in major exploits like DoS attacks or the stealing of funds by a malicious party. A static code analysis can help to automate the auditing processes and prevent introduction of defects throughout the software life-cycle.
 
-Therefore we would like to develop a tool - SARP (Static Analysis tool for Runtime Pallets) to perform static analysis with reasonable soundness guarantees. In particular, we would like to target vunerability classes that are detectable using dataflow analysis techniques like *tag analysis* and *taint analysis*.
+Therefore we would like to develop a tool - SARP (Static Analysis tool for Runtime Pallets) to perform static analysis with reasonable soundness guarantees. In particular, we would like to target vulnerability classes that are detectable using dataflow analysis techniques like *tag analysis* and *taint analysis*.
 
 Our team has no prior knowledge in static code analysis, but has a good understanding of substrate and Rust.
 

docs/RFPs/Static-Analysis-for-Runtime-Pallets.md

@@ -9,7 +9,7 @@ This Request for Proposals is currently considered **under development**, meanin
 
 ## Project Description :page_facing_up:  
 
-[Runtime Pallets](https://docs.substrate.io/fundamentals/runtime-development/) are modules for writing the business logic of blockchains in [Substrate](https://github.com/paritytech/polkadot-sdk/tree/master/substrate) (a Rust framework for building blockchians). These are usually concise pieces of standalone code with relatively few dependencies and clear specifications, hence tractable targets for performing static analysis and verification. We would like to develop tools and techniques to perform static analysis with reasonable soundness guarantees. In particular, we would like to target vunerability classes that are detectable using dataflow analysis techniques like *tag analysis* and *taint analysis*. Just to give a flavor, relevant might vulnerabilities include:
+[Runtime Pallets](https://docs.substrate.io/fundamentals/runtime-development/) are modules for writing the business logic of blockchains in [Substrate](https://github.com/paritytech/polkadot-sdk/tree/master/substrate) (a Rust framework for building blockchians). These are usually concise pieces of standalone code with relatively few dependencies and clear specifications, hence tractable targets for performing static analysis and verification. We would like to develop tools and techniques to perform static analysis with reasonable soundness guarantees. In particular, we would like to target vulnerability classes that are detectable using dataflow analysis techniques like *tag analysis* and *taint analysis*. Just to give a flavor, relevant might vulnerabilities include:
 * [incorrect origin](https://github.com/bhargavbh/MIRAI/blob/main/substrate_examples/incorrect-origin/description.md) of dispatchable functions. 
 * [unsigned transaction](https://github.com/bhargavbh/MIRAI/blob/main/substrate_examples/unsigned-transaction/description.md) validation.
 * tracking bad randomness: ensure bad randomness does not leak into sensitive functions.

docs/RFPs/alternative-polkadot-js-api-console.md

@@ -47,7 +47,7 @@ The following items could be the initial deliverables of the project. Of course,
 
 - Initial research:
   - study how the current javascript console is developed at https://polkadot.js.org/apps/#/js
-  - understand the libaries currently integrated from [polkadot JS API docs](https://polkadot.js.org/docs/)
+  - understand the libraries currently integrated from [polkadot JS API docs](https://polkadot.js.org/docs/)
 
 - Development:
   - design a new UI/UX with better experience than current javascript console with features like

docs/Support Docs/privacy_policy.md

@@ -99,7 +99,7 @@ Updated November 2023
    * Receive their data and have it transferred to another controller. Users have the right to receive their data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance. This provision is applicable provided that the data is processed by automated means and that the processing is based on the User's consent, on a contract which the User is part of or on pre-contractual obligations thereof.
    * Lodge a complaint. Users have the right to bring a claim before their competent data protection authority (depending on your country of residence and the applicable data protection laws – note that in certain countries you may only notify a data protection authority which may then decide to initiate legal steps based on its own discretion).
 2. Any requests to exercise User rights can be directed to the Controller through the contact details provided in this document.
-3. Where possible, the Controller will fulfil such a request of the User within the statutory applicable timeframe, unless a delay or a retention of the relevant data is permitted by law (e.g. a lack of convincing identity proof by an information requestor), is required for another valid purpose, for example, to enable the fulfilment of contractual obligations, or is covered by a valid limitation or exemption under relevant privacy or data protection regulations.
+3. Where possible, the Controller will fulfil such a request of the User within the statutory applicable timeframe, unless a delay or a retention of the relevant data is permitted by law (e.g. a lack of convincing identity proof by an information requestor), is required for another valid purpose, for example, to enable the fulfillment of contractual obligations, or is covered by a valid limitation or exemption under relevant privacy or data protection regulations.
 4. Any requests will be free of charge, provided we do not incur unexpected and inadequate costs for providing you with details of your Personal Data.
 
 ## VII. Cookies