Merge branch 'master' into master

README.md

@@ -178,7 +178,7 @@ You need to have
 
 ### Splitting tests with groups
 
-Groups can be used to group tests in a test file together. The advantage is you can avoid running long test files when you want to focus on a specific set of tests within a test file.x
+Groups can be used to group tests in a test file together. The advantage is you can avoid running long test files when you want to focus on a specific set of tests within a test file.
 
 These groups only apply to the test file, not across all test files. So for example group1 in the ballot is not related to a group1 in another test file.
 

apps/remix-ide/src/app/components/panel.ts

@@ -29,7 +29,7 @@ export class AbstractPanel extends HostPlugin {
       view: view,
       active: false,
       pinned: false,
-      class: 'plugItIn active'
+      class: 'plugItIn active pb-2'
     }
   }
 

apps/remix-ide/src/remixAppManager.js

@@ -145,7 +145,8 @@ export function isNative(name) {
     'environmentExplorer',
     'templateSelection',
     'walletconnect',
-    'contract-verification'
+    'contract-verification',
+    'popupPanel'
   ]
   return nativePlugins.includes(name) || requiredModules.includes(name) || isInjectedProvider(name) || isVM(name) || isScriptRunner(name)
 }

apps/remixdesktop/TEST.md

@@ -15,7 +15,7 @@ Executables are stored in the ./release directory. Without that executable you c
 
 This is done by running ./rundist.bash
 
-Normally when you would do a 'real' release you would package remix IDE into the distributable but for local e2e this not necessary because it will use the remix IDE that is being served.
+Normally when you would do a 'real' release you would package remix IDE into the distributable but for local e2e this is not  necessary because it will use the remix IDE that is being served.
 
 
 ```
@@ -39,7 +39,7 @@ In order to facilitate local testing nightwatch will boot the executable with th
 
 So to start testing locally 
 - run the IDE with 'yarn serve' as you would normally do.
-- build your release. You will always need to this when the Desktop app itself changes its code. 
+- build your release. You will always need to do this when the Desktop app itself changes its code. 
     - ./rundist.bash
 - in apps/remixdesktop: 
     - yarn build:e2e

libs/remix-tests/README.md

@@ -246,7 +246,7 @@ remixTests.runTestSources(contractSources: SrcIfc, versionUrl: string, usingWork
 2. `compilerConfig` - Custom compiler configuration
 * `currentCompilerUrl: URL to load compiler from`
 * `evmVersion: EVM name`
-* `optimize: set true to enable optimizartion`
+* `optimize: set true to enable optimization`
 * `usingWorker?: set true to load compiler using worker`
 * `runs: number of contract runs`
 3. `testCallback(object)` - Called each time there is a test event. 3 possible type of objects:
@@ -269,7 +269,7 @@ For more details, see parameters' type definitions [here](src/types.ts).
 
 Please feel free to open an issue or a pull request. 
 
-In case you want to add a code, do have a look to our contribution guidelnes [here](https://github.com/ethereum/remix-project/blob/master/CONTRIBUTING.md). Reach us in [Gitter](https://gitter.im/ethereum/remix) in case of any queries.
+In case you want to add a code, do have a look to our contribution guidelines [here](https://github.com/ethereum/remix-project/blob/master/CONTRIBUTING.md). Reach us in [Gitter](https://gitter.im/ethereum/remix) in case of any queries.
 
 ### License
 MIT © 2018-21 Remix Team

libs/remix-ui/run-tab/src/lib/actions/events.ts

@@ -46,7 +46,7 @@ export const setupEvents = (plugin: RunTab) => {
     setFinalContext(plugin, dispatch)
     fillAccountsList(plugin, dispatch)
     // 'contextChanged' & 'networkStatus' both are triggered on workspace & network change
-    // There is chance that pinned contracts state is overrided by othe event
+    // There is chance that pinned contracts state is overridden by other event
     // We load pinned contracts for VM environment in this event
     // and for other environments in 'networkStatus' event
     if (context.startsWith('vm')) await loadPinnedContracts(plugin, dispatch, context)

release-process.md

@@ -49,7 +49,7 @@ This command will ask for a new version.
  
 This command uses `lerna` and is solely responsible for publishing all the remix libraries. It will ask for a new version of each library. Make sure you are logged in to NPM.
 
-Once these command run successfully, the version for each remix library will be updated to latest in the libs' package.json file.
+Once these commands run successfully, the version for each remix library will be updated to latest in the libs' package.json file.
 
  - Create and merge bump PR to master
  
@@ -95,7 +95,7 @@ Publish a new release on GitHub using created tag and generate automated changel
 
 ### Part 2. Update the Remix Live
 
-Updating the `remix_live` branch latest to the `remix_beta` runs the CircleCI build which updates liver version of Remix IDE on `remix.ethereum.org`
+Updating the `remix_live` branch latest to the `remix_beta` runs the CircleCI build which updates live version of Remix IDE on `remix.ethereum.org`
 
 Use this unified command: