docs: add Zup I.T. company (#492)

Author: Washington Soares

docs/dom-testing-library/api-configuration.md

@@ -54,8 +54,8 @@ and related queries. Defaults to `data-testid`.
 [`getBy*`](api-queries#getby) or [`getAllBy*`](api-queries#getallby) fail. Takes
 the error message and container object as arguments.
 
-`asyncUtilTimeout`: The global timeout value in milliseconds used by `waitFor` utilities.
-Defaults to 1000ms.
+`asyncUtilTimeout`: The global timeout value in milliseconds used by `waitFor`
+utilities. Defaults to 1000ms.
 
 <!--DOCUSAURUS_CODE_TABS-->
 

docs/ecosystem-jasmine-dom.md

@@ -3,8 +3,8 @@ id: ecosystem-jasmine-dom
 title: jasmine-dom
 ---
 
-[`jasmine-dom`][gh] is a companion library for Testing Library that
-provides custom DOM element matchers for Jasmine
+[`jasmine-dom`][gh] is a companion library for Testing Library that provides
+custom DOM element matchers for Jasmine
 
 ```
 npm install --save-dev @testing-library/jasmine-dom

docs/example-react-context.md

@@ -53,7 +53,7 @@ test('NameProvider composes full name from first, last', () => {
  }
  customRender(
  <NameContext.Consumer>
- {(value) => <span>Received: {value}</span>}
+ {value => <span>Received: {value}</span>}
  </NameContext.Consumer>,
  { providerProps }
  )

docs/guide-which-query.md

@@ -58,9 +58,15 @@ const foo = container.querySelector('[data-foo="bar"]')
 ```
 
 ## Chrome extension
-Do you still have problems knowing how to use Testing Library queries? 
 
-There is a very cool Chrome extension named [Testing Playground](https://chrome.google.com/webstore/detail/testing-playground/hejbmebodbijjdhflfknehhcgaklhano/related), and it helps you find the best queries to select elements. It allows you to inspect the element hierarchies in the Chrome Developer Tools, and provides you with suggestions on how to select them, while encouraging good testing practices.
+Do you still have problems knowing how to use Testing Library queries?
+
+There is a very cool Chrome extension named
+[Testing Playground](https://chrome.google.com/webstore/detail/testing-playground/hejbmebodbijjdhflfknehhcgaklhano/related),
+and it helps you find the best queries to select elements. It allows you to
+inspect the element hierarchies in the Chrome Developer Tools, and provides you
+with suggestions on how to select them, while encouraging good testing
+practices.
 
 ## Playground
 

docs/intro.md

@@ -45,7 +45,8 @@ Testing Library encourages you to avoid testing
 [implementation details](https://kentcdodds.com/blog/testing-implementation-details)
 like the internals of a component you're testing (though it's still possible).
 [The Guiding Principles](/docs/guiding-principles) of this library emphasize a
-focus on tests that closely resemble how your web pages are interacted by the users.
+focus on tests that closely resemble how your web pages are interacted by the
+users.
 
 You may want to avoid following implementation details:
 

docs/react-testing-library/api.md

@@ -70,8 +70,8 @@ const { container } = render(<TableBody {...props} />, {
 ### `baseElement`
 
 If the `container` is specified, then this defaults to that, otherwise this
-defaults to `document.body`. This is used as the base element for the
-queries as well as what is printed when you use `debug()`.
+defaults to `document.body`. This is used as the base element for the queries as
+well as what is printed when you use `debug()`.
 
 ### `hydrate`
 

website/siteConfig.js

@@ -118,6 +118,12 @@ const users = [
  infoLink: 'https://gusto.com/',
  pinned: true,
  },
+ {
+ caption: 'Zup I.T. Innovation',
+ image: '/img/users/zup.png',
+ infoLink: 'https://www.zup.com.br/',
+ pinned: true,
+ },
  {
  caption: 'iFood',
  image: '/img/users/ifood.png',