feat(docs): make some instances of quasar.conf more clear that they r…

…efer to the file with this name
quasarframework · Feb 10, 2022 · 2437d97 · 2437d97
1 parent 9f8a083
commit 2437d97
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/src/pages/layout/grid/introduction-to-flexbox.md b/docs/src/pages/layout/grid/introduction-to-flexbox.md
@@ -226,7 +226,7 @@ Also check [Visibility](/style/visibility#window-width-related) Style page to se
 
 ## Flex Addons
 
-When enabled (through `quasar.conf > framework > cssAddon: true`) it provides breakpoint aware versions for all flex (and display) related CSS classes.
+When enabled (through `quasar.conf.js > framework > cssAddon: true`) it provides breakpoint aware versions for all flex (and display) related CSS classes.
 
 ::: warning
 Note that there will be a noticeable bump in CSS footprint when enabling it. So only do it if you really need it.

diff --git a/docs/src/pages/quasar-cli/developing-ssr/ssr-production-export.md b/docs/src/pages/quasar-cli/developing-ssr/ssr-production-export.md
@@ -63,7 +63,7 @@ Detailing the Object:
 {
   app,     // Expressjs app instance
 
-  port,    // process.env.PORT or quasar.conf > ssr > prodPort
+  port,    // process.env.PORT or quasar.conf.js > ssr > prodPort
 
   isReady, // Function to call returning a Promise
            // when app is ready to serve clients
@@ -120,7 +120,7 @@ export default ssrProductionExport(({ app, port, isReady }) => {
 
 ### Listen on a port
 
-This is the default option that you get when adding SSR support in a Quasar CLI project. It starts listening on the configured port (process.env.PORT or quasar.conf > ssr > prodPort).
+This is the default option that you get when adding SSR support in a Quasar CLI project. It starts listening on the configured port (process.env.PORT or quasar.conf.js > ssr > prodPort).
 
 ``` js
 // src-ssr/production-export.[js|ts]

diff --git a/docs/src/pages/quasar-cli/handling-webpack.md b/docs/src/pages/quasar-cli/handling-webpack.md
@@ -93,7 +93,7 @@ Quasar comes with a bunch of useful Webpack aliases preconfigured. You can use t
 | `assets` | /src/assets |
 | `boot` | /src/boot |
 
-Also if you configure to build with the Vue compiler version (quasar.conf > build > vueCompiler: true), `vue$` resolves to  `vue/dist/vue.esm.js`.
+Also if you configure to build with the Vue compiler version (quasar.conf.js > build > vueCompiler: true), `vue$` resolves to  `vue/dist/vue.esm.js`.
 
 ### Adding Webpack aliases
 

diff --git a/docs/src/pages/quasar-cli/quasar-conf-js.md b/docs/src/pages/quasar-cli/quasar-conf-js.md
@@ -229,7 +229,7 @@ Most used properties are:
 | onBeforeSetupMiddleware | Function | Configure the dev middlewares before webpack-dev-server applies its own config. |
 | onAfterSetupMiddleware | Function | Configure the dev middlewares after webpack-dev-server applies its own config. |
 
-Using `open` prop to open with a specific browser and not with the default browser of your OS (check [supported values](https://github.com/sindresorhus/open#options)). The `options` param described in previous link is what you should configure quasar.conf > devSever > open with. Some examples:
+Using `open` prop to open with a specific browser and not with the default browser of your OS (check [supported values](https://github.com/sindresorhus/open#options)). The `options` param described in previous link is what you should configure quasar.conf.js > devSever > open with. Some examples:
 
 ```js
 // quasar.conf.js