Skip to content

Commit

Permalink
🔧 chore(layout.tsx): Fixed incorrect docs that still said u-hide rath…
Browse files Browse the repository at this point in the history
…er than u-none
  • Loading branch information
Spiderpig86 committed Jan 16, 2021
1 parent 50175b6 commit e3b8b37
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion cirrus-docs-next/layouts/default/layout.tsx
Expand Up @@ -47,7 +47,7 @@ export const DefaultLayout = ({ children, ...rest }: any) => {
<Header extraClasses="header--docs-theme" rightNavChildren={rightNavChildren} />
<div className="default-layout tree-nav-body mx-auto mb-0">
<div className="tree-nav-header u-items-center">
<a href="#sidebar" className="u-hide-tablet u-shadow-none">
<a href="#sidebar" className="u-none-tablet u-shadow-none">
<span className="icon">
<FontAwesomeIcon className="fa-wrapper small" icon={['fas', 'chevron-right']} />
</span>
Expand Down
12 changes: 6 additions & 6 deletions cirrus-docs-next/src/fundamentals/viewports/index.tsx
Expand Up @@ -224,47 +224,47 @@ export const ViewportsPage: React.FC<any> = (props) => {
<tbody>
<tr>
<td>
<code>u-hide-xs</code>
<code>u-none-xs</code>
</td>
<td>
Hide content for widths below <code>640px</code>.
</td>
</tr>
<tr>
<td>
<code>u-hide-sm</code>
<code>u-none-sm</code>
</td>
<td>
Hide content for widths <code>641px</code> and above.
</td>
</tr>
<tr>
<td>
<code>u-hide-sm-only</code>
<code>u-none-sm-only</code>
</td>
<td>
Hide content for widths between <code>641px</code> and <code>768px</code>.
</td>
</tr>
<tr>
<td>
<code>u-hide-md</code>
<code>u-none-md</code>
</td>
<td>
Hide content for widths <code>768px</code> and above.
</td>
</tr>
<tr>
<td>
<code>u-hide-md-only</code>
<code>u-none-md-only</code>
</td>
<td>
Hide content for widths between <code>768px</code> and <code>1023px</code>.
</td>
</tr>
<tr>
<td>
<code>u-hide-lg</code>
<code>u-none-lg</code>
</td>
<td>
Hide content for <code>1024px</code> and above.
Expand Down

0 comments on commit e3b8b37

Please sign in to comment.