diff --git a/New Team Contact.md b/New Team Contact.md
new file mode 100644
index 0000000..51b00a9
--- /dev/null
+++ b/New Team Contact.md	
@@ -0,0 +1,94 @@
+# Finances
+
+Current Bank Account
+
+- Business chequing account
+- $2/month service fees
+- $140 for a cheque book
+- Pay for cheques
+- Ridiculous name
+- No e-transfer
+- No online control, only checking the account
+- No ATM
+- 2 guarantors to do anything
+- We can remove people
+
+New Bank Account
+
+- Need to be able to accept e-transfers
+- Would love to be able to e-transfer people
+- No service fees
+- Fix the name
+- Possibility for credit card
+
+## Bank Account
+
+- Clear bank account name
+- Bank account type
+- Needs e-transfer
+
+## Structure
+
+Who has access to it
+
+- Team Captain
+- Treasurer
+- Internal Affairs Officer
+- Election process (TBD)
+
+## Reimbursements
+
+- Ask lead for approval
+- Submit a purchase request
+  - What is to be purchased and from where
+  - How much they think it will cost
+  - Justification for specific purchase (someone who isn't an engineer should understand why you bought this product)
+  - Approval from lead
+    - If a lead, approval from captain
+    - If captain, approval from internal auditor or treasurer
+  - Approval and audit from captain, treasurer
+  - Purchase
+  - If possible, purchases should be made directly using the team account after approval is given
+- Submit reimbursement request
+  - Must have itemized receipt
+  - For international purchase, show charge on card (if cash, use Bank of Canada daily conversion rate on that day)
+  - Approval from captain
+  - If captain, approval from internal auditor or treasurer
+  - If you make a material purchase and this procedure is not followed, you may not be eligible for reimbursement under the discretion of the team captain, treasurer, or internal auditor.
+
+# Conflict Resolution and Termination
+
+1. All members must comply with the University Student Conduct policies
+1. Should conflicts arise, the following outlines a general process:
+   - If conflicts concerns member, brought to direct superior
+   - If conflicts concerns lead, to captain(s)
+   - If conflicts concerns captain, brought to leads
+1. The process for termination of members is as follows:
+   - Meeting with sub-team lead to address issues and resolution plan
+   - Should issues continue, a meeting with the sub-team lead and captain to address issues and resolution plan
+   - Should issues continue, a meeting of the leadership is held to discuss and vote on the offender's membership. The offender will be notified of the meeting, but shall not be present
+   - Signed document acknowledging the meeting and plan going forward is required for all meetings
+1. The process for termination of sub-team leads is as follows:
+   - A request for removal is submitted to the captain
+   - Captain will have a meeting with the sub-team lead to address issues and resolution plan
+   - A meeting with the leadership team to address issues and resolution plan
+   - Should issues continue, a meeting of the leadership is held to discuss and vote on the offender's membership. The offender will be notified of the meeting, but shall not be present
+1. The process for termination of the captain(s) is as follows:
+   - A request for removal is submitted to the internal affairs officer
+   - Leadership team will have a meeting with the captain to address issues and resolution plan
+   - Should issues continue, a meeting of the leadership is held to discuss and vote on the offender's membership. The offender will be notified of the meeting, but shall not be present
+
+# Leadership Selection
+
+## Eligibility:
+
+1. Have been a member of UCalgary Baja for a minimum of 1 academic year
+1. Demonstrate the ability to effectively cooperate in a productive and respectful manner with fellow members
+1. Demonstrate the ability to effectively cooperate in a productive and respectful manner with fellow members
+1. Display leadership, technical ability, and a willingness to learn when completing their projects
+1. Uphold and represent the teams goals and mission statement
+
+### The process for selecting leads and captain(s) is as follows:
+
+1. An expression of interest is submitted to the leadership team
+   Sub-team leads and captain(s) are selected by majority vote of the leadership team
diff --git a/README.md b/README.md
index bf16893..3134647 100644
--- a/README.md
+++ b/README.md
@@ -5,36 +5,42 @@ Developed in part by Brock
 Competition Season Written in 2024 - 2025
 
 # Subteam Sepcific
+
 Your lead will go over this later with just your sub team
+
 1. [Software](./Software/SoftwareSpecific.md)
 
 ## Overview of Whole Club
+
 Based on the 2018 Baja Charter
 
-UCalgary Baja is a performance team. We are committed to designing, building, and completing an off-road vehicle. Our intent is to develop the best vehicle possible and place it in the top 10 in competition. To achieve this goal UCalgary Baja enlists high-performing, committed and passionate individuals. 
+UCalgary Baja is a performance team. We are committed to designing, building, and completing an off-road vehicle. Our intent is to develop the best vehicle possible and place it in the top 10 in competition. To achieve this goal UCalgary Baja enlists high-performing, committed and passionate individuals.
 
 UCalgary Baja is a team comprised of students who want to expand and apply their knowledge of engineering principles and develop a skill set to aid in their development as engineers. It is important to note that UCalgary Baja does not exclusively recruit “car enthusiasts”. UCalgary Baja provides you with opportunities to realize your developmental aspirations.
 
 UCalgary Baja believes in the mantra You get out what you put in. We’re excited to have you and your unique individual skills and experience contributing to the mission of creating the best car possible. The lessons you will learn and the accomplishments you will make are up to you, and UCalgary Baja will gladly work alongside you to push you to your limits and beyond.
 
-
 ## What do you get out of Baja
+
 This is based on the 2018 Baja charter
 
 ### Camaraderie & Lasting Friendships
+
 UCalgary Baja is a team where strong, long-lasting friendships are made. This camaraderie aids in both successful teamwork and personal well-being. Outside of the workshop, team members network between classes they share with one another. As well, the team is no stranger to celebrating a hard-working day by going out together to catch a movie, grab refreshments, or even just hang out.
 
 ### Career Opportunities
+
 UCalgary Baja provides you the opportunity to network with industry professionals from numerous industries, most notably in the automotive sector with the likes of Honda, Ford Motor Company, Volvo, Cummins, and many more. Alumni from the team have established engineering careers at such companies as these.
 
-
 ## Code of Conduct
+
 Based on the 2018 Baja Charter
 
 Although this does not apply, for the most part, to the Software Subteam, these are all important, including the safety aspects.
 Safety should allow for any leave of absence or refusal of work.
 
-UCalgary Baja reserves the right to remove any team member from the team if they are not compliant with the Code of Conduct. All issues will be dealt with on a case-by-case basis. We are investing in you and are here to work with you to make you and UCalgary Baja successful. 
+UCalgary Baja reserves the right to remove any team member from the team if they are not compliant with the Code of Conduct. All issues will be dealt with on a case-by-case basis. We are investing in you and are here to work with you to make you and UCalgary Baja successful.
+
 <ol>
     <li>Safety is a core value. We care about keeping you safe! Continual negligence and disregard for safety will result in removal from the team. Safety is regarding:
     <ul>
@@ -91,6 +97,7 @@ These rules can also be superseded by governing bodies such as the government of
 Other bodies that could possibly have a say are IEEE (I triple E), the worker's Board of Alberta, Health and Safety Boards, etc.
 
 ## How do I report
+
 If you wish to report a violation of any of these rules please talk to any of the lead(s) that you feel most comfortable with or the Captain.
 
 This will be investigated promptly and action will be taken depending on the severity.
@@ -103,113 +110,134 @@ This will be investigated promptly and action will be taken depending on the sev
 It is important to note that issues and concerns in performance addressed by UCalgary Baja will be dealt with on a case-by-case basis for every member. UCalgary Baja understands that there are circumstances in life that are beyond anyone’s control and will work with you to best solve these issues. If issues continue to persist and impact your ability to fulfill your commitment to UCalgary Baja, approach us to have a discussion and we can have you reevaluate roles and responsibilities on the team.
 
 ## Roles and Expectations
+
 based upon the 2018 Baja Charter
 
 ### All Members
- - Your position on this team is a privilege, not a right.
- - All members will follow through with commitments in a timely matter or inform your Team Lead/Team Captain if you cannot. 
- - Will be present and attend meetings/workdays on time at the times specified.
- - Unless Exceptions are given either by the Software Lead or Team Captain
- - This includes an Internship program where Wednesdays are optional
- - Exams always
- - Safety always
- - Software Lead is on Internship, Wednesdays will either be optional or lead by a Senior member or Future Software Lead
- - Team members will need to be a part of all phases of your assigned project and possibly projects that you aren't part of - Design, & Coding. This ensures that mistakes, issues, and concerns are addressed ASAP and corrected accordingly. 
- - Asking questions is encouraged and is the greatest way for you to learn. Every member will be open to taking questions. If you are unable to answer a question either admit that “I don’t know”, or suggest someone who may be better qualified to answer the question. Asking questions is beneficial for both parties as it expands the asker’s knowledge base, and keeps the question recipient current with their knowledge
- - Googling the docs or Stackoverflow is a great start
+
+- Your position on this team is a privilege, not a right.
+- All members will follow through with commitments in a timely matter or inform your Team Lead/Team Captain if you cannot.
+- Will be present and attend meetings/workdays on time at the times specified.
+- Unless Exceptions are given either by the Software Lead or Team Captain
+- This includes an Internship program where Wednesdays are optional
+- Exams always
+- Safety always
+- Software Lead is on Internship, Wednesdays will either be optional or lead by a Senior member or Future Software Lead
+- Team members will need to be a part of all phases of your assigned project and possibly projects that you aren't part of - Design, & Coding. This ensures that mistakes, issues, and concerns are addressed ASAP and corrected accordingly.
+- Asking questions is encouraged and is the greatest way for you to learn. Every member will be open to taking questions. If you are unable to answer a question either admit that “I don’t know”, or suggest someone who may be better qualified to answer the question. Asking questions is beneficial for both parties as it expands the asker’s knowledge base, and keeps the question recipient current with their knowledge
+- Googling the docs or Stackoverflow is a great start
 
 ### Juniors
- - Are expected to work and ask questions. Enthusiasm to learn and a positive attitude is a must!
-### Intermediates
- - In addition to Junoir Member roles and expectations:
- - Expected to carry out some of their own research and ask whatever questions they may have about their project. They may not necessarily know everything about the language/project but must make an effort to verse themselves as completely as they can.
- - Can Volunteer to teach Juniors and other members new skills and assist in the transfer of knowledge.
- - A Developmental level amount of time management to ensure adequate research and development of your design projects is a must.
+
+- Are expected to work and ask questions. Enthusiasm to learn and a positive attitude is a must!
+
+### Intermediates (remove if wanted)
+
+- In addition to Junior Member roles and expectations:
+- Expected to carry out some of their own research and ask whatever questions they may have about their project. They may not necessarily know everything about the language/project but must make an effort to verse themselves as completely as they can.
+- Can Volunteer to teach Juniors and other members new skills and assist in the transfer of knowledge.
+- A Developmental level amount of time management to ensure adequate research and development of your design projects is a must.
+
 ### Seniors
- - In addition to Intermediate Member roles and expectations:
- - Expected to carry out their own research and ask whatever questions they may have about their project. They may not necessarily know everything about the language/project but must make an effort to verse themselves as completely as they can.
- - Are expected to be able to take on more challenging design projects on the vehicle.
- - Effective time management to ensure adequate research and development of your design projects is a must.
- - During each season, must be willing to teach Juniors and other members new skills and assist in a transfer of knowledge.
- - Can request a member be reassigned to another group
- - Must check in regularly with everyone in their group to ensure they are learning and making progress on a weekly or bi-weekly basis. 
- - Reports will also be conducted by the team lead
+
+- In addition to Intermediate Member roles and expectations:
+- Expected to carry out their own research and ask whatever questions they may have about their project. They may not necessarily know everything about the language/project but must make an effort to verse themselves as completely as they can.
+- Are expected to be able to take on more challenging design projects on the vehicle.
+- Effective time management to ensure adequate research and development of your design projects is a must.
+- During each season, must be willing to teach Juniors and other members new skills and assist in a transfer of knowledge.
+- Can request a member be reassigned to another group
+- Must check in regularly with everyone in their group to ensure they are learning and making progress on a weekly or bi-weekly basis.
+- Reports will also be conducted by the team lead
 
 ### Team Leads
- - In addition to Senior Member roles and expectations:
- - Are responsible for all members, projects, components, and hardware within their system. If progress is not being made, it is their responsibility to work with the designer/programmer to ensure timelines are met. 
- - May assign and reassign projects as they see fit. 
- - Must empower, guide, and facilitate their members learning and projects. 
- - Must check in regularly with everyone on their system team to ensure they are learning and making progress on a weekly or bi-weekly basis. 
- - Enforce with encouragement what teammates are learning and provide insight on their designs. 
- - Will work alongside their future lead. This does not mean offloading your workload to the future lead as a means to shy away from Baja's responsibilities and commitments. 
- - Expected to be the final decision maker regarding any project within their system.
- - The Software lead will be in consistent contact with Senior members to ensure that a project is running smoothly.
- - Team leads will be in consistent contact with one another (primarily Electrical and Business) to ensure designs housed/shared by systems are working in tandem.
+
+- In addition to Senior Member roles and expectations:
+- Are responsible for all members, projects, components, and hardware within their system. If progress is not being made, it is their responsibility to work with the designer/programmer to ensure timelines are met.
+- May assign and reassign projects as they see fit.
+- Must empower, guide, and facilitate their members learning and projects.
+- Must check in regularly with everyone on their system team to ensure they are learning and making progress on a weekly or bi-weekly basis.
+- Enforce with encouragement what teammates are learning and provide insight on their designs.
+- Will work alongside their future lead. This does not mean offloading your workload to the future lead as a means to shy away from Baja's responsibilities and commitments.
+- Expected to be the final decision maker regarding any project within their system.
+- The Software lead will be in consistent contact with Senior members to ensure that a project is running smoothly.
+- Team leads will be in consistent contact with one another (primarily Electrical and Business) to ensure designs housed/shared by systems are working in tandem.
 
 ### Future Team Leads
- - In addition to Senior Member roles and expectations:
- - Work alongside their team lead to learn how to manage the system team 
- - Act to the best of their ability to aid and advise the system team lead concerning current and future work and tasks to be done
- - Act to the best of their ability to provide design insight to fellow system teammates under the direction of his or her system lead 
 
+- In addition to Senior Member roles and expectations:
+- Work alongside their team lead to learn how to manage the system team
+- Act to the best of their ability to aid and advise the system team lead concerning current and future work and tasks to be done
+- Act to the best of their ability to provide design insight to fellow system teammates under the direction of his or her system lead
 
 ## Seasons
+
 There are multiple phases throughout the year. As UCalgary Baja is a competition team focused on performing well all members are expected to have full involvement in each phase. The Baja year can be broken down into the following cycle (It is important to note that each phase may feather into one another):
 
 Timelines in Software are flexible this is a guide to the year not a set in stone, some project scopes may take longer than others.
 
 ### 2025 Season Edit **Mech/Electrical**
+
 This year the school has reduced the nubmer of shop tech hours and removed many alot of the shop time in favor of a class, this mean that everyone is under crunch and we only get a limited amount of time, limited number of people we can train to work in the machine and one designated cnc machine that must be used or we lose it
 
 ### Summer - Testing **Mech/Electrical**
+
 This is when UCalgary Baja tests the previous vehicle to influence designs for the future vehicle. Testing consists of gathering data from the previous vehicle to influence design decisions for the new vehicle. Such tests may include strain gauge impact testing, vehicle roll testing, transmission dynamometer characterization, etc.
 
 #### Summer Semster 2025 Season Edit **Mech/Electrical**
+
 The new car designs start here, we need something for Fall to be made. This does not mean summer testing cant happen at the same time but rather creating something for the Fall manufacting timeslot is more important.
 
 ### Summer - Testing **Software**
+
 The software could get involved in this time, this time should primarily be used for the setup/preparation for the new season, recruitment period, and any SSAF requests and allowing for the new lead to get situated and plan the projects for the year, this time also allows the old lead to mentor as well as they can the new lead.
 This is a time where a break can be taken such as only meeting every second week.
 
 ### Fall Semster 2025 Season Edit **Whole Team**
+
 A number of deliverables get done
+
 1. SSAF funding for the main manufacturing period (Winter Semster)
 1. Recuitment
 
-
 ### Fall Semester - Design **Mech/Electrical**
+
 The design period involves brainstorming, drafts, CAD modelling, design reviews, system collaboration, document creation, drawing submission, hardware sourcing, material sourcing and manufacture sourcing for all projects.
 
-
 #### Fall Semster 2025 Season Edit **Mech/Electrical**
+
 For fall this means that as much manufacting as possible happens here, any finished designs are manufactured by the new (and forced upon) manufacting group/team, this happens at the same time as designs are being made/CADed.
 
 New members of the manufacting group are trained during this time, the number of new people is determined by the university/machine shop and then is selected based upon commitment and free time during the week (sorry we this sometimes happens to be the only times available for us to get into the shop)
 
 ### Fall Semester - Easier Projects **Software**
+
 This is the time when either your first or the easier projects happen, typically the projects involve higher-level languages like Python, JavaScript, HTML, CSS or high-level programming where the background level is low, it should be typically reserved for learning opportunities even if the club needs the tool.
 This is a time for learning and enforcing good programming rules.
 Recruitment also happens during this time which reduces the amount of time able to be spent on complex projects.
 
-
 ### Winter Semester - Fabrication **Mech/Electrical**
+
 Time to get your hands dirty! Fabrication is when the car is built and parts are submitted to machine shops. Learn to use tools and understand the importance of designing for manufacturability. This period provides the opportunity to learn the most about the vehicle, how its projects and systems work together, and assemble a vehicle!
 
 #### Winter Semster 2025 Season Edit **Mech/Electrical**
+
 Not much changes here other than the manufacting team is in full swing, anything else that is made outside of the machine shop goes on as normal.
 
 ### Winter Semester - Harder Projects **Software**
+
 The concepts learned from the fall semester are now built upon in more difficult tasks such as testing (boundary, inner whatever the lead decides is appropriate to accomplish)
 This time can also be spent wrapping up easier projects, possibly continuing on with projects that were originally thought to be easy but instead turned out to be difficult
 
 ### Late Winter to Early Spring - Pre-Competition Testing **Mech/Electrical**
+
 In this phase, tests will be performed to validate the new vehicle’s designs. Examples of tests performed are torsion tests, locating center-of-gravity, impact testing, transmission dynamometer, etc.
 
 #### Late Winter to Early Spring 2025 Season Edit **Mech/Electrical**
+
 Normally this is our crunch time, please expect to spend up to 13 hours a day on Baja. This does not mean school comes second, this is just meant to inform you
 
 ### Late Winter to Early Spring **Software**
+
 No changes from the start of the Winter Semester
 The addition of the Online Cost Report is the responsibility of the lead and senior members collaborating with electrical members.
 Rules for software as of the 2025 season
@@ -220,12 +248,15 @@ If any data collection system is on the car it must be included then a software
 **We do not go to comp if no SSAF travel fund is completed**
 
 ### Just Before Competition - Vehicle Tuning & Driver Training **Mech/Electrical**
+
 Vehicle tuning consists of testing and recording multiple setups of the drivetrain, suspension, and braking systems. This allows the team to find the best settings for each event the vehicle will come up against. Alongside tuning, drivers who prove themselves as confident, comfortable, and skilled in the driver’s seat will be chosen to drive specific events at the competition. Efforts will be taken to emulate events and train drivers accordingly.
 
 ### Just Before Competition 2025 Season Edit **Whole Team**
+
 A SSAF funding round happeens so that we get buy things for the Fall Semster manufacturing period
 
 ### Just Before Competition **Software**
+
 If reasonable Software transforms into the tool fetchers if work is behind
 
 Other tasks include cleaning the truck (with a shop vac) cleaning the trailer (sweeping dirt out) and removing any garbage from the truck and trailer.
@@ -237,11 +268,12 @@ Reasonable is no juniors or other members available to perform this task.
 The highest priority is to get the car out the door.
 
 ### May to June - Competition
-The moment we’ve all been waiting for! Competition is where all your blood, sweat, and tears invested in the vehicle pay off. It is the ultimate testament to what the vehicle was designed to do. The competition consists of static events (business and design presentations), dynamic events (acceleration, maneuverability, hill climb, suspension & traction, and rock crawl), and finally a 4-hour endurance race. 
+
+The moment we’ve all been waiting for! Competition is where all your blood, sweat, and tears invested in the vehicle pay off. It is the ultimate testament to what the vehicle was designed to do. The competition consists of static events (business and design presentations), dynamic events (acceleration, maneuverability, hill climb, suspension & traction, and rock crawl), and finally a 4-hour endurance race.
 
 ### May to June - Competition **Software**
-We help where we can, that could be running the sim for the driver, fetching tools (hence why the previous phase), taking photos, helping businesses, helping where you can
 
+We help where we can, that could be running the sim for the driver, fetching tools (hence why the previous phase), taking photos, helping businesses, helping where you can
 
 ### Repeat
 
diff --git a/Software/SoftwareFnStandards.md b/Software/SoftwareFnStandards.md
index 8ceaf31..817e1b5 100644
--- a/Software/SoftwareFnStandards.md
+++ b/Software/SoftwareFnStandards.md
@@ -87,6 +87,28 @@ function exampleFunct2(inputVar) {
 
 ### Svelte/SvelteKit
 
+```html
+<script>
+	// imports, runes and javascript/typescript functions
+	let { exampleProp } = $props();
+	let exmapleState = $state(intialValue);
+	let exampleDerivedState = $derived(exampleState + exampleProp);
+</script>
+
+<p>Html tags go here</p>
+<div>{exmapleDerivedState}</div>
+
+<style>
+	div {
+		/* scoped stying (only effects the tags in this .svelte file) */
+	}
+	p {
+		margin: 0px;
+		padding: 0px;
+	}
+</style>
+```
+
 <!-- svelte is not a default preview -->
 
 ```html