Typo fix

technical_assessment_rubric.md

@@ -7,5 +7,5 @@
 | Source Control | Has basic understanding of source control (i.e. git) and can execute basic tasks: Pull, commit, push, etc. Likely needs help when anything more advanced is necessary | Has an intermediate understanding of source control; for example, can create/move to a branch and cherry-pick, but has a more mechanical process than thorough understanding of these tasks. | Has good command of the source control tools for the company, and good understanding of the infrastructure behind it. |
 | Testing | Occasionally runs tests, seldom writes them without prompting.  Can write a test to confirm that, with standard use-case, the expected output results. Likely overlooks writing tests for edge cases | Runs tests most of the time when finishing up a project, writes basic tests to confirm expected behavior and spends some time thinking of edge cases.  Tests are likely verbose and may test for multiple things, and likely don't give the most useful information when they fail. | Consistently runs tests while developing, and writes appropriate tests concurrently.  Tests are plentiful, small, and test only one thing at a time, and give useful feedback when they fail.  Writes tests for expected use cases and thoroughly addresses possible edge cases. |
 | IDE/Tool Knowledge | Uses most basic features of the tool. Will need to look most things up in documentation. Uses GUI whenever possible. | Uses some of the shortcuts of their tools, but still needs to look things up a lot. Will not be terribly efficient, but can get around to what's needed when necessary. | Can efficiently navigate tools through shortcuts, seldom needs mouse, customizes tools for their needs confidently. |
-| Frameworks | Hasn't used the frameworks for the company before, but will walk through tutorials for them.  Will understand the most basic application shown in the tutorial, but not how to integrate that with a more complex system. | Understands, high-level, what the framework is good for, what the basic component parts are. WOuld need guidance in putting them together from scratch, but is comfortable navigating/revising existing systems.  Asks questions about implementation. | Has a good understanding of the framework, and can put component parts together themselves with  minimal assistance.  Asks good questions about value of the framework vs other tools they've explored. |
+| Frameworks | Hasn't used the frameworks for the company before, but will walk through tutorials for them.  Will understand the most basic application shown in the tutorial, but not how to integrate that with a more complex system. | Understands, high-level, what the framework is good for, what the basic component parts are. Would need guidance in putting them together from scratch, but is comfortable navigating/revising existing systems.  Asks questions about implementation. | Has a good understanding of the framework, and can put component parts together themselves with  minimal assistance.  Asks good questions about value of the framework vs other tools they've explored. |
 | Codebase Knowledge | Gets lost navigating code and identifying code causing a problem. | Has tools to identify what code needs to be revised/where code needs to be written, can navigate the system and understand the basic code layout and how the different parts of the code base work together. | Understands, before looking at the code, what changes are likely necessary for the problem at hand, and where to start.  Is able to dive in to a project and quickly understand the related parts. |