diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index af3ac72..b6eb797 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,4 +1,48 @@
 # Contributing guidelines
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** — try to reproduce it using the
+   latest `master` or development branch in the repository.
+
+3. **Isolate the problem** — create a [reduced test
+   case](http://css-tricks.com/reduced-test-cases/) and a live example.
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? What would you expect to be the outcome? All these
+details will help people to fix any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the browser/OS environment in which it occurs. If
+> suitable, include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the reduced test case
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+
 
 ## Pull Request Checklist
 
diff --git a/README.md b/README.md
index 2b398e3..d3f12c7 100755
--- a/README.md
+++ b/README.md
@@ -6,11 +6,11 @@
 ## To do list:
 - [x] Import model detection (SSD & YOLO3)
 - [x] Model Panel Detection (SSD7)
-- [ ] Model Panel Detection (YOLO3)
+- [x] Model Panel Detection (YOLO3)
 - [x] Model Soiling Fault Detection (YOLO3)
 - [x] Model Diode Fault  Detection (YOLO3)
 - [ ] Model Other Fault  Detection
-- [ ] Model Fault Panel Disconnect
+- [x] Model Fault Panel Disconnect
 - [x] Example use Trained Model
 
 
@@ -19,8 +19,8 @@
 
 * Python 3.x
 * Numpy
-* TensorFlow 1.x
-* Keras 2.x
+* TensorFlow 2.x
+* Keras 2.x (in TensorFlow)
 * OpenCV
 * Beautiful Soup 4.x
 
@@ -185,6 +185,12 @@ On folder [Result ssd7 panel](Result_ssd7_panel/) show code (jupyter notebook),
 
 ![](Result_ssd7_panel/result_ssd7_panel/DJI_0110.jpg)
 
+
+### YOLO3
+On folder [Result yolo3 panel](Result_yolo3_panel/)  weight and result of this model (mAP 86.3%).
+
+![](Result_yolo3_panel/Mision%203_DJI_0045.jpg)
+
 ## Soiling Fault Detector
 ### SSD300
 On folder [Result ssd300 fault 1](Result_ssd300_fault_1/) show code (jupyter notebook), weight and result of this model (mAP 79.5%).
@@ -206,8 +212,17 @@ On folder [Result yolo3 fault 4](Result_yolo3_fault_4/) show [history train](Res
 
 ![](Result_yolo3_fault_4/result_yolo3_fault_4/Mision%2041_DJI_0044.jpg)
 
+## Panel Disconnect Detector
+### YOLO3
+To use the detector we must only use 'panel_yolo3_disconnect.py' with the previously established form, that is:
+`python predict_yolo3_disconnect.py -c config_full_yolo_panel_infer.json -i /path/to/image/ -o /path/output/result`
+To use this model, only the yolo3_panel detector model is needed.
 
 
+![](Result_yolo3_panel/Mision%2011_DJI_0058.jpg)
+
+The idea to detect the disconnection is by calculating the luminosity of each panel, to then normalize this data and highlight the panels with a luminosity out of normality.
+
 # Contributing
 
 Contributions are welcome and will be fully credited. We accept contributions via Pull Requests on GitHub.