fix: Fix identation problems and improve grammar

Author: andres-acc

testing/unit-testing-jest/docs/angular-configuration.md

@@ -1,5 +1,6 @@
 ## Angular default test configuration
-When you create a new component, directive, service, etc. The default configuration of the tests file is something like this.
+When you create a new component, directive, service, etc. The default configuration of the tests file should be something like this.
+
 ```ts
 import { ComponentFixture, TestBed } from '@angular/core/testing';
 import { ExampleComponent } from './example.component';
@@ -27,10 +28,10 @@ describe('ExampleComponent', () => {
 });
 ```
 
-This is the default configuration of a test file. As you can see, it uses a lot of what we already got on the top theory. Now let's go to understand the TestBed.
+This is the default configuration of a test file. As you can see, it uses a lot of what we already got on the top theory. Now let's understand the TestBed.
 
 ### Understanding TestBed :test_tube:
-TestBed is a utility of [Angular](https://angular.io/api/core/testing/TestBed). With this, we can configure all the environments of our tests.
+[TestBed](https://angular.io/api/core/testing/TestBed) is a utility of Angular. With this, we can configure all the environments of our tests.
 
 Configure a testing module
 With this we can set all the dependencies for our tests, for example:
@@ -39,7 +40,7 @@ TestBed.configureTestingModule(
     {
         declarations: [ ExampleComponent, OtherComponents ... ],
         imports: [ PipesModule, RouterTestingModule, OtherModules... ],
-        providers: [ ExampleService, DecimalPipe, ... ],
+        providers: [ ExampleService, DecimalPipe, OtherProviders... ],
     },
     schemas: [CUSTOM_ELEMENTS_SCHEMA],
 );
@@ -68,5 +69,4 @@ order to update the DOM with the expected information.
 
 ### But why?
 According to Angular docs: 
-> Delayed change detection is intentional and useful. It gives the tester an opportunity to inspect and change the state of the component before Angular initiates data binding and calls lifecycle hooks.
-See more information [here](https://angular.io/guide/testing-components-scenarios#detectchanges).
+> [Delayed change detection is intentional and useful. It gives the tester an opportunity to inspect and change the state of the component before Angular initiates data binding and calls lifecycle hooks.](https://angular.io/guide/testing-components-scenarios#detectchanges)

testing/unit-testing-jest/docs/getting-dom-elements.md

@@ -6,12 +6,12 @@ So, les's see how it works:
 ## Getting element
 Consider the next element
 <br>
-test.html
+``test.html``
 ```html
 <button class="btn_login" (click)="login()">Login</button>
 ```
 
-test.spec.ts
+``test.spec.ts``
 ```ts
 it('should call login function', () => {
     // as nativeElement
@@ -31,7 +31,7 @@ When using `triggerEventHandler` note that the second parameter is the actual ev
 You can see more about ```nativeElement vs debugElement``` on this [link](https://angular.io/guide/testing-components-basics), also note that in debugElement we use the css class from ```By``` to use this you need to import from ```import { By } from '@angular/platform-browser';``` an you can see more info about ```By``` on this [link](https://angular.io/api/platform-browser/By)
 
 Consider the next elements
-test.html
+``test.html``
 ```html
 <app-header-process
     [tabs]="data.tabs"
@@ -47,7 +47,7 @@ test.html
 </ul>
 ```
 To get any of this elements we can use:
-test.spec.ts
+``test.spec.ts``
 ```ts
 it('should render information', () => {
     // get component

testing/unit-testing-jest/docs/http-test.md

@@ -77,12 +77,12 @@ tests cases.
 it('return all users', (done) => {
   service.findAllUsers().subscribe((users) => {
     expect(users).toEqual(USERS);
-      done();
-    });
-    const req = controller.expectOne('api/users');
-    expect(req.request.method).toEqual('GET');
-    req.flush(USERS);
+    done();
   });
+  const req = controller.expectOne('api/users');
+  expect(req.request.method).toEqual('GET');
+  req.flush(USERS);
+});
 ```
 In this test, we subscribe to ```findAllUsers```. Then, inside we create the assertion to verify the response data. ```done()``` is used to indicate the successful finish of the subscription.
 

testing/unit-testing-jest/docs/introduction.md

@@ -1,4 +1,4 @@
-## Whats is testing? and why is important?
+## Whats is testing and why is important?
 Testing is a method to check if the code is working as expected. Testing the code helps to detect bugs on time and prevent the appearance of new bugs in the future. Also, testing gives confidence to our code. We can expect that they don't find problems in QA tests.
 
 ## Benefits

testing/unit-testing-jest/docs/issues.md

@@ -23,13 +23,13 @@ import '@angular/localize/init';
 ```
 
 ### Navigator dependency
-Sometimes, when we are testing many problems don’t let our test execute. Is so frustrating don't find a simple solution just checking the error console and understanding the problem. This is a collection of typical errors that you can get when you are testing. Hope that helps.
+Sometimes, when we are testing many problems don't let our test execute. Is so frustrating don't find a simple solution just checking the error console and understanding the problem. This is a collection of typical errors that you can get when you are testing. Hope that helps.
 
 ### Error with the navigator
 #### Issue:
 If we use the navigator router on the test files, maybe we get an error like this:
 ![error navigator](./assets/NavigatorError.png "Error");
-This means we are using a specific path to test the routing. But we aren’t declaring on the environments file.
+This means we are using a specific path to test the routing. But we aren't declaring on the environments file.
 
 For example, this component:
 ```ts
@@ -116,7 +116,7 @@ describe('ExampleComponent', () => {
     const element = fixture.debugElement.query(By.css('tag'))
     expect(element).toBeTruthy();
   });
-}
+});
 ```
 This solution came from [here](https://stackoverflow.com/questions/42656045/angular2-testing-and-resolved-data-how-to-test-ngoninit)
 

testing/unit-testing-jest/docs/spy-local.md

@@ -8,14 +8,14 @@ Component
   selector: 'app-example',
   templateUrl: `
     <div class="section" (click)="log('test')">
-        Click me
+      Click me
     </div>
   `
 })
 export class ExampleComponent {
-    log(message: string): void {
-        console.log(message); 
-    }
+  log(message: string): void {
+    console.log(message); 
+  }
 }
 ````
 
@@ -38,10 +38,10 @@ describe('ExampleComponent', () => {
     fixture.detectChanges();
   });
 
-it('Should call log function when div is clicked', () => {
+  it('Should call log function when div is clicked', () => {
     const spy = jest.spyOn(component, 'log');
     fixture.nativeElement.querySelector('.section').click();
     expect(spy).toHaveBeeCalledWith('test');
-    });
+  });
 });
 ````