docs: adjust grammar

- houseclean yarn scripts

docs-new/intro/getting-started.md

@@ -6,7 +6,7 @@ Developers:
 ## How do I use this site?
 
 This is a live showcase, meaning this site is powered by actual TDS components. The interactive examples give you an idea
-of both the look-and-feel and the behaviour of the components, while the code snippets and API documentation give developers 
+of both the aesthetic and the behaviour of the components, while the code snippets and API documentation give developers
 the information needed to use the components in an application. Any edits you make to the code snippets will be immediately
 reflected in the corresponding example.
 

docs-new/intro/welcome.md

@@ -1,5 +1,5 @@
 Welcome to the TELUS Design System (TDS).
 
-TDS is a set of living guidelines that communicates our brand promise through our digital experiences. It's a holistic 
-platform that integrates documentation, guidelines and design management and that serves as single source for digital 
+TDS is a set of living guidelines that communicates our brand promise through our digital experiences. It's a holistic
+platform that integrates documentation, guidelines, and design management that serves as single source for digital
 design guidelines, code patterns and UI elements.

package.json

@@ -13,23 +13,23 @@
     "UPGRADING.md"
   ],
   "scripts": {
-    "precommit": "yarn lint && yarn test && yarn build",
-    "lint": "yarn lint:js && yarn lint:scss",
-    "lint:js": "eslint src --ext '.js,.jsx' --config config/.eslintrc.json",
-    "lint:scss": "stylelint 'src/scss/**/*.scss' --config config/.stylelintrc.json",
-    "test": "jest --config config/jest.config.js",
-    "test:watch": "yarn test -- --watch",
-    "test:u": "yarn test -- -u",
-    "test:ci": "yarn run lint && yarn run test",
-    "build": "yarn build:js && yarn build:scss && yarn build:styleguide",
     "build:js": "rollup -c config/rollup.config.js",
     "build:scss": "sh ./scripts/cp-scss.sh",
     "build:styleguide": "styleguidist build --config config/styleguide.config.js",
-    "start": "node styleguide.js",
-    "start:dev": "styleguidist server --config config/styleguide.config.js",
-    "release": "scripts/release.sh",
+    "build": "yarn build:js && yarn build:scss && yarn build:styleguide",
+    "deploy:docs": "node ./scripts/deploy-docs.js",
+    "dev": "styleguidist server --config config/styleguide.config.js",
+    "lint:js": "eslint src --ext '.js,.jsx' --config config/.eslintrc.json",
+    "lint:scss": "stylelint 'src/scss/**/*.scss' --config config/.stylelintrc.json",
+    "lint": "yarn lint:js && yarn lint:scss",
+    "precommit": "yarn lint && yarn test && yarn build",
     "release:changelog": "changelog",
-    "deploy:docs": "node ./scripts/deploy-docs.js"
+    "release": "scripts/release.sh",
+    "start": "node styleguide.js",
+    "test:ci": "yarn run lint && yarn run test",
+    "test:u": "yarn test -- -u",
+    "test:watch": "yarn test -- --watch",
+    "test": "jest --config config/jest.config.js"
   },
   "repository": {
     "type": "git",

src/components/SelectorCounter/SelectorCounter.md

@@ -29,11 +29,11 @@
 
 Customizing the incrementor and decrementor labels is a helpful way to accurately describe a Selector Counter’s controls, especially when there are more than one present on the page.
 
-The component exposes a focus() method that you can call to place the cursor in the number field.
+The component exposes a `focus()` method that you can call to place the cursor in the number field.
 
 ### Contextual prefix and suffix
 
-The contextPrefix and contextSuffix props can be used to define text that helps the user understand changes in the field’s value. For example, this code produces a field whose value is announced as “You chose [number] smartphone plans” whenever the number changes.
+The `contextPrefix` and `contextSuffix` props can be used to define text that helps the user understand changes in the field’s value. For example, this code produces a field whose value is announced as “You chose [number] smartphone plans” whenever the number changes.
 
 The contextual prefix & suffix can be used together or separately. They’re also optional - if an accessible field can be built using the standard label/description/aria markup, then use those first.