docs: change telus digital name to lowercase

telus · Dec 28, 2017 · f528990 · f528990
1 parent 468620f
commit f528990
Show file tree

Hide file tree

Showing 8 changed files with 8 additions and 8 deletions.
diff --git a/LICENSE.md b/LICENSE.md
@@ -1,5 +1,5 @@
 ISC License (ISC)
-Copyright 2017 TELUS Digital
+Copyright 2017 TELUS digital
 
 Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
 

diff --git a/docs/elements/intro.md b/docs/elements/intro.md
@@ -10,5 +10,5 @@ some of that pain, but do not eliminate it. In addition, CSS classes only provid
 concerns such as accessibility and interactive behaviors. Finally, CSS classes are tough to evolve, often requiring breaking 
 changes.
 
-TELUS Digital is aligned on React as the target for creating UIs. Because React makes components a first-class citizen, 
+TELUS digital is aligned on React as the target for creating UIs. Because React makes components a first-class citizen, 
 the stylesheet-first approach of TDS makes less sense. We can provide a richer TDS experience by embracing React completely.
diff --git a/guide/contributing/designer-guide.md b/guide/contributing/designer-guide.md
@@ -11,7 +11,7 @@ Design contributions should be contributed in the form of a Sketch file.
 Components that are being contributed to TDS should be in a separate sketch file, in stand-alone art boards 
 (i.e. not in a mock of a project). This will reduce the risk of any confusion of what is being supplied for contribution.
 
-Files being contributed should be clearly named according to the TELUS Digital file naming convention. And that convention
+Files being contributed should be clearly named according to the TELUS digital file naming convention. And that convention
 is....
 
 Contributed design files should be attached to the Github Issue, or if the design file is accompanying a code contribution,

diff --git a/guide/getting-started/faq.md b/guide/getting-started/faq.md
@@ -67,4 +67,4 @@ All TDS components accept most standard HTML attributes, which are helpful with
 
 ## What if I'm not using the RA?
 
-Technically, TDS is a library of React components that are bundled as transpiled ES6 modules that can be used outside of the RA. However, it is **strongly** encouraged to use it together with the RA (TELUS Digital Platform) to easily implement all of the standards that TELUS web properties need to follow and are enforced by [DRB](https://drb.telus.com).
+Technically, TDS is a library of React components that are bundled as transpiled ES6 modules that can be used outside of the RA. However, it is **strongly** encouraged to use it together with the RA (TELUS digital Platform) to easily implement all of the standards that TELUS web properties need to follow and are enforced by [DRB](https://drb.telus.com).
diff --git a/guide/getting-started/getting-started.md b/guide/getting-started/getting-started.md
@@ -1,6 +1,6 @@
 # Getting started with TDS
 
-TDS includes resources for designers and developers that are needed to build consistent user interfaces on the TELUS Digital Platform. TDS enables designers and developers to focus on solving unique application challenges, rather than having to reinvent standard interface elements.
+TDS includes resources for designers and developers that are needed to build consistent user interfaces on the TELUS digital Platform. TDS enables designers and developers to focus on solving unique application challenges, rather than having to reinvent standard interface elements.
 
 These guides assume that you are building user experiences on the Digital Platform, using the [Reference Architecture](https://github.com/telusdigital/reference-architecture), which specifies a collections of standards, tooling, and processes, specifically Sketch, JavaScript, and React.
 

diff --git a/guide/roadmap.md b/guide/roadmap.md
@@ -17,7 +17,7 @@ From the alpha and beta periods, we learned that large amounts of CSS in the glo
 at scale. CSS classes only provide look-and-feel, while missing other critical concerns such as accessibility and interactivity. 
 Finally, CSS classes do not have a straightforward evolution path, often requiring breaking changes.
 
-TELUS Digital is aligned on JavaScript and React as the target for creating rich user experiences on the web. Because React 
+TELUS digital is aligned on JavaScript and React as the target for creating rich user experiences on the web. Because React 
 makes components a first-class citizen, the CSS-first approach of TDS makes less sense. We can provide a richer 
 TDS experience by embracing React completely.
 

diff --git a/guide/standards.md b/guide/standards.md
@@ -29,7 +29,7 @@ TBD
 
 Design contributions should be contributed in the form of a Sketch file (*.sketch).
 Components and blocks that are being contributed to TDS should be in a separate sketch file, in stand-alone art boards (i.e. not in a mock of a project). This will reduce the risk of any confusion of what is being supplied for contribution.
-Files being contributed should be clearly named according to the TELUS Digital file naming convention.
+Files being contributed should be clearly named according to the TELUS digital file naming convention.
 
 ### Viewports and Grid
 

diff --git a/package.json b/package.json
@@ -42,7 +42,7 @@
     "type": "git",
     "url": "git+https://github.com/telusdigital/tds.git"
   },
-  "author": "TELUS Digital",
+  "author": "TELUS digital",
   "engines": {
     "node": ">=8"
   },