make all links into same repo relative

Questionnaire/README.md

@@ -4,7 +4,7 @@
 
 To start the questionnaire in English, [click here] (http://tool.surveypirate.com/Survey.aspx?surveyid=25731&sp.mac=DomDcdUgTB8gwbR5uWLCIg%3d%3d)
 
-But first send your solution of the [TDD micro-exercises] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/tree/master/TDDMicroExercises).
+But first send your solution of the [TDD micro-exercises] (../TDDMicroExercises).
 
 
 
@@ -13,5 +13,5 @@ But first send your solution of the [TDD micro-exercises] (https://github.com/lu
 
 Per iniziare il questionario in Italiano, [clicca qui] (http://tool.surveypirate.com/Survey.aspx?surveyid=25808&sp.mac=yMAXSLB8yJuht8rRsJCdoA%3d%3d)
 
-Ma prima invia la tua soluzione dei [micro-esercizi di TDD] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/tree/master/TDDMicroExercises).
+Ma prima invia la tua soluzione dei [micro-esercizi di TDD] (../TDDMicroExercises).
 

README.md

@@ -2,5 +2,5 @@
 
 Here you can find:
 
--  the Coding-Dojo [Refactoring legacy code driven by tests] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/tree/master/TDDMicroExercises#readme) with source code (Java, C#, JavaScript, Python, Ruby, PHP), instructions and slides
--  the [paper] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/blob/master/Paper/mockobjects_emergingproperties.pdf?raw=true) and the [paper's presentation] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/blob/master/Slides/TDD-SOLID.pdf?raw=true)
+-  the Coding-Dojo [Refactoring legacy code driven by tests] (TDDMicroExercises#readme) with source code (Java, C#, JavaScript, Python, Ruby, PHP), instructions and slides
+-  the [paper] (Paper/mockobjects_emergingproperties.pdf?raw=true) and the [paper's presentation] (Slides/TDD-SOLID.pdf?raw=true)

TDDMicroExercises/README.md

@@ -3,7 +3,7 @@
 ## Facilitator Instructions and Coding-Dojo Agenda
 
 
-- Provide attendees with [Quick Start instructions](https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/blob/master/Slides/Quick%20Start.pdf?raw=true) to setup the IDE and load the first exercise ([here in Italian](https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/blob/master/Slides/Quick%20Start%20ITA.pdf?raw=true)); for public events consider sending in advance the code via email or providing Usb keys 
+- Provide attendees with [Quick Start instructions](../Slides/Quick%20Start.pdf?raw=true) to setup the IDE and load the first exercise ([here in Italian](../Slides/Quick%20Start%20ITA.pdf?raw=true)); for public events consider sending in advance the code via email or providing Usb keys
 
 - List the languages supported and help the attendees to organize in pairs based on they favorite language and balancing their level of expertise
 
@@ -15,7 +15,7 @@
 
 - Now it’s coding time, for 40 minutes max. Provide support and help attendees when asked.
 
-- Let attendees present their solutions and facilitate group discussions ([downlonad here the comments about the exercises for the facilitator](https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/blob/master/TDDMicroExercises.ProposedSolution/General%20comments.rtf))
+- Let attendees present their solutions and facilitate group discussions ([downlonad here the comments about the exercises for the facilitator](../TDDMicroExercises.ProposedSolution/General%20comments.rtf))
 
 - Show the proposed solution and discuss the design improvements and the refactoring steps
 
@@ -36,7 +36,7 @@ You can count about 90 minutes per exercise: you can organize a 90 minutes dojo
 
 The time required for the opening and the closing of the dojo is almost always the same. The more exercises (90 minutes sessions) you include in the dojo, the more time is available for attendees to show and discuss their solutions, for general questions and for discussing more advanced topics.
 
-Consider one facilitator per 10 attendees. Pair facilitators can help 20 attendees. 
+Consider one facilitator per 10 attendees. Pair facilitators can help 20 attendees.
 Consider that the larger the number of attendees is, the less air-time is available to every attendee to show the solution, to discuss and to ask questions.
 
 Have fun!!! And share your experiences and your learnings.
@@ -52,44 +52,44 @@ When you have some kind of test to lean on, refactor the code and make it testab
 
 Apply the unit testing style and framework you are most comfortable with. You can choose to use stubs or mocks or none at all. If you do, you are free to use the mocking tool that you prefer.
 
-#### 1. **TirePressureMonitoringSystem exercise**:  
+#### 1. **TirePressureMonitoringSystem exercise**:
 Write the unit tests for the Alarm class, refactor the code as much as you need to make the class testable.
 
 The Alarm class is designed to monitor tire pressure and set an alarm if the pressure falls outside of the expected range. The Sensor class provided for the exercise simulates the behaviour of a real tire sensor, providing random but realistic values.
 
-#### 2. **UnicodeFileToHtmTextConverter exercise**: 
+#### 2. **UnicodeFileToHtmTextConverter exercise**:
 Write the unit tests for the UnicodeFileToHtmTextConverter class, refactor the code as much as you need to make the class testable.
 
 The UnicodeFileToHtmTextConverter class is designed to reformat a plain text file for display in a browser.
 
 
-#### 3. **TicketDispenser exercise**: 
+#### 3. **TicketDispenser exercise**:
 Write the unit tests for the TicketDispenser, refactor the code as much as you need to make the class testable.
 
 The TicketDispenser class is designed to be used to manage a queuing system in a shop. There may be more than one ticket dispenser but the same ticket should not be issued to two different customers.
 
 
-#### 4. **TelemetrySystem exercise**: 
+#### 4. **TelemetrySystem exercise**:
 Write the unit tests for the TelemetryDiagnosticControls class, refactor the code as much as you need to make the class testable.
 
 The responsibility of the TelemetryDiagnosticControls class is to establish a connection to the telemetry server (through the TelemetryClient), send a diagnostic request and successfully receive the response that contains the diagnostic info. The TelemetryClient class provided for the exercise simulates the behavior of the real TelemetryClient class, and can respond with either the diagnostic information or a random sequence. The real TelemetryClient class would connect and communicate with the telemetry server via tcp/ip.
 
 ## A possible solution
 
-Here you find one of the possible solutions for the exercise and general comment to assess your solutions: [possible solutions.] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/tree/master/TDDMicroExercises.ProposedSolution#readme) 
+Here you find one of the possible solutions for the exercise and general comment to assess your solutions: [possible solutions.] (../TDDMicroExercises.ProposedSolution#readme)
 
 
 ## Share your solutions
 
-Share your solutions [here] (https://github.com/lucaminudel/TDDwithMockObjectsAndDesignPrinciples/tree/master/TDDMicroExercises.YoursSolutions#readme).
+Share your solutions [here] (../TDDMicroExercises.YoursSolutions#readme).
 
 
 ## Credits
 
 Thanks to [Emily Bache] (https://github.com/emilybache) for the Python version of the exercises, for the Scala and C++ versions of the exercises.
 Thanks to [Peter Rhys Thomas] (https://github.com/peterrhysthomas) for the porting to Java.
 Thanks to [Sam Serpoosh] (https://github.com/Sam-Serpoosh) for the porting to Ruby.
-Thanks to [Arthur Almeida] (https://github.com/arthuralmeidap) for the porting to PHP. 
+Thanks to [Arthur Almeida] (https://github.com/arthuralmeidap) for the porting to PHP.
 Thank you all !