"
Team:UCSF/Safety1
From 2013.igem.org
(Difference between revisions)
| (3 intermediate revisions not shown) | |||
| Line 174: | Line 174: | ||
} | } | ||
p1{ | p1{ | ||
| - | font-size: 1. | + | font-size: 1.5em; |
line-height: 1.2em; | line-height: 1.2em; | ||
| - | + | color: #008000; | |
font-weight: bold; | font-weight: bold; | ||
} | } | ||
| Line 213: | Line 213: | ||
#box1{ | #box1{ | ||
width: 740px; | width: 740px; | ||
| - | height: | + | height: 500px; |
background: #fffff; | background: #fffff; | ||
float: left; | float: left; | ||
| Line 515: | Line 515: | ||
<div id="leftcontenttext" style = "width: 725px;height:170px;margin-left:15px" align="justify"> | <div id="leftcontenttext" style = "width: 725px;height:170px;margin-left:15px" align="justify"> | ||
<p1>The UCSF Team safety forms were approved on 9/18/13 by David Lloyd and Julie McNamara.<br></p1> | <p1>The UCSF Team safety forms were approved on 9/18/13 by David Lloyd and Julie McNamara.<br></p1> | ||
| - | + | <br> | |
| - | < | + | <p2> |
The form was submitted by UCSF iGEM team member David Dinh and is available for download: <a href="https://static.igem.org/mediawiki/2013/d/dd/UCSF_iGEM_Basic_Safety_Form_2013.pdf">Safety Form</a>. <br> | The form was submitted by UCSF iGEM team member David Dinh and is available for download: <a href="https://static.igem.org/mediawiki/2013/d/dd/UCSF_iGEM_Basic_Safety_Form_2013.pdf">Safety Form</a>. <br> | ||
Other safety concerns and issues have been discussed on our project description pages, but these are by no means exhaustive. We welcome additional comments, so please see our contact page to reach us for any other questions or concerns. | Other safety concerns and issues have been discussed on our project description pages, but these are by no means exhaustive. We welcome additional comments, so please see our contact page to reach us for any other questions or concerns. | ||
Latest revision as of 18:06, 28 October 2013
Safety
Other safety concerns and issues have been discussed on our project description pages, but these are by no means exhaustive. We welcome additional comments, so please see our contact page to reach us for any other questions or concerns.
