Merge pull request cockroachdb#3365 from cockroachdb/copy-to-clipboard-updates

Copy to clipboard updates

Author: Jesse Seldess

v2.0/backup.md

@@ -76,6 +76,7 @@ The `BACKUP` process minimizes its impact to the cluster's performance by distri
 
 For best performance, we also recommend always starting backups with a specific [timestamp](timestamp.html) at least 10 seconds in the past. For example:
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP...AS OF SYSTEM TIME '2017-06-09 16:13:55.571516+00:00';
 ~~~
@@ -99,7 +100,7 @@ After the backup has been initiated, you can control it with [`PAUSE JOB`](pause
 ## Synopsis
 
 <div>
-{% include sql/{{ page.version.version }}/diagrams/backup.html %}
+  {% include sql/{{ page.version.version }}/diagrams/backup.html %}
 </div>
 
 {{site.data.alerts.callout_info}}The <code>BACKUP</code> statement cannot be used within a <a href=transactions.html>transaction</a>.{{site.data.alerts.end}}
@@ -132,6 +133,7 @@ Per our guidance in the [Performance](#performance) section, we recommend starti
 
 ### Backup a Single Table or View
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP bank.customers \
 TO 'gs://acme-co-backup/database-bank-2017-03-27-weekly' \
@@ -140,6 +142,7 @@ AS OF SYSTEM TIME '2017-03-26 23:59:00';
 
 ### Backup Multiple Tables
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP bank.customers, bank.accounts \
 TO 'gs://acme-co-backup/database-bank-2017-03-27-weekly' \
@@ -148,6 +151,7 @@ AS OF SYSTEM TIME '2017-03-26 23:59:00';
 
 ### Backup an Entire Database
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP DATABASE bank \
 TO 'gs://acme-co-backup/database-bank-2017-03-27-weekly' \
@@ -156,6 +160,7 @@ AS OF SYSTEM TIME '2017-03-26 23:59:00';
 
 ### Backup with Revision History<span class="version-tag">New in v2.0</span>
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP DATABASE bank \
 TO 'gs://acme-co-backup/database-bank-2017-03-27-weekly' \
@@ -166,6 +171,7 @@ AS OF SYSTEM TIME '2017-03-26 23:59:00' WITH revision_history;
 
 Incremental backups must be based off of full backups you've already created.
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP DATABASE bank \
 TO 'gs://acme-co-backup/db/bank/2017-03-29-nightly' \
@@ -175,6 +181,7 @@ INCREMENTAL FROM 'gs://acme-co-backup/database-bank-2017-03-27-weekly', 'gs://ac
 
 ### Create Incremental Backups with Revision History<span class="version-tag">New in v2.0</span>
 
+{% include copy-clipboard.html %}
 ~~~ sql
 > BACKUP DATABASE bank \
 TO 'gs://acme-co-backup/database-bank-2017-03-29-nightly' \

v2.0/experimental-audit.md

@@ -22,7 +22,7 @@ For a detailed description of exactly what is logged, see the [Audit Log File Fo
 ## Synopsis
 
 <div>
-{% include sql/{{page.version.version}}/diagrams/experimental_audit.html %}
+  {% include sql/{{page.version.version}}/diagrams/experimental_audit.html %}
 </div>
 
 ## Required Privileges
@@ -89,6 +89,7 @@ If your deployment requires particular lifecycle and access policies for audit l
 
 Let's say you have a  `customers` table that contains personally identifiable information (PII). To turn on audit logs for that table, run the following command:
 
+{% include copy-clipboard.html %}
 ~~~ sql
 ALTER TABLE customers EXPERIMENTAL_AUDIT SET READ WRITE;
 ~~~
@@ -112,6 +113,7 @@ For a more detailed example, see [SQL Audit Logging](sql-audit-logging.html).
 
 To turn off logging, issue the following command:
 
+{% include copy-clipboard.html %}
 ~~~ sql
 ALTER TABLE customers EXPERIMENTAL_AUDIT SET OFF;
 ~~~