John Feliciani

17072 Pleasant Circle

Huntington Beach, CA 92649
(562) 235-8533

Dr. Leslie Bruce

University Hall room 435
800 N. State College Boulevard
Fullerton, CA 92831

Dear Dr. Bruce,

I enrolled in this course to learn about technical writing and about what a technical writer
can achieve. Through the helpful six student learning outcomes (SLOs) you have provided,
development of clean and coherent writing has become easier to produce. The documents I have
included to showcase my abilities as a writer are my iFixit team proposal, an iFixit guide for Fan
Replacement I created, and a peer review checklist for team Tech No Logics iFixit project.
My iFixit team proposal was one of the first major tasks I worked on in the semester. The
most important and helpful aspect of the proposal was that the project was a collaboration of 5
different minds that. (SLO 6) I understood that my audience was the iFixit team and I could write
directly to them, as shown when the proposal addresses iFixit directly thanking them for their
consideration in allowing us to fix the Dell Inspiron 14z 5423 laptop they provided. (SLO 1) My
team and I reviewed the Dells Owner Manual before writing the proposal to review the help
Dell provided for their customers. (SLO 2) The proposal was not only an outline for our entire

iFixit project, but also a tool to persuade the iFixit team that we understood our assignment and
could help users of iFixit with our guides. (SLO 3) The paper was a tool that allowed us to show
iFixt why our team could create guides for their website.
I chose to include my Fan Replacement guide because the guide specifically fulfills SLOs
number 4 and 5. I understood that my audience were resourceful users of iFixit from all around
the world and with varying levels of wealth and education. (SLO 1) This also means that not
every user was a native speaker of English and therefore, I had to adjust my instruction to be
read by all users. (SLO 5) The use of markers on pictures also helped to illustrate where the steps
occurred on the device (SLO 4).
Finally, the inclusion of the peer review checklist I created for team Tech no Logic shows
my skills in rhetoric, language, and collaboration. By understanding that I was talking to my
peers, I could inform the team of the problems I had with their project in a short and informal
manner (SLO 1 & 4). I used descriptive language to communicate where the errors in the project
occurred and possible solutions when applicable (SLO 5). This peer review gave me the
opportunity to showcase my collaboration skills by giving feedback and confirming that the team
understood the problems they had in their project (SLO 6). I will continue to improve my skills
and I hope that the works I have provided demonstrate the SLOs satisfactorily.

Sincerely,
John Feliciani